Wicket is a wonderful framework for handle web pages request. But I'm
thinking that it would be nice too to publish general web service without
any visual component associated.
In other word would be very useful to use Wicket to expose a server side
services in protocol agnostic way.
For
I think using final for the onComponentTag and onComponentTagBody
methods have served their purposes fine during our wild two years of
development, but our core components are now stable enough to not have
to be worried about painting ourselves in the corner when we would
open up these methods
write your own IRequestTargetUrlCodingStrategy class.
That can decode a request to a IRequestTarget and encode one to a url (that
shouldn't be to hard)
Then also have you own kind of IRequestTarget that is the service.
johan
On 12/6/06, Paolo Di Tommaso [EMAIL PROTECTED] wrote:
Wicket is a
versioning can handle this. because it won't clone the page but you will
keep the reference to the old page for every of course.
and if that page2 gets saved to disk and reloaded back in it will also
instantiate the page1 again ofcourse.
So you will have always that baggage of that extra page.
in the current versioning we don't store a pointer. We only keep a reference
of that page when we encounter
it and then set it back when we deserialize it (that immediately happens)
So if that page is in the pagemap by itself or not doesn't really matter (it
is in the pagemap through the other
yes fine.
On 12/6/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
Is that a +1 on my proposal?
Eelco
On 12/6/06, Johan Compagner [EMAIL PROTECTED] wrote:
just look if there is not a gotcha somehow that we can open
for the method you want to remove final.
If you can't think of one then remove
[X] Yes
[ ] no
Yes! My first vote here :)
(These are open votes, right?)
Erik.
Eelco Hillenius wrote:
I think using final for the onComponentTag and onComponentTagBody
methods have served their purposes fine during our wild two years of
development, but our core components are now stable
On 12/6/06, Johan Compagner [EMAIL PROTECTED] wrote:
so what you fix was nothing.
You still get swamped in exceptions on jetty for OSX and now also others
that do throw
the right socket exception are getting swamped with exceptions.
No, because I log a warning exluding the exception. But fine,
