Thanks, implemented it with wicket 1.4.x also, anybody interested in
the code let me know ;)
On Fri, Jul 6, 2012 at 5:17 PM, Martin Grigorov mgrigo...@apache.org wrote:
I have tried with
On Fri, Jul 6,
- jWeekend LegUp
On Fri, Aug 24, 2012 at 8:33 PM, Bruce McGuire brlmcgu...@gmail.com wrote:
PS: I forgot to mention that I would like to use testNG.
On Fri, Aug 24, 2012 at 10:31 AM, Bruce McGuire
Also see org.apache.wicket.devutils.inspector.RenderPerformanceListener
in wicket-devutils module. Enable it and then check the data with the
On Sat, Aug 25, 2012 at 2:58 AM, steven.li steven...@skyworthglobal.com wrote:
Enable wicket debug
Looking forward for your articles!
On Sun, Aug 26, 2012 at 7:21 AM, Jonathan Locke
It's been a long while since I checked in,
we are developers from the Apache project Apache OpenMeetings, we
provide a Web-Conferencing application that is currently Flash-based
on the client side.
We already have a server side stack with Spring + openJPA + Axis2 that
provides us with a SOAP/REST API and ORM.
We are currently
You didn't say what your web service response's type is.
By referring to jQuery's #load() method it seems like your WS returns
ready to render HTML, but later you say that you will create the
returned response is plain data
Thanks for the detailed answer Martin!
You are right in my description I missed one part, for generating the
HTML my plan was to use Apache Velocity. The REST interface will only
generate data to fill that HTML.
I've created a MockUp of the architecture proposal that should cover it all:
I see a little problem in your architecture - the jQuery client will
make a request to the Velocity servlet, then if you use
the REST API you'll need to make another http request. If both the
servlet app and the REST app are deployed on the same
web container instance/node then you
The security aspect is true. I don't see a problem in the worker
threads yet, however you might be right.
We might try a Wicket example to see how we can integrate all our
existing code into it.
2012/8/26 Martin Grigorov mgrigo...@apache.org:
I see a little
Thread starvation problem:
1) the Velocity servlet is deployed at /velocity
2) the REST API is in another app deployed at /rest
3) the JS client makes a call to /velocity - this acquires one worker thread
4) the Velocity servlet by using some HTTP client Java library makes a
call to /rest - this
that seems to be a misunderstanding. The velocity servlet would never
trigger the REST interface using some Java library.
The velocity servlet can access all required data that it needs to
render the HTML websites.
It would actually even use the same Spring injected Services to
I've got a 1.5.x app which I'm converting to 6.0-beta3 and I keep my markup
separate and under WEB-INF/html.
With 1.5.x I use the following in my Application class:
IResourceSettings resourceSettings = getResourceSettings();
I can't seem to
WebApplicationPath doesn't look in WEB-INF anymore because this may
lead to a security hole.
If you still want to load resources from there it is quite easy to
create your own version of WebApplicationPath that doesn't have this
On Sun, Aug 26, 2012 at 10:19 PM, Phill
Mail list logo