Hi,
Looking at the github project you refer to, it should work.
The GuiceComponentInjector which is set-up in the wicket application
injects proxies. That means that when your form is submitted (and a
second request is made), a new service instance is created.
So if it's not working for you,
hi guys,
i'm stuck in a problem showing up a modal window before a long running task
started by an ajax button and closing it when the process is finished - any
help/advice is highly appreciated!
i already managed to show up the ModalWindow using onBeforeSend ajax, but
one the one hand, the
Hi,
You should use onComplete instead of onAfter.
What is the problem with the contents ?
On Thu, Jun 27, 2013 at 9:48 AM, smöker smoe...@gmail.com wrote:
hi guys,
i'm stuck in a problem showing up a modal window before a long running task
started by an ajax button and closing it when the
I've found the combination of Wicket + Scala to be very productive.
Just make sure you use Fodel from Wicketstuff
When things get tricky, simply reduce the problem down to a java quick
start and proceed as usual.
I find that 99% of the time making a quick start solves the problem, when I
I want to add some jquery java script for every AjaxRequestTarget, I dont
want to repeat this code all over , is there a way to add my java script
to the target instance in a global way?
--
View this message in context:
org.apache.wicket.protocol.http.WebApplication#getAjaxRequestTargetListeners().add(new
org.apache.wicket.ajax.AjaxRequestTarget.AbstractListener() {
@Override
org.apache.wicket.ajax.AjaxRequestTarget.AbstractListener#onBeforeRespond()
})
On Thu, Jun 27, 2013 at 1:02 PM, fachhoch
I have egg on my face. After delving into this more deeply, I discovered
our corporate framework helpfully removes disabled buttons before they
get to the browser. Don't agree with the approach, but it is what it is.
(slinks away with tail between legs...)
From: Paul Bors p...@bors.ws
I agree; Since the EntityManager is bound to the request (scope), it's
usually better to inject ProviderEntityManager
However, in the demo project the service is not a singleton, so it
should be fine. A new instance of the service is created for every
injection.
Met vriendelijke groet,
Kind
Here are some discussions:
http://stackoverflow.com/questions/10431640/guice-persist-attempting-to-execute-an-operation-on-a-closed-entitymanager
http://stackoverflow.com/questions/14585505/jpa-guice-persist-permanently-opened-connection-issue
On Thu, Jun 27, 2013 at 3:20 PM, Bas Gooren
I'm not the one who posed the original question.
Andreas, like I said: please show us some code, and we can help you
pinpoint your issue.
In case your service is being serialized, a quick fix is to inject a
ProviderEntityManager instead of an EntityManager.
Met vriendelijke groet,
Kind
Forgive my newbie questions, but what is Fodel?
Is JBoss the most promising app server to build on? I have always felt like
any sufficiently advanced Rails app is indistinguishable from an ad-hoc
reinvention of a poorly spec'ed Java app server...
On Thu, Jun 27, 2013 at 5:18 AM, Peter Henderson
On Thu, Jun 27, 2013 at 6:29 PM, Mike Pence mike.pe...@gmail.com wrote:
Forgive my newbie questions, but what is Fodel?
https://github.com/wicketstuff/core/blob/master/jdk-1.6-parent/scala-extensions-parent/wicket-scala/src/main/scala/org/wicketstuff/scala/Fodel.scala?source=cc
Is JBoss
So when you need to add background jobs, message queues, user authentication
and such, do you just grab your favorite java libraries for those kinds of
things?
On Jun 27, 2013, at 11:34 AM, Martin Grigorov mgrigo...@apache.org wrote:
On Thu, Jun 27, 2013 at 6:29 PM, Mike Pence
I'm getting a serialization error when I shutdown Tomcat that has me confused.
java.io.NotSerializableException:
com.oa.frontoffice.service.AuthenticationService
I experienced quite a bit of this at first before learning that Wicket
serializes quite heavily, but gained a more thorough
While I agree with searching mailing list or searching web first, from
most users perspective, if you google for information before bothering
others, you end up on old pages and then links are broken. For example
just google wicket framework documentation. First link shows up in
google is
I found a solution, but I'm not sure it's the best/most elegant one, there is
a lot of messy code.
Upon selecting a certain AjaxCheckbox A in a ListView, I had to
1) disable AjaxCheckbox B
2) set its value to TRUE
and conversely, upon deselecting A, I had to (1) enable B and (2) set its
value
Yes I did reach this 404 page with a Google search.
Yes it would be nice to have a redirect to the new wiki or at least a
warning message.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/wicket-wiki-down-tp4659747p4659873.html
Sent from the Users forum mailing list
This is not the (or a) new wiki. This has been the wiki since we
joined Apache. We were obligated to use an export of the wiki (which
is a java process that is often broken) and link to the static files.
Since a couple of upgrades the export doesn't work anymore, and now
the static content has
On Thu, Jun 27, 2013 at 6:48 PM, Michael Pence mike.pe...@gmail.com wrote:
So when you need to add background jobs, message queues, user
authentication and such, do you just grab your favorite java libraries for
those kinds of things?
Yes. Often they provide much more functionality than what
On Thu, Jun 27, 2013 at 3:59 PM, Bas Gooren b...@iswd.nl wrote:
I'm not the one who posed the original question.
Andreas, like I said: please show us some code, and we can help you pinpoint
your issue.
Thanks for all the rapid help!
I've created a minimal page that shows the error.
Thank you both for your answers.
I wonder what would be best if you want to use the same validation
framework in multiple scenarios. I have a domain object that can be updated
either by a wicket form or by uploading an excel file. I want to have the
same validation logic. Would it be best to use
Yeah I have seen that post about that issue, but I don't use any img. Most of
my pictures are div and the image is called in the CSS.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Chrome-Calling-Pages-Twice-Issue-tp4659839p4659879.html
Sent from the Users forum
Hi Andreas,
When your validator fails, you remain on the FormPage. A quick debug
session shows me that the injected IService remains the same accross
requests.
The fix for your problem is simple, and a best practice anyway: inject
ProviderEntityManager in your service.
It's a best practice
On Thu, Jun 27, 2013 at 11:25 PM, Bas Gooren b...@iswd.nl wrote:
Hi Andreas,
When your validator fails, you remain on the FormPage. A quick debug session
shows me that the injected IService remains the same accross requests.
I've seen this too. I thought that this didn't matter since, as you
PS See https://code.google.com/p/google-guice/wiki/InjectingProviders
(header Providers for Mixing Scopes).
Met vriendelijke groet,
Kind regards,
Bas Gooren
Op 27-6-2013 22:03, schreef Andreas Lundblad:
On Thu, Jun 27, 2013 at 3:59 PM, Bas Gooren b...@iswd.nl wrote:
I'm not the one who
Hi Andreas,
My guess is that the GuiceComponentInjector proxies are detached when
the page is serialized.
The last page (or the last N pages) are kept in memory by wicket (I
think, last I checked was some years ago).
Checking ...
Yes, see LazyInitProxyFactory and its nested class JdkJHandler
hi
quick question about clustering: am i right to believe that putting
session/pagemap data in a memcached-like storage has advantages over the
tomcat session clustering in terms of latency and robust failover behaviour?
i mean, the latter obviously has the data nearby (when assuming sticky
27 matches
Mail list logo
