#1, I didn't know about it. #2, I wanted to get familiar with JSR-299, so having to write an integration is a pretty good way to get "down and dirty." :)
On Fri, Jun 19, 2009 at 3:43 AM, janneru<[email protected]> wrote: > hi james&joe, > > which are the issues with clint popetz's current work on the webbeans-wicket > integration (already contained in the webbeans preview) that you would write > your own? > > cheers, uwe. > > > On Thu, Jun 18, 2009 at 8:05 PM, James Carman > <[email protected]>wrote: > >> JSR-299 is somewhat of a moving target right now, so it's hard to stay >> up-to-date with it. I'm mainly working with the OpenWebBeans folks on >> it. >> >> On Thu, Jun 18, 2009 at 2:03 PM, Joe Fawzy <[email protected]> wrote: >> > >> > Hi all >> > >> > On Thu, Jun 18, 2009 at 7:44 AM, James Carman >> > <[email protected]>wrote: >> > >> > > On Thu, Jun 18, 2009 at 12:38 AM, Igor Vaynberg < >> [email protected]> >> > > wrote: >> > > > >> > > > you are free to implement this as an open source addition to wicket. >> > > > there is wicketstuff or googlecode or sf.net where you can host it. >> > > > >> > > > wicket is a ui framework and conversational scope management falls >> > > > outside wicket's scope. it is our job to provide the hooks to make >> > > > such things possible, not to provide an implementation. >> > > >> > > And, those hooks are very nice. I would only ask for some more >> > > listener registering opportunities (like for listening to request >> > > cycle events like begin/end rather than having to implement your own >> > > request cycle). >> > >> > >> > Yes this is a much needed functionality >> > i think we may cooperate in that thing >> > can u start another mail discussion suggesting ur needs , and make >> everyone >> > participate >> > Thanks >> > Joe >> > >> > >> > >> > > >> > > >> > > --------------------------------------------------------------------- >> > > To unsubscribe, e-mail: [email protected] >> > > For additional commands, e-mail: [email protected] >> > > >> > > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
