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. The biggest changes are in conversation
propagation. If you do not use the conversation scope, the transition to
the new module should be
Thanks Emond,
I will watch the progress and report back.
For now.. I'm ignoring the warnings and using a snapshot from glassfish.
I'm using CDI just for EntityManager injection..and it's just RequestScoped.
So.. from what I saw in the current version, the biggest problem would
be if it was context
Yes, we are using the .FeedbackMessages#hasMessage(IFeedbackMessageFilter)
as we had no other choice.
I'll file a ticket with a pull request now that I got used to GitHub :)
~ Thank you,
Paul Bors
On Thu, Dec 5, 2013 at 11:39 AM, Martin Grigorov wrote:
> Hi,
>
> You are right.
> But I think
Hi,
You are right.
But I think we can only improve the javadoc.
You will have to
use
org.apache.wicket.feedback.FeedbackMessages#hasMessage(org.apache.wicket.feedback.IFeedbackMessageFilter)
with a filter that makes exact match.
I have the feeling that we added such filter but I can only
see org.
Currently (as of 6.10.0) the JavaDoc on
the FeedbackMessages#hasMessage(int) states that it returns true if and
only if a message with the specified level was registered.
However it relies on FeedbackMessage#isLevel(int) which in turn return true
if whether the message level is greater than or equ
remove the "don't"
On Thu, Dec 5, 2013 at 3:30 PM, Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:
> Why just don't pass an attribute that means "do not show progress"... and
> use the same for all AJAX action that do not need to show progress
>
>
> On Thu, Dec 5, 2013 at 2:58 PM, Mar
Why just don't pass an attribute that means "do not show progress"... and
use the same for all AJAX action that do not need to show progress
On Thu, Dec 5, 2013 at 2:58 PM, Marieke Vandamme wrote:
> Hi,
>
> Okay, I'll do my best to explain more in detail.
>
> When doing an ajax call, we want
Hi,
On Thu, Dec 5, 2013 at 2:58 PM, Marieke Vandamme wrote:
> Hi,
>
> Okay, I'll do my best to explain more in detail.
>
> When doing an ajax call, we want to show a busy indicator on the page, so
> that the user knows that something is happening and that he must wait for
> the ajax response. Th
Hi,
Okay, I'll do my best to explain more in detail.
When doing an ajax call, we want to show a busy indicator on the page, so
that the user knows that something is happening and that he must wait for
the ajax response. This can be done by adding the Generic busy indicator (as
described on the
Hi,
Please give more details what exactly is the problem.
On Thu, Dec 5, 2013 at 8:30 AM, Marieke Vandamme wrote:
> Dear wicket users,
>
> We are using the Generic busy indicator found on the wiki to have a busy
> indicator for every ajax event.
>
> https://cwiki.apache.org/confluence/display/W
These phone signal jammers are available at a very reasonable price. You can
buy this phone signal jammer very easily. As this service takes nominal
charges on the network, so you would need to spend a little amount to get
complete peace of mind when you are not willing to get disturbed.
--
Vie
11 matches
Mail list logo
