That would, ofcourse, be the perfect solution. Do I have to report a bug
for this?
I guess it would make sense to provide just a single implementation to
be used by both components, avoiding problems while trying to keep
them in sync.
Juergen
On 11/7/05, Ruud Booltink [EMAIL PROTECTED]
Somewhere in this thread I think I have identified a suggestion that looked very much in the
direction I would like to see it going. Unfortunately, right now I will need to pass through the
thread again and identify it.
Probably the way I would go would be to define an annotation
I think Eelco fixed it already in HEAD
Juergen
On 11/8/05, Marco van de Haar [EMAIL PROTECTED] wrote:
That would, ofcourse, be the perfect solution. Do I have to report a bug
for this?
I guess it would make sense to provide just a single implementation to
be used by both components,
Hi,
Which version of Wicket are you using? Lastest HEAD? You're not using
the component re-render feature, do you?
no, Wicket 1.1.
It is a redirect you do and the response gets rendered. Based on the
stack trace something is wrong in one of the headers. Within
Well, I rechecked all the
Try using jetty and the jetty-launcher plugin for eclipse. That is realy easy.
Juergen
On 11/8/05, Ralf Ebert [EMAIL PROTECTED] wrote:
Hi,
Which version of Wicket are you using? Lastest HEAD? You're not using
the component re-render feature, do you?
no, Wicket 1.1.
It is a redirect you
You may not even need Jetty or Tomcat. Take a look at the unit tests
which make use of WicketTester. It provides all the mock objects and
wireing required.
Juergen
On 11/8/05, Juergen Donnerstag [EMAIL PROTECTED] wrote:
Try using jetty and the jetty-launcher plugin for eclipse. That is realy
yet another way would be to enable debug logs on
wicket.Component=DEBUG. You should see messages like Begin render
... and End render The last Begin render .. should be of
interest.
Juergen
On 11/8/05, Juergen Donnerstag [EMAIL PROTECTED] wrote:
You may not even need Jetty or Tomcat. Take
Hi,
yet another way would be to enable debug logs on
wicket.Component=DEBUG. You should see messages like Begin render
... and End render The last Begin render .. should be of
interest.
thanks for your help, that helped me fix it. I saved a
StyleSheetReference static in my base page.
I take a look at WebRequestCrawlerSaver and this can be what i loking for
what is the way to plug this in a wicket application
thanks in advantage
On 11/8/05, Juergen Donnerstag [EMAIL PROTECTED] wrote:
If you are sure that you are realy not interested in path=xxx, may be
it worth if you
Wow great job Igor. Thanks for doing it. I think that's the proper way to
go.
Regarding cglib I think you should use spring AOP (it is already a
dependency and generalization can wait a bit). Spring AOP handles all that
and a bit more and is easy to use. Ie for cglib like in the current
please see http://www.wicket-wiki.org.uk/wiki/index.php/Obfuscating_urls
Jürgen
On 11/8/05, pepone pepone [EMAIL PROTECTED] wrote:
I take a look at WebRequestCrawlerSaver and this can be what i loking for
what is the way to plug this in a wicket application
thanks in advantage
On 11/8/05,
Hi,I've been looking at the Dojo and Scriptaculous extensions for Wicket and haven't seen what I'm looking for. Essentially, I want to have a master-detail display where the details are retrieved from the server and displayed in a div. Also, I'd like to be able to request a Form object from the
Howare thebase url's different? In all cases, aren't the base url's the following?
www.wicket-library.com/wicket-examples/template
My desire is to have url's that are as simple as possible. Long url's are problems for nontechnical users (for example in emails, whenbookmarking, on written
We could also support:
page=wicket (instead of bookmarkablePage=wicket)
the base in this:
www.wicket-library.com/wicket-examples/template
is
www.wicket-library.com/wicket-examples/
but with:
www.wicket-library.com/wicket-examples/template
/page
it is:
Yes you are right!
I was now more thinking of Igors proposal todo the 'injection' from the
outside:
MyComponent comp = new MyComponent(id);
//set this and that
SpringInitializer.initialize(comp,locator);
If you'd do it from the inside (as the original code) it is a different
story.
I
What I'm working on now is an ApplicationContext which wrapps the 'real'ApplicationContext and does create for getBean() etc automatically the
proxies. I think this way I'll never have to worry about the serializationproblem for such beans.
but what will inject your pages?
-Igor
On 11/8/05, Jeff Miller [EMAIL PROTECTED] wrote:
How are the base url's different? In all cases, aren't the base url's the
following?
www.wicket-library.com/wicket-examples/template
My desire is to have url's that are as simple as possible. Long url's are
problems for nontechnical users
I'll give it a shot. To be honest, I'd really like some more docs about the AJAX stuff. I've looked at the examples and they don't really provide the high-level overview I need to get my head around it.
On 11/8/05, Eelco Hillenius [EMAIL PROTECTED] wrote:
In the HEAD (1.2 dev) version of Wicket
It is more for components:
//constructor
public OrderPage(){
add(new
CustomerPanel(customer,getWrappingContext().getBean(customerDAO,CustomerDAO.class));
}
Just for normal DI in code.
Christian
On Tue, 8 Nov 2005 08:31:47 -0800, Igor Vaynberg [EMAIL PROTECTED]
wrote:
What I'm working
Well, the ajax support in Wicket is quite basic really. Just take a
look at Behaviour/ AjaxHandler/ one of the concrete AjaxHandlers like
DojoAjaxHandler. Generally, what they do is provide the means to let
handlers cooperate with components (due to suggestions earlier this
week, this was
In the mean time, I think Jessy Sightler has got some ajax writing on
his blog. Google for scriptaculous, wicket and autocomplete.
Martijn
On 11/8/05, Eelco Hillenius [EMAIL PROTECTED] wrote:
Well, the ajax support in Wicket is quite basic really. Just take a
look at Behaviour/ AjaxHandler/
Im still getting a class cast exception using cglib directly. im
probably doing something dumb, you want to take a look?
SpringInitializer line 61 is commented out, thats where proxies are
created for concrete objects.
By the way, the spring one works fine IF the dependency implements
I considered recommending "page=". It would be better than "bookmarkablePage=". Allowing "page=" in conjunction with alias would certainly allow simpler urls.
When browsing to bookmarkable page,wouldthe urlshow in browser as "page=alias"? I would prefer that to
On Tue, 8 Nov 2005 11:59:22 -0800, Igor Vaynberg [EMAIL PROTECTED]
wrote:
Im still getting a class cast exception using cglib directly. im probably
doing something dumb, you want to take a look? SpringInitializer line 61
is
commented out, thats where proxies are created for concrete objects.
I would rather weave it in using cglib and stay away from a
spring-specific proxy impl, becuase this thing can easily be
generalized to things beyound spring, like jndi lookups, etc.
-Igor
On 11/8/05, Christian Essl [EMAIL PROTECTED] wrote:
On Tue, 8 Nov 2005 11:59:22 -0800, Igor Vaynberg [EMAIL
Jeff Miller wrote:
I considered recommending page=. It would be better than
bookmarkablePage=. Allowing page= in conjunction with alias would
certainly allow simpler urls.
+1
---
SF.Net email is sponsored by:
Tame your development
ok, got the pure cglib solution working.
just had to call enhancer.setInterfaces(new Class[] { Serializable.class}) to weave in the serializable interface.
now it appears everything is working. sweet.
i am going to do a lot of refactoring today. maybe you can make your
wrappingcontext use the
you know you can have that today by implementing it yourself? Take a
look WebRequestCrawlerSave and you'll see that you can easily change
bookmarkablePage to page; you can make it case insensitive etc.
Juergen
On 11/8/05, Dan Gould [EMAIL PROTECTED] wrote:
Jeff Miller wrote:
I considered
or use a url rewriting filter like http://tuckey.org/urlrewrite/
-Igor
On 11/8/05, Juergen Donnerstag [EMAIL PROTECTED] wrote:
you know you can have that today by implementing it yourself? Take alook WebRequestCrawlerSave and you'll see that you can easily changebookmarkablePage to page; you can
Thanks. I'll take a look. With the proper regular expression, I may
be able to affect any url. I don't want to program a rule for each
url.
I was hoping you Wicket developers would tell me that my proposal was
faily simple to add to Wicket. I was looking for the simple url's to
be as easy and
Very good. I am still playing around with the writeReplace thing.
Regarding the refactoring what do you thing about this:
Instead of the ISpringContextLocator have a
interface ObjectResolverFactory{
ObjectResolver getObjectResolver(Field field);
}
interface ObjectResolver{
Object
thats pretty much exactly what i was thinking.
-Igor
On 11/8/05, Christian Essl [EMAIL PROTECTED] wrote:
Very good. I am still playing around with the writeReplace thing.Regarding the refactoring what do you thing about this:Instead of the ISpringContextLocator have ainterface
you can create a regular _expression_ to go from page=name to bookmarkablePage=name
that along with page aliases whill get you where you want to go
we are concentrating our efforts on 1.2. your request is pretty simple
to implement, but we are trying to figure out how to create pluggable
and
Hello all
when i load the firs page browser is redirected to a url that is like
/app;jsessionid=12324?path=1
there are any way to be redirected to samething like
bookmarkablePage=HomePage
thanks in advantage
---
SF.Net email is sponsored
There is no way for Wicket to remove jsessionid (at least no legal
way). It's your servlet container that appends it. When you support
cookies however, there should be no need to encode this id in the url,
and I think some servlet engines don't append it if this is the case.
Eelco
On 11/8/05,
No, I am not sure for all appservers, so I decided to abandon the
attempts for the most perfect URL ;-)) Because there will be only one
address which is screwed up after all, so I really don't care much (or
so I convinced myself).
I would say to pepone, forgeddaboudid ;-)
Michael.
On 11/8/05,
Hi,
I'm trying to use recompile code that uses PageableGridDataView which
used to work. The problem is that PageableGridDataView has a constructor
which takes in wicket.contrib.dataview.IDataProvider in its constructor
but HibernateDataProvider now extends
I don't know much about that package, but afaik the dataview project
will be dropped in favor of the extensions project.
Eelco
On 11/8/05, Gili [EMAIL PROTECTED] wrote:
Hi,
I'm trying to use recompile code that uses PageableGridDataView which
used to work. The problem is that
oops, not=now.
-Igor
On 11/8/05, Igor Vaynberg [EMAIL PROTECTED] wrote:
PageableGridDataView is not GridView in extensions. there are only
minor incompatibilities with the old dataview package so you should
have no problems migrating.
the dataview project is no longer in wicket-stuff cvs btw.
39 matches
Mail list logo
