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. -igor On Wed, Jun 17, 2009 at 9:36 PM, Joe Fawzy<[email protected]> wrote: > Hiyou mean: injecting webbeans conversation component in wicket component at > construction time > this is only what we can achieve with webbeans, as wicket component cannot > be webbeans components (wicket is unmanaged framework) > my idea is about native conversation support, which enable wicket component > to be the component and the target for injection in a natural wicket way > beside, why depending on external project when we have all the functionality > we need as wicket is stateful and each pagemap is a conversation(long one > which may be easily break down to smaller pieces) > > Joe > > > On Thu, Jun 18, 2009 at 7:22 AM, James Carman > <[email protected]>wrote: > >> There are a few folks working on implementing JSR-299 support for Wicket, >> which would provide support for conversation-scoped beans. I'm working on >> one currently and I believe that the jboss folks have one working too. >> >> On Thu, Jun 18, 2009 at 12:08 AM, Joe Fawzy <[email protected]> wrote: >> >> > Hican this functionality added to the standard wicket? >> > actually much of seam popularity came from supporting conversation >> > scope..., >> > so i think that adding explicit wicket support will have momentum >> > i think that having just a store for conversation objects will be a good >> > begin >> > then we may add apis like beginConversation, endConversation >> > ,joinConversation,mergeConversation >> ,suspendConversation,resumeConversation >> > and other concepts like workspace >> > what do u think? >> > Joe >> > >> > >> > On Thu, Jun 18, 2009 at 12:32 AM, Igor Vaynberg <[email protected] >> > >wrote: >> > >> > > only time will tell >> > > >> > > -igor >> > > >> > > On Wed, Jun 17, 2009 at 11:59 AM, Joe Fawzy<[email protected]> >> wrote: >> > > > thanks dearwill wicket continue to support pageMap beyond 1.4 or it >> is >> > > now a >> > > > deprecated feature? >> > > > thanks >> > > > Joe >> > > > >> > > > On Wed, Jun 17, 2009 at 9:56 PM, Igor Vaynberg < >> > [email protected] >> > > >wrote: >> > > > >> > > >> if the scope of your conversation is a browser window then its the >> > best >> > > >> choice. >> > > >> >> > > >> -igor >> > > >> >> > > >> On Wed, Jun 17, 2009 at 11:45 AM, Joe Fawzy<[email protected]> >> > wrote: >> > > >> > Hi dearthanks for the reply and for the code snippet >> > > >> > But, do u think that using pageMap is reliable or what.... >> > > >> > i mean , is using pageMap is a good solution or just a hack, work >> > > around >> > > >> > thanks >> > > >> > Joe >> > > >> > >> > > >> > On Wed, Jun 17, 2009 at 8:58 PM, Igor Vaynberg < >> > > [email protected] >> > > >> >wrote: >> > > >> > >> > > >> >> class mysession extends websesison { >> > > >> >> private map<string, map<object,object>> coversations; >> > > >> >> >> > > >> >> public map<object,object> getconversation(ipagemap pmap) { >> > > >> >> return conversations.get(pmap.getid()); >> > > >> >> } >> > > >> >> } >> > > >> >> >> > > >> >> -igor >> > > >> >> >> > > >> >> On Wed, Jun 17, 2009 at 10:29 AM, Joe Fawzy<[email protected]> >> > > wrote: >> > > >> >> > Hi alli need to implement something like a conversation scope >> in >> > > >> wicket >> > > >> >> > i know that wicket is stateful by default and i can pass object >> o >> > > from >> > > >> >> page >> > > >> >> > A -> page B >> > > >> >> > But if Object o in page A which -> page B -> page C -> page D >> -> >> > > page >> > > >> E >> > > >> >> > and i need Object o in page E ,that will be very tedious to >> pass >> > o >> > > all >> > > >> >> > throught the way from A ----> ..E >> > > >> >> > also if i need to pass a large number of objects between a set >> of >> > > >> pages >> > > >> >> > ,this will be a nightmare >> > > >> >> > >> > > >> >> > so How can i implement a Conversation object ala Session and >> > store >> > > >> these >> > > >> >> > objects there >> > > >> >> > >> > > >> >> > i thought of using the IPageMap as a key in this situation as >> it >> > > >> >> represent >> > > >> >> > an open browser window or tab ie. conversation, but in a >> previous >> > > mail >> > > >> ,i >> > > >> >> > 've been tald that it cannot be extended easily, and i cannot >> > > provide >> > > >> my >> > > >> >> own >> > > >> >> > factory for one >> > > >> >> > >> > > >> >> > so, any ideas about the conversation scope? >> > > >> >> > what do u think about the pageMap ? will it work? is it >> reliable? >> > > >> >> > can the core team provide some hooks to implement something >> like >> > > >> >> > IPageMapFactory? >> > > >> >> > >> > > >> >> > 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] >> > > >> > > >> > >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
