time I ran into some strange problem I could not solve.
Emond Papegaaij
On Thursday 26 February 2009 17:20:04 Brill Pappin wrote:
I don't think we're talking about the same plugin then (although you
seem to be calling it the same thing)...
I'm referring to:
http://m2eclipse.codehaus.org
eclipse:eclipse , it works every time :)
2009/2/27 Emond Papegaaij emond.papega...@topicus.nl
That is the plugin Martijn is talking about, and I am one of the
co-workers he
mentioned. I tried the m2eclipse plugin and used it for a day. The plugin
(version 0.9.7.200902090947) was able
) integration though, that I see the benefits of
(and for me it works 95% of the time)...
2009/2/27 Emond Papegaaij emond.papega...@topicus.nl
Yes, mvn eclipse:eclipse works, but it's not really integrating maven in
eclipse. I have to run it manually after changing the pom or the project
regards,
Emond Papegaaij
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
that
does not only give permission to the specified class, but also to its
subclasses. This could be achieved by extending ComponentPermission and
overriding the implies method. The first part of the the path array should
contain the classname of the component.
Best regards,
Emond Papegaaij
AnnotatedPermission ? That would be really great.
Kind Regards,
Olger
On 6 jan 2010, at 12:52, Emond Papegaaij wrote:
Hi,
Your change breaks some functionality. It is now no longer possible to
grant permissions for anonymous inner classes at all, you are now forced
to grant the permission
On 6 jan 2010, at 14:03, Emond Papegaaij wrote:
Hi Olger,
The InPrincipal annotation is something we developed as an alternative
for the hive files (which we find difficult to maintain, not only with
anonymous inner classes). Principals are defined by a set of classes with
annotations
(with
org.apache.wicket.security.hive.authorization.permissions.ComponentSubclassPermission).
Best regards,
Emond Papegaaij
On Thursday 07 January 2010 12:42:17 Emond Papegaaij wrote:
Well, provided you've implemented the ComponentSubclassPermission, you
could overwrite the alias for ComponentPermission
not yet started.
Best regards,
Emond Papegaaij
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
it does not provide
the page identity, and using BookmarkablePageLink is not an option because in
many cases the target page is not bookmarkable.
Can PageLink please be restored?
Best regards,
Emond Papegaaij
-
To unsubscribe, e
The javadoc says I should use Link or BookmarkablePageLink, which, as I
explained, are both not an option.
Emond
On Friday 15 January 2010 05:08:42 Igor Vaynberg wrote:
what does the javadoc say?
-igor
On Thu, Jan 14, 2010 at 6:12 AM, Emond Papegaaij
emond.papega...@topicus.nl wrote
I totally agree with Jeroen. The 3rd constructor is dangerous and should be
removed. The other two, however, are lazy and create the page in the onClick
(provided that the IPageLink interface is implemented correctly). Of course,
it is possible to copy PageLink and IPageLink to wicket-security,
That's what I'm trying to say: it can't be accomplished by either
BookmarkablePageLink or Link. Link does not have a getPageIdentity method and
BookmarkablePageLink only works for bookmarkable links (duh). So Link is never
an option because of the missing getPageIdentity method and
But leaving IPageLink without any classes using it seems a bit weird to me. I
think IPageLink should be removed with PageLink and probably be moved to
wicket-security.
On Tuesday 19 January 2010 11:36:59 Jeroen Steenbeeke wrote:
Which is what I suggested earlier in this discussion as well. So
Wicket Security 1.4-beta1 has just been released.
This release contains all updates made by Olger Warnier in the last 6 months
to make Wicket Security work with Wicket 1.4 and the examples he added. It
also contains the new ComponentSubclassPermission, which makes it possible to
authorize a
Personally, I think, it is much more elegant to call setVisible on the
component you want to display or hide, or, when the outcome of the condition
can change on each render, override isVisible to return the outcome of the
condition.
Emond Papegaaij
On Friday 17 April 2009 08:50:21 Vladimir K
I've had similar problems when using method breakpoints on inner classes.
Removing the breakpoint speeds up the entire application dramatically (the
breakpoint also doesn't work). So try removing your breakpoints.
Emond
On Tuesday 14 July 2009 19:15:02 John Ipson wrote:
Has anyone ever run
of it, or the other way around (building SWARM
on top of Shiro). Perhaps this core security framework can then be integrated
into the wicket core. However, I doubt if such a thing can be accomplished for
wicket 1.5 (or at all).
Best regards,
Emond Papegaaij
On Monday 25 January 2010 11:11:31 nino martinez
On Monday 25 January 2010 13:02:05 James Carman wrote:
On Mon, Jan 25, 2010 at 6:11 AM, Emond Papegaaij
emond.papega...@topicus.nl wrote:
I do think this is a good idea, however it will be difficult to
implement. WASP/SWARM already provides this setup. WASP defines the
interface, where
On Monday 25 January 2010 14:31:47 James Carman wrote:
On Mon, Jan 25, 2010 at 8:07 AM, Emond Papegaaij
emond.papega...@topicus.nl wrote:
That sounds a bit overkill to me. I don't think anyone will ever want to
use SWARM in a non-Wicket application. Naturally, this is a bit different
On Monday 25 January 2010 15:22:42 James Carman wrote:
On Mon, Jan 25, 2010 at 9:11 AM, Emond Papegaaij
The current wicket-security code is somewhat limited in what you can do
with it. WASP provides a much richer (probably too rich) interface for
security. I see WASP as a viable basis
On Monday 25 January 2010 15:59:53 James Carman wrote:
On Mon, Jan 25, 2010 at 9:50 AM, Emond Papegaaij
Most of the complicated stuff is from SWARM, which indeed requires a lot
of configuration. The difference between WASP and SWARM is not quite
clear from the documentation, nor
it or provide a
solution in another way.
If you do not want to test this commit, you can always stick to beta1,
released last week.
Best regards,
Emond Papegaaij
On Thursday 21 January 2010 10:48:36 Emond Papegaaij wrote:
Wicket Security 1.4-beta1 has just been released.
This release contains all
to
keep the wicket:path attributes in the generated markup, because they can be
very handy for debugging, but I have to disable them to keep the HTML
validator happy.
Best regards,
Emond Papegaaij
-
To unsubscribe, e-mail: users
(ON/SELENIUM_COMPATIBLE/OFF)? Perhaps this can be implemented in wicket 1.5?
On Tuesday 27 April 2010 18:05:48 Igor Vaynberg wrote:
turn off the attribute before you run your validator.
-igor
On Tue, Apr 27, 2010 at 12:11 AM, Emond Papegaaij
emond.papega...@topicus.nl wrote:
Hi,
For our project, we
need yet another configuration option'. Could this
please be reconsidered? I like to keep the wicket:path attributes in the
generated markup, because they can be very handy for debugging, but I
have to disable them to keep the HTML validator happy.
Best regards,
Emond Papegaaij
In our application we use quartz for long running jobs. These threads have
access to the application context, which contains the wicket application. In
the execute method, we locate the application and use Application.set and
Application.unset to set and remove the application. This is,
On Thursday 27 May 2010 12:41:10 James Carman wrote:
On Thu, May 27, 2010 at 2:34 AM, Emond Papegaaij
emond.papega...@topicus.nl wrote:
In our application we use quartz for long running jobs. These threads
have access to the application context, which contains the wicket
application
changed since then,
because no bugs were found.
Emond Papegaaij
On Friday 28 May 2010 01:38:54 Jeremy Thomerson wrote:
See the second message at this link (the one from Martijn):
http://apache-wicket.1842946.n4.nabble.com/Wicket-1-4-upgrade-dependent-on-
Wicket-Security-1-4-td2031552.html
Jeremy
On Friday 28 May 2010 15:33:16 Sven Meier wrote:
OK, no ITL, got it.
Then, you can use that Runnable anywhere to run a task
with all of the appropriate Wickety goodness set up for you (except
for the request cycle of course because you're not executing within a
request cycle).
But what
On Wednesday 02 June 2010 15:54:50 david_ wrote:
Maybe someone knows who I can contact about this?
I wicket-security developer maybe?
Unfortunately we don't use multiple applications in the same servlet
container. So, I can't really help you with this. Maurice probably would have
known how to
On Wednesday 09 June 2010 21:30:39 ViShap wrote:
I just stumbled upon this announce and didn't have the time to dig deep
into the code, and the links you suggested don't mention anything, so i
have a short question:
Is it possible to use annotations instead of that manual hive-file?
If
Hi Ichiro,
If you want to enforce valid XHTML, take a look at the WicketStuff HTML
Validator: http://github.com/dashorst/wicket-stuff-markup-validator
It automatically validates all pages served by the application and shows an
error report for invalid markup.
Best regards,
Emond Papegaaij
recommend Safari
(best with webkit-nightly) or a Chromium daily build. Plain Safari works quite
well, but with some minor issues. Google Chrome is able to display the page,
but most of the effects do not work well.
Emond Papegaaij
On Thursday 25 November 2010 01:28:08 Martijn Dashorst wrote
Hi Alec,
If you use WiQuery for your javascript-enabled panels, this is done
automatically. WiQuery will add the javascript calls in the right places for
you.
Best regards,
Emond
On Saturday 24 September 2011 19:58:05 Alec Swan wrote:
Hello,
We use panel swapping to implement tabbing. The
Hi Dan,
As Martin stated, wicket-security (wasp-swarm) is now part of wicketstuff-core
and as such is released for every wicket release. It is maintained and it will
continue to work, as all our major applications are built on top of it.
Best regards,
Emond Papegaaij
On Friday 09 December
Thanks for the suggestion! I've just implemented this. It should be available
in 1.5.5 and 6.0.0, see https://issues.apache.org/jira/browse/WICKET-4419 for
details.
Best regards,
Emond
On Monday 20 February 2012 10:48:52 Josh Kamau wrote:
Thanks for the post.
I wish this could be
Wicket security for 1.4 is no longer maintained and it was never released as
part of WicketStuff core. If you want to use wicket security on 1.4, I suggest
you build it yourself from https://github.com/dashorst/wicketstuff-security .
This is where we put it before adding it to WicketStuff core.
I've already created the ticket (WICKET-4536) and committed a fix.
Best regards,
Emond
On Monday 07 May 2012 11:13:22 Martin Grigorov wrote:
Hi Thomas,
It seems WICKET-4468 broke it somehow.
Please file a ticket.
On Sun, May 6, 2012 at 1:55 PM, Thomas Heigl tho...@umschalt.com wrote:
of the AtmosphereServlet.
Perhaps you forgot to add AtmosphereServlet to your web.xml? AtmosphereServlet
loads atmosphere.xml, which in turn fires up the WicketFilter.
Best regards,
Emond Papegaaij
On Wednesday 13 June 2012 13:54:54 heapifyman wrote:
I think I had the same problem and was able to overcome
as I know, this is the only way
to do push in Wicket 1.5. Both server and client (js) do not support pushing
component updates to the client without initiating an AJAX-call.
Best regards,
Emond Papegaaij
On Thursday 12 July 2012 04:15:52 Decebal Suiu wrote:
Hi
I want to use a push technology
Hi Pierre,
First of all, I strongly recommend you do not use a different
HeaderRenderStrategy. It is likely to get removed in future versions of Wicket
and might break libraries that depend on the normal HeaderRenderStrategy.
Second, I suggest you use Wicket 6, because consistent resource
Hi Pierre,
First of all, I strongly recommend you do not use a different
HeaderRenderStrategy. It is likely to get removed in future versions of Wicket
and might break libraries that depend on the normal HeaderRenderStrategy.
Second, I suggest you use Wicket 6, because consistent resource
On Monday 30 July 2012 18:18:46 Pierre Goiffon wrote:
But one more question though : why rendering wicket:head (in the markup
file) contributions before renderHead() (in the java file) contributions ?
Seems to me that what you'll put in wicket:head will certainly be some
king of static code,
We've noticed this problem as well. It only happens on Tomcat. I'm not sure
what is going on, but it all starts with Tomcat loosing query parameters on
the ws-request (url/?0-1.IBehaviorListener.0- is changed to url). This
makes it impossible for wicket to recognize the call to a behavior,
You probably did not setup Atmosphere. Wicket-Atmosphere requires Atmosphere
to be available in your web application. Please consult the documentation of
Atmosphere for instructions. You can also take a look at wicket-examples
(especially web.xml and atmosphere.xml), which includes a working
Yes, this is the way to do it. Most of the code in ResourceAggregator is about
resolving dependencies and resource bundles. If your DojoRequireHeaderItem is
never part of a bundle (which probably is the case), you can skip the
'getItemToBeRendered' part.
Best regards,
Emond
On Sunday 09
Hi,
I don't know HazelCast, but the problem you are seeing is that EventBus.get()
only works when the application is attached to the current thread. You either
have to pass a reference to the EventBus to your broadcaster, or, if you have
access to the Wicket Application, you can set it on
Hi,
I just noticed a small error in my advice: the class is not called
ThreadLocal but ThreadContext. The idea is very simple:
try {
ThreadContext.setApplication(application);
/* do your thing */
} finally {
ThreadContext.setApplication(null);
}
The problem with this code is that you
You will need the application. Without the application, it won't work. There
are dozens of ways to pass the application to where you need it. For example,
you could inject it using your favorite dependency injection framework, or you
could pass it manually to the place where you need it.
Best
You can find all information about Wicket's downloads, repositories and scm on
http://wicket.apache.org/start/download.html
Best regards,
Emond
On Tuesday 11 September 2012 04:37:36 esajjkh wrote:
Thanks Emond, Where I can find the wicket-atmosphere 0.4-snapshot maven
dependency?
--
Then you probably didn't register the EventBus in your application's init
method. Please take a look at the demo-application I've setup:
https://github.com/papegaaij/wicket-atmosphere-quickstart
It contains the minimal configuration needed for wicket-atmosphere.
Best regards,
Emond
On
This is most likely caused by incorrect escaping, which might be a bug in
Wicket or Wicket-Atmosphere. Can you try to create a quickstart to demonstrate
the problem and file a Jira ticket? You can use the example application at
https://github.com/papegaaij/wicket-atmosphere-quickstart
Best
As far as I know, the latest versions of wicket-atmosphere and atmosphere
should fall through to the default servlet handling if wicket does not handle
the request. I don't know that much about servlet configuration, but I don't
think wicket-atmoshpere changes anything in this context. You
the response in chunks.
Jean Francois explained in Atmosphere mailing lists that a special
Atmosphere has to be used that will collect the whole response before
flushing it.
On Tue, Nov 13, 2012 at 3:25 PM, Emond Papegaaij emond.papega...@topicus.nl
wrote:
This is most likely caused
of some
attributes in AtmosphereRequest on which to write your filter, which puts a
lot less weight on the server than setting up a RequestCycle.
Best regards,
Emond Papegaaij
On Thu, Dec 20, 2012 at 8:31 PM, Noven noven_...@yahoo.com wrote:
Hi,
I just saw new features released at wicket 6.40
asking this question at their google groups. I've created a ticket
(WICKET-4946) for passing parameters to atmosphere, which would allow you
to disable websocket.
Best regards,
Emond Papegaaij
On Mon, Dec 24, 2012 at 12:22 PM, Noven noven_...@yahoo.com wrote:
Hi,
Thank you for your reply before
param-valuefalse/param-value
/init-param
Don't know if there's drawback doing that since it comes as default setting
in the quickstart.
Regards,
Noven
From: Emond Papegaaij emond.papega...@gmail.com
To: users@wicket.apache.org
not work in firefox?
I will enable WS back and figure it out how to fix in firefox.
Regards,
Noven
From: Emond Papegaaij emond.papega...@topicus.nl
To: users@wicket.apache.org; Noven noven_...@yahoo.com
Sent: Tuesday, January 8, 2013 3:38 PM
Subject
Hi Pierre,
The UUID is bound to a page when atmosphere makes to call back to the server,
which makes sense because before then, there is no AtmosphereResource, which
means there cannot be a UUID. I think this is a bit of a design flaw, because
it is not possible to listen to the registration
,
Pierre
On Tue, Jan 8, 2013 at 2:07 PM, Pierre Goupil goupilpie...@gmail.comwrote:
Excellent, Emond! I'll try it like you said and tell you what happens.
Cheers,
Pierre
On Tue, Jan 8, 2013 at 1:55 PM, Emond Papegaaij
emond.papega...@topicus.nl wrote:
Hi Pierre
With recent versions of wicket-atmosphere, you are required to add this
parameter to the AtmosphereServlet:
init-param
param-nameorg.atmosphere.cpr.broadcastFilterClasses/param-name
param-valueorg.apache.wicket.atmosphere.TrackMessageSizeFilter/param-
value
/init-param
Did you
never called.
Is there any more than implementing ResourceRegistrationListener that
I'm
supposed to do?
Regards,
Pierre
On Thu, Jan 10, 2013 at 1:05 PM, Emond Papegaaij
emond.papega...@topicus.nl
wrote:
I've just pushed the fix for WICKET-4957
-side nor server-side.
As I understand things, it should work with any version of Atmosphere
starting from 1.0.0, right?
Do you have any clue?
Regards,
Pierre
On Thu, Jan 10, 2013 at 1:07 PM, Emond Papegaaij emond.papega...@topicus.nl
wrote:
With recent versions of wicket
on this page:
https://github.com/Atmosphere/atmosphere/wiki/Enabling-HttpSession-Supportand
it works like a charm!
Cheers, men!
Pierre
On Fri, Jan 11, 2013 at 5:22 PM, Emond Papegaaij
emond.papega...@topicus.nl
wrote:
Yes, it should work with any 1.0 version. I think you should try to
verify
? Issue a pull-request? Or just let
you introduce this tiny bit of code?
Thanks for the good, hard work!
Regards,
Pierre Goupil
On Thu, Jan 10, 2013 at 4:22 PM, Emond Papegaaij emond.papega...@topicus.nl
wrote:
You should register it with EventBus.addRegistrationListener and a page
DroppableBehavior is the replacement of DroppableAjaxBehavior. You use it
like this:
final DroppableBehavior droppableBehavior = new DroppableBehavior();
droppableBehavior.setDropEvent( new AjaxDropCallback() {
protected void drop(AjaxRequestTarget target, Component source,
Component dropped)
Hi,
I'm sorry for the late reply, but I haven't been well last week.
Wicket-atmosphere follows the wicket request cycle. Perhaps you can add a
RequestCycleListener to setup the context? Keep in mind though that this
listener is also called for normal requests. Let me know if this is ok for
you.
On Monday 25 March 2013 00:59:30 Leonid Bogdanov wrote:
Hello!
I'm playing with the wicket-atmosphere module and, while generally it
works fine, I stumbled upon a couple of issues:
1) Suppose I have a Page with a method marked with @Subscribe
annotation, this subscribtion has a
Hi,
I suggest you try upgrading wicket, wicket-atmosphere and atmosphere to
more recent versions first. The version of wicket-atmosphere you are using
is almost a year old. The most recent version is 0.12. Several bugs have
been fixed since then.
Best regards,
Emond
On Friday 09 August 2013
Hi,
As you can see in the ticket, we are unable to reproduce this problem. It is
likely to be related to a particular way of using wicket-atmosphere. If you
can provide us with a quickstart (you can clone the wicket-atmosphere-
quickstart project at
As you can see in the web.xml, the WicketFilter runs under /app. You can
start it in jetty using the maven jetty plugin: mvn jetty:run (which will make
the application available under localhost:8080/app)
On Tuesday 13 August 2013 03:21:20 souvikbhattacharyas wrote:
Hi,
I have compiled the
Hi Pierre,
Good to hear you like it! Unfortunately, we are still waiting for the rest of
the server stack to support websockets before we can actually use it in
production applications. Hopefully, with the release of jee7 (with jsr356)
maintainers of httpd and ajp will finally realize they
, Aug 14, 2013 at 3:33 PM, Emond Papegaaij
emond.papega...@topicus.nl
wrote:
Hi Pierre,
Good to hear you like it! Unfortunately, we are still waiting for the
rest
of
the server stack to support websockets before we can actually use
it in
production applications
Until then, you can test with 0.2-SNAPSHOT. You can find the details for
the snapshot repository on our download page.
If you find any issues with wicket-cdi-1.1, please file JIRA issues and
assign them to me.
Best regards,
Emond Papegaaij
On Wed, Dec 4, 2013 at 7:02 PM, Diogo Casado diogocas
RequestScoped.
So.. from what I saw in the current version, the biggest problem would
be if it was context oriented.
Regards,
Diogo C.
On Wed, Dec 4, 2013 at 7:01 PM, Emond Papegaaij
emond.papega...@gmail.com wrote:
Hi Diogo,
Please note that wicket-cdi-1.1 is still experimental. I do
.
Thank you for your efforts!
- Diogo
On Thu, Dec 5, 2013 at 6:09 PM, Emond Papegaaij
emond.papega...@gmail.com wrote:
The new module should be fully functional, including all scopes. The
performance should be much better than with the old module, due to
InjectionTarget caching
Did you migrate to wicket-cdi-1.1? To inject a non-managed class, use
NonContextual.of(MyClass.class).inject(instance). Components, however, are
injected by wicket-cdi itself. You should not need to inject those manually.
Best regards,
Emond
Op 4 apr. 2014 20:54 schreef David Beer
Hi Duto,
I've just pushed the upgrade to the latest version of Atmosphere to the
wicket-6.x and master branches. It should be in the next release of wicket-
atmosphere for both versions. I've also changed the
TrackMessageSizeFilter to extend the atmosphere class.
Best regards,
Emond
On Monday
I replied to your mail already, but it seems my message was lost in the mail
outage. Atmosphere and the JS are upgraded on the wicket-6.x and
master branches. I've also fixed the filter.
https://issues.apache.org/jira/browse/WICKET-5589
Best regards,
Emond
On Monday 05 May 2014 14:08:20
Could you create a JIRA issue for this, so we (and other users) can track
this issue? A short sample is not needed, because I can see in the code
that this can indeed go wrong. I'll make sure this gets fixed in the next
version.
Best regards,
Emond
On Sat, May 17, 2014 at 3:59 PM, Olivier
You are right. The filter allows the client to know the length of pushed
messages. I believe it was also needed for very long messages. The problem
with the default filter was, that the separator was far too common to use for
wicket's Ajax responses and the default implementation did not offer
Hi Sebastien,
I did not see any CDI related discussion on dev yet. What needs to be changed
to wicket-cdi?
Best regards,
Emond
On Saturday 07 February 2015 21:57:11 Sebastien wrote:
Dear all,
I think I've now a full working version of my usecase: in EJB/@Asynchronous
mode (stateless and
The @Subscribe annotation has 2 filter options. In this case, I would go for
the first: 'filter()'. The Predicate type you need to specify gets an
AtmosphereEvent, where the payload is set to the object you are broadcasted.
If you change this object to a little more than just a message, you can
Hi François,
Since 8.0.0-M2 (and 7.5.0) the CsrfPreventionRequestCycleListener will block
requests without an Origin and Referer header. The reason for this is that is
possible for an attacker to prevent a browser from sending a referer header
(for example with rel="noreferrer"). When you open
Before you spend another day on troubleshooting again: check WICKET-6457. It's
a regression caused by the fix for WICKET-6387 which will cause the pagestore
to keep growing on some containers (like wildfly). It is fixed in 7.8.1 which
is
in the process of being released at this moment.
Emond
Martin is right. It seems like you found a regression in the changes made for
WICKET-6021. In general, the performance was increased by those changes, but
evidently not in this case. Please create a JIRA issue and attach a quickstart
that shows the problem. That should help us debug this
11:36:54 CEST Thomas Heigl wrote:
> Hi Emond,
>
> How can I test this? Did you do a milestone release or do I have to build
> from source and push to my local artifact repo?
>
> Best,
>
> Thomas
>
> On Tue, Jun 5, 2018 at 3:01 PM, Emond Papegaaij
> wrote:
>
oss.sonatype.org/content/repositories/snapshots was cached in
> >> the local repository, resolution will not be reattempted until the update
> >> interval of sonatype-nexus-snapshots has elapsed or updates are forced ->
> >> [Help 1]
> >> [ERROR]
> >
&
ttps://oss.sonatype.org/content/repositories/snapshots was cached in
> >> the local repository, resolution will not be reattempted until the update
> >> interval of sonatype-nexus-snapshots has elapsed or updates are forced ->
> >> [Help 1]
> >> [ERROR]
>
On donderdag 7 juni 2018 17:10:16 CEST Martin Grigorov wrote:
> 8.0 is on its way to Maven Central!
Thanks for the help with the release Martin, and Thomas thanks for testing!
Emond
-
To unsubscribe, e-mail:
some exploratory testing against the current build. I checked
> >> Dialog,
> >> Autocomplete, Accordion, Slider, Sortable, and Tooltip and all seem to be
> >> working at first glance.
> >>
> >> All my tests pass as well.
> >>
> >> Best,
>
library. At least the will make it easy to stay up to date with the latest
version :)
I can't push a release to central, but perhaps Martin can do that when I'm
done? For now you can use a snapshot build. It works, but the UI API might
change a bit before the 8.0 release.
Best regards,
Emond Papegaaij
a snapshot build. It works, but the UI API might
> change a bit before the 8.0 release.
>
> Best regards,
> Emond Papegaaij
>
> Op vr 1 jun. 2018 17:36 schreef Thomas Heigl :
> > Hi Ernesto,
> >
> > I'm not sure how many people are still using it. But as I said
On maandag 19 februari 2018 11:22:30 CET Thomas Heigl wrote:
> 1. Current WiQuery version is not compatible with M9
>
> It still depends on WicketEventJQueryResourceReference. It would be great
> if someone could cut a milestone release for WiQuery as well, so I can do
> further testing with my
Hi,
The javadoc states 'Whether the session is invalid now, or will be invalidated
by the end of the request.' The first part is no longer true. The javadoc also
states that you normally should not need this method (why is it part of the
public API then?)
I think we can fix the method by
I think it should be enough to change the javadoc. The method returns
true when the session was invalidated *during the current request*.
Without a request there is no way of telling whether the session is
invalidated or not. IMHO throwing an exception is fine, but this
behavior should be
warded_for;
proxy_set_header X-Forwarded-Proto $proxy_x_forwarded_proto;
proxy_set_header X-Forwarded-Port $proxy_x_forwarded_port;
Best regards,
Emond Papegaaij
On Sat, Dec 22, 2018 at 7:31 PM Chris Turchin wrote:
>
> This might help:
> https://stackoverflow.com/questions/46337253/apache-rever
warded_for;
proxy_set_header X-Forwarded-Proto $proxy_x_forwarded_proto;
proxy_set_header X-Forwarded-Port $proxy_x_forwarded_port;
Best regards,
Emond Papegaaij
On zaterdag 22 december 2018 12:46:11 CET Chris Turchin wrote:
> This might help:
> https://stackoverflow.com/questions/46337253/apac
Hi,
Some time ago, we faced a similar issue. A custom component accessed
pages after they were unlocked, causing stale locks. Back then I filed
an issue (WICKET-6558), but haven't had time to implement the fix.
Locking pages after commitRequest should be blocked.
Best regards,
Emond
On Tue, Aug
1 - 100 of 106 matches
Mail list logo
