Gerald Fernando wrote:
Hello Friends,
Am Gerald, new to wicket.
can anyone say about wicket and advantages over other technologies
it is very useful to my next step.
please help me
http://lmgtfy.com/?q=wicket+advantages
--
Igor Vaynberg wrote:
what makes you think you need any special tweaking or scaling in
wicket to handle that kind of load?
I've got a bit of knowledge (not wicket-specific) in this area and the one
thing I can say for sure is: if there is a financial stake in the project,
then you should never
nino martinez wael wrote:
The largest issue about going towards a desktop solution with java are
that designing the ui really are a pain if you dont use something like
mattise, it's even worse that hacking html.. I'll agree on the javaFX
Granted, HTML frameworks have come a long way in the
I've changed out PageExpiredErrorPage to be the login page for our app.
Does wicket have any support built-in to help return the user to where
they were after re-authenticating?
From my modest understanding of Wicket, it would need to be a bookmarkable
page, which will be ok for a good
Wow, I hope it's really that easy!?!
Should this work through an appserver restart? E.g. if I
1) login to the app
2) restart the app server
3) click a page link in the browser
Should this work? It didn't for me. Based on my limited understanding of
how wicket works and stepping into the
Jeremy Thomerson wrote:
the path is stored in the session, so as long as your app server
reloads existing sessions on restart, it should (iirc). however, in
your dev environment, the app server probably blows away sessions
hr, i just re-read and realized that you said this is for the
Warren Bell wrote:
Try securing the link on your HomePage and do not secure the HomePage
itself. The link has to implement ISecureComponent.
Warren,
I've followed your suggestion but the link is still rendering, so I'm still
missing something.
First, I made my own component MyPageLink that
, that was really easy
:
Chris
Christopher L Merrill wrote:
Warren Bell wrote:
Try securing the link on your HomePage and do not secure the HomePage
itself. The link has to implement ISecureComponent.
Warren,
I've followed your suggestion but the link is still rendering, so I'm still
missing
I have a question about rendering of links to secure pages when the user has not
been authenticated.
Based on this line from the tutorial:
In addition we granted links to our homepage the right to be clicked
(enable).
I expected the link to either be non-visible or non-clickable - since I did
Frank Tegtmeyer wrote:
would the Request object be a good place to store a JPA EntityManager?
It would be created in onBeginRequest() and destroyed in
onEndRequest() of the RequestCycle object.
You may find these of interest:
Dashorst wrote:
Might be a dumb question, but why not make your wicket front end use
the JAX-WS services as well?
Martijn
On Thu, May 28, 2009 at 10:01 PM, Christopher L Merrill
ch...@webperformance.com wrote:
I've got a few questions that are somewhat general to web development,
but since we've chosen
James Carman wrote:
Is there any particular reason that you want to use XML-based
communication if you have an all-Java architecture going on?
Wouldn't it be easy to XMLize the services you're exposing remotely later if a
different type of client would want to connect to it? I'd say just
use
I've got a few questions that are somewhat general to web development,
but since we've chosen Wicket as one of our front-end frameworks, I
thought I would ask here first for pointers...especially where there
may be a wicket way of doing things that we need to be aware of.
The system we're
Martin Makundi wrote:
Use an IDE plugin?
That's a hack, not a design.
Wow...I'm new to this list, but I doubt you can expect much help with
that attitude. I suggest you request a refund for your Wicket license
and support subscription and go find a tool that better fits your needs.
Oh,
I'm just getting my feet wet with Wicket and OpenJPA. I've got the
basics of both and have started prototyping parts of an upcoming
project in each and everything was going great. Then I tried to put
the two technologies together and hit a wall. I'd written the
OpenJPA pieces in a standalone
15 matches
Mail list logo
