You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Joe Fawzy <jo...@gmail.com> on 2009/06/17 19:29:46 UTC
Conversation scope in wicket
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
Re: Conversation scope in wicket
Posted by Joe Fawzy <jo...@gmail.com>.
Hi Igor
On Wed, Jun 17, 2009 at 8:58 PM, Igor Vaynberg <ig...@gmail.com>wrote:
> class mysession extends websesison {
> private map<string, map<object,object>> coversations;
>
> public map<object,object> getconversation(ipagemap pmap) {
> return conversations.get(pmap.getid());
> }
> }
in your last code line , do you mean pmap.getName() instead of pmap.getId()
as i cannot find a public getId() in ipagemap
thanks
Joe
>
>
> -igor
>
> On Wed, Jun 17, 2009 at 10:29 AM, Joe Fawzy<jo...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Conversation scope in wicket
Posted by James Carman <jc...@carmanconsulting.com>.
On Thu, Jun 18, 2009 at 8:27 AM, Carl-Eric Menzel
<cm...@users.bitforce.com> wrote:
> > The idea of a "conversation" has been around for a long time. It's
> > called a stateful session bean.
>
> You have a point there. But I think this is all provided by Wicket
> already - You have components and models that perfectly encapsulate all
> this. Basically this is about the lifecycle of the data needed for a
> unit of work from the user's point of view. If you have a flow of
> pages, or wizard steps, or whatever, you have a defined starting point
> where you can, for example, create a model. And then you go to the next
> step and pass this model along. Once you're finished, you just drop the
> references.
>
> Or am I missing something here?
Yes, Wicket does have great support for stateful programming. That's
why I love Wicket! However, if I can run Wicket inside a "container"
that supports JSR-299 and I can have my web beans injected into my
Wicket components/pages as proxies so that I'm always talking to the
right bean at the right time and I don't have to worry about all that
state crap (at least in the web tier), then I think that's a big win.
>
> Carl-Eric
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Conversation scope in wicket
Posted by Carl-Eric Menzel <cm...@users.bitforce.com>.
On Thu, 18 Jun 2009 08:10:33 -0400
James Carman <jc...@carmanconsulting.com> wrote:
> On Thu, Jun 18, 2009 at 7:46 AM, Carl-Eric Menzel
> <cm...@users.bitforce.com> wrote:
> > Then you already have an object that your components can work on.
> > Put that in a Wicket model and enjoy. My point is this: You either
> > have existing business code that supports conversations - then you
> > don't need Wicket conversations, you need to write your components
> > so they work with the existing code's notion of a conversation.
>
> Wicket needs to understand when it needs to resume a previously-begun
> conversation. The business logic can't know that by itself. The UI
> has to provide a bit of help.
Yes of course. That's what I meant by "write your components so they
work with your existing code".
> The idea of a "conversation" has been around for a long time. It's
> called a stateful session bean.
You have a point there. But I think this is all provided by Wicket
already - You have components and models that perfectly encapsulate all
this. Basically this is about the lifecycle of the data needed for a
unit of work from the user's point of view. If you have a flow of
pages, or wizard steps, or whatever, you have a defined starting point
where you can, for example, create a model. And then you go to the next
step and pass this model along. Once you're finished, you just drop the
references.
Or am I missing something here?
Carl-Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Conversation scope in wicket
Posted by James Carman <jc...@carmanconsulting.com>.
On Thu, Jun 18, 2009 at 7:46 AM, Carl-Eric Menzel
<cm...@users.bitforce.com> wrote:
> Then you already have an object that your components can work on. Put
> that in a Wicket model and enjoy. My point is this: You either have
> existing business code that supports conversations - then you don't need
> Wicket conversations, you need to write your components so they work
> with the existing code's notion of a conversation.
Wicket needs to understand when it needs to resume a previously-begun
conversation. The business logic can't know that by itself. The UI
has to provide a bit of help.
>
> Or you don't have a "business" conversation, and the whole conversation
> thing is just something for UI workflow. Then you should not have it in
> the business code. Instead, write components and models so that they
> keep all the state they need for this "conversation" where they need
> it. I don't think there needs to be a special abstraction for this,
> you'd be much better off with keeping state as appropriate for your use
> case.
The idea of a "conversation" has been around for a long time. It's
called a stateful session bean.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Conversation scope in wicket
Posted by Carl-Eric Menzel <cm...@users.bitforce.com>.
On Thu, 18 Jun 2009 07:21:36 -0400
James Carman <jc...@carmanconsulting.com> wrote:
> > I fully agree. Conversation scope is a kludge for a broken model,
> > and in the end nothing more than a specialized form of global
> > variables.
>
> To which model are you referring?
Not a model in the Wicket sense, but the model of application
development where you throw everything into a big bag (e.g. the
session, or any other such scope).
> > Just put your state into the appropriate page or component instances
> > and/or models, and you get *any* scope you need, for free.
>
> Your business logic might not know anything about page/component
> instances, but it may support "conversations."
Then you already have an object that your components can work on. Put
that in a Wicket model and enjoy. My point is this: You either have
existing business code that supports conversations - then you don't need
Wicket conversations, you need to write your components so they work
with the existing code's notion of a conversation.
Or you don't have a "business" conversation, and the whole conversation
thing is just something for UI workflow. Then you should not have it in
the business code. Instead, write components and models so that they
keep all the state they need for this "conversation" where they need
it. I don't think there needs to be a special abstraction for this,
you'd be much better off with keeping state as appropriate for your use
case.
I may have been unclear in my earlier message, does this make more
sense?
Carl-Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Conversation scope in wicket
Posted by James Carman <jc...@carmanconsulting.com>.
On Thu, Jun 18, 2009 at 7:07 AM, Carl-Eric Menzel
<cm...@users.bitforce.com> wrote:
>
> +1
>
> I fully agree. Conversation scope is a kludge for a broken model, and in
> the end nothing more than a specialized form of global variables.
To which model are you referring?
>
> Just put your state into the appropriate page or component instances
> and/or models, and you get *any* scope you need, for free.
Your business logic might not know anything about page/component
instances, but it may support "conversations."
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Conversation scope in wicket
Posted by Carl-Eric Menzel <cm...@users.bitforce.com>.
+1
I fully agree. Conversation scope is a kludge for a broken model, and in
the end nothing more than a specialized form of global variables.
Just put your state into the appropriate page or component instances
and/or models, and you get *any* scope you need, for free.
Carl-Eric
On Thu, 18 Jun 2009 01:55:26 -0700 (PDT)
svenmeier <sv...@meiers.net> wrote:
>
> What is this 'conversation' all about?
>
> It doesn't seem to be a known concept in any GUI guideline I know
> (e.g. Apple's Human Interface Guidelines). Neither does wikipedia
> list it under http://en.wikipedia.org/wiki/GUI_widget.
>
> This is what wikipedia is saying about Seam's conversation: 'The
> default Seam context is conversation which can span multiple pages
> and usually spans the whole business flow, from start to finish.'
> This seems to describe a
> http://en.wikipedia.org/wiki/Wizard_(software) .
>
> IMHO 'conversation' is a buzzword invented for those who still think
> a web UI consists of a sequence of HTML pages only.
> Back in 2000 the same guys invented 'mvc-2' and told us that a UI can
> be built on actions only.
>
> Just my rant (worth 2 cents or less).
>
> Back to Wicket and wizards:
> For a wizard I'd suggest to use a single Wicket page, replacing
> components as you step through it.
> Note that Wicket extensions provide a wizard component, but you can
> easily roll your own implementation.
>
> Sven
>
> > 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Conversation scope in wicket
Posted by Johan Compagner <jc...@gmail.com>.
+1
that whole api like beginConversation, end etc
just looks to me like set/get methods on session.
Or and that is in my eyes better is to transport the conversation object (1
object not many) from 1 page to the next
or use as below 1 page and just replace panels. And then the page model
object is the conversation object
johan
On Thu, Jun 18, 2009 at 10:55, svenmeier <sv...@meiers.net> wrote:
>
> What is this 'conversation' all about?
>
> It doesn't seem to be a known concept in any GUI guideline I know (e.g.
> Apple's Human Interface Guidelines). Neither does wikipedia list it under
> http://en.wikipedia.org/wiki/GUI_widget.
>
> This is what wikipedia is saying about Seam's conversation: 'The default
> Seam context is conversation which can span multiple pages and usually
> spans
> the whole business flow, from start to finish.'
> This seems to describe a http://en.wikipedia.org/wiki/Wizard_(software) .
>
> IMHO 'conversation' is a buzzword invented for those who still think a web
> UI consists of a sequence of HTML pages only.
> Back in 2000 the same guys invented 'mvc-2' and told us that a UI can be
> built on actions only.
>
> Just my rant (worth 2 cents or less).
>
> Back to Wicket and wizards:
> For a wizard I'd suggest to use a single Wicket page, replacing components
> as you step through it.
> Note that Wicket extensions provide a wizard component, but you can easily
> roll your own implementation.
>
> Sven
>
> > 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
>
> --
> View this message in context:
> http://www.nabble.com/Conversation-scope-in-wicket-tp24078377p24088943.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Conversation scope in wicket
Posted by svenmeier <sv...@meiers.net>.
What is this 'conversation' all about?
It doesn't seem to be a known concept in any GUI guideline I know (e.g.
Apple's Human Interface Guidelines). Neither does wikipedia list it under
http://en.wikipedia.org/wiki/GUI_widget.
This is what wikipedia is saying about Seam's conversation: 'The default
Seam context is conversation which can span multiple pages and usually spans
the whole business flow, from start to finish.'
This seems to describe a http://en.wikipedia.org/wiki/Wizard_(software) .
IMHO 'conversation' is a buzzword invented for those who still think a web
UI consists of a sequence of HTML pages only.
Back in 2000 the same guys invented 'mvc-2' and told us that a UI can be
built on actions only.
Just my rant (worth 2 cents or less).
Back to Wicket and wizards:
For a wizard I'd suggest to use a single Wicket page, replacing components
as you step through it.
Note that Wicket extensions provide a wizard component, but you can easily
roll your own implementation.
Sven
> 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
--
View this message in context: http://www.nabble.com/Conversation-scope-in-wicket-tp24078377p24088943.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Conversation scope in wicket
Posted by Joe Fawzy <jo...@gmail.com>.
Hi alli am working on a prototype which i think will convince you that
conversation is an important concept, it is very onject oriented as wicket
is and has many use cases
On Thu, Jun 18, 2009 at 7:38 AM, Igor Vaynberg <ig...@gmail.com>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.
yes, u r right, wicket can'nt be everything for everyone ,but the question
is how much this hook thing is the responsibility of wicket
do you really think wicket is only ui framework?with no scopes.... so why u
support sessions? conversation is much like sessions, it is just narrowwer
Thanks
Joe
>
> -igor
>
> On Wed, Jun 17, 2009 at 9:36 PM, Joe Fawzy<jo...@gmail.com> 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
> > <jc...@carmanconsulting.com>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 <jo...@gmail.com>
> 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 <
> igor.vaynberg@gmail.com
> >> > >wrote:
> >> >
> >> > > only time will tell
> >> > >
> >> > > -igor
> >> > >
> >> > > On Wed, Jun 17, 2009 at 11:59 AM, Joe Fawzy<jo...@gmail.com>
> >> 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 <
> >> > igor.vaynberg@gmail.com
> >> > > >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<jo...@gmail.com>
> >> > 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 <
> >> > > igor.vaynberg@gmail.com
> >> > > >> >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<
> joewicket@gmail.com>
> >> > > 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: users-unsubscribe@wicket.apache.org
> >> > > >> >> For additional commands, e-mail: users-help@wicket.apache.org
> >> > > >> >>
> >> > > >> >>
> >> > > >> >
> >> > > >>
> >> > > >>
> >> ---------------------------------------------------------------------
> >> > > >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> > > >> For additional commands, e-mail: users-help@wicket.apache.org
> >> > > >>
> >> > > >>
> >> > > >
> >> > >
> >> > >
> ---------------------------------------------------------------------
> >> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> > > For additional commands, e-mail: users-help@wicket.apache.org
> >> > >
> >> > >
> >> >
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Conversation scope in wicket
Posted by James Carman <jc...@carmanconsulting.com>.
#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<ja...@googlemail.com> 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
> <jc...@carmanconsulting.com>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 <jo...@gmail.com> wrote:
>> >
>> > Hi all
>> >
>> > On Thu, Jun 18, 2009 at 7:44 AM, James Carman
>> > <jc...@carmanconsulting.com>wrote:
>> >
>> > > On Thu, Jun 18, 2009 at 12:38 AM, Igor Vaynberg <
>> igor.vaynberg@gmail.com>
>> > > 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: users-unsubscribe@wicket.apache.org
>> > > For additional commands, e-mail: users-help@wicket.apache.org
>> > >
>> > >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Conversation scope in wicket
Posted by Joe Fawzy <jo...@gmail.com>.
Hi dearfirst of all, why add another dependency,just for conversation
handling, while we have in wicket a strong ground for it
note: jsr299 is a big spec with a somehow complex lifecycle(which may not be
compatible with that of wicket) and really complicated bean resolution
strategy
second: wicket components are not 299 beans, wicket is an unmanaged
framework , u must create the components urself, not by the framework, which
is a requirement for jsr299
what can be done with web beans, is to inject its objects in wicket
components BUT u cannot manage wicket components as web beans , and for
example inject them or handle there lifecycle
Joe
On Fri, Jun 19, 2009 at 10:43 AM, janneru <ja...@googlemail.com> 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
> <jc...@carmanconsulting.com>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 <jo...@gmail.com> wrote:
> > >
> > > Hi all
> > >
> > > On Thu, Jun 18, 2009 at 7:44 AM, James Carman
> > > <jc...@carmanconsulting.com>wrote:
> > >
> > > > On Thu, Jun 18, 2009 at 12:38 AM, Igor Vaynberg <
> > igor.vaynberg@gmail.com>
> > > > 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: users-unsubscribe@wicket.apache.org
> > > > For additional commands, e-mail: users-help@wicket.apache.org
> > > >
> > > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
Re: Conversation scope in wicket
Posted by janneru <ja...@googlemail.com>.
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
<jc...@carmanconsulting.com>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 <jo...@gmail.com> wrote:
> >
> > Hi all
> >
> > On Thu, Jun 18, 2009 at 7:44 AM, James Carman
> > <jc...@carmanconsulting.com>wrote:
> >
> > > On Thu, Jun 18, 2009 at 12:38 AM, Igor Vaynberg <
> igor.vaynberg@gmail.com>
> > > 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: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Conversation scope in wicket
Posted by James Carman <jc...@carmanconsulting.com>.
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 <jo...@gmail.com> wrote:
>
> Hi all
>
> On Thu, Jun 18, 2009 at 7:44 AM, James Carman
> <jc...@carmanconsulting.com>wrote:
>
> > On Thu, Jun 18, 2009 at 12:38 AM, Igor Vaynberg <ig...@gmail.com>
> > 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: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Conversation scope in wicket
Posted by Joe Fawzy <jo...@gmail.com>.
Hi all
On Thu, Jun 18, 2009 at 7:44 AM, James Carman
<jc...@carmanconsulting.com>wrote:
> On Thu, Jun 18, 2009 at 12:38 AM, Igor Vaynberg <ig...@gmail.com>
> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Conversation scope in wicket
Posted by James Carman <jc...@carmanconsulting.com>.
I will. I'm just keeping notes on what all listeners I'd like to see. :)
On Thu, Jun 18, 2009 at 1:08 AM, Igor Vaynberg<ig...@gmail.com> wrote:
> jira it up.
>
> -igor
>
> On Wed, Jun 17, 2009 at 9:44 PM, James
> Carman<jc...@carmanconsulting.com> wrote:
>> On Thu, Jun 18, 2009 at 12:38 AM, Igor Vaynberg <ig...@gmail.com> 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).
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Conversation scope in wicket
Posted by Igor Vaynberg <ig...@gmail.com>.
jira it up.
-igor
On Wed, Jun 17, 2009 at 9:44 PM, James
Carman<jc...@carmanconsulting.com> wrote:
> On Thu, Jun 18, 2009 at 12:38 AM, Igor Vaynberg <ig...@gmail.com> 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).
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Conversation scope in wicket
Posted by James Carman <jc...@carmanconsulting.com>.
On Thu, Jun 18, 2009 at 12:38 AM, Igor Vaynberg <ig...@gmail.com> 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).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Conversation scope in wicket
Posted by Igor Vaynberg <ig...@gmail.com>.
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<jo...@gmail.com> 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
> <jc...@carmanconsulting.com>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 <jo...@gmail.com> 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 <igor.vaynberg@gmail.com
>> > >wrote:
>> >
>> > > only time will tell
>> > >
>> > > -igor
>> > >
>> > > On Wed, Jun 17, 2009 at 11:59 AM, Joe Fawzy<jo...@gmail.com>
>> 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 <
>> > igor.vaynberg@gmail.com
>> > > >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<jo...@gmail.com>
>> > 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 <
>> > > igor.vaynberg@gmail.com
>> > > >> >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<jo...@gmail.com>
>> > > 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: users-unsubscribe@wicket.apache.org
>> > > >> >> For additional commands, e-mail: users-help@wicket.apache.org
>> > > >> >>
>> > > >> >>
>> > > >> >
>> > > >>
>> > > >>
>> ---------------------------------------------------------------------
>> > > >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> > > >> For additional commands, e-mail: users-help@wicket.apache.org
>> > > >>
>> > > >>
>> > > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> > > For additional commands, e-mail: users-help@wicket.apache.org
>> > >
>> > >
>> >
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Conversation scope in wicket
Posted by Joe Fawzy <jo...@gmail.com>.
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
<jc...@carmanconsulting.com>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 <jo...@gmail.com> 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 <igor.vaynberg@gmail.com
> > >wrote:
> >
> > > only time will tell
> > >
> > > -igor
> > >
> > > On Wed, Jun 17, 2009 at 11:59 AM, Joe Fawzy<jo...@gmail.com>
> 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 <
> > igor.vaynberg@gmail.com
> > > >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<jo...@gmail.com>
> > 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 <
> > > igor.vaynberg@gmail.com
> > > >> >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<jo...@gmail.com>
> > > 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: users-unsubscribe@wicket.apache.org
> > > >> >> For additional commands, e-mail: users-help@wicket.apache.org
> > > >> >>
> > > >> >>
> > > >> >
> > > >>
> > > >>
> ---------------------------------------------------------------------
> > > >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > >> For additional commands, e-mail: users-help@wicket.apache.org
> > > >>
> > > >>
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > > For additional commands, e-mail: users-help@wicket.apache.org
> > >
> > >
> >
>
Re: Conversation scope in wicket
Posted by James Carman <jc...@carmanconsulting.com>.
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 <jo...@gmail.com> 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 <igor.vaynberg@gmail.com
> >wrote:
>
> > only time will tell
> >
> > -igor
> >
> > On Wed, Jun 17, 2009 at 11:59 AM, Joe Fawzy<jo...@gmail.com> 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 <
> igor.vaynberg@gmail.com
> > >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<jo...@gmail.com>
> 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 <
> > igor.vaynberg@gmail.com
> > >> >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<jo...@gmail.com>
> > 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: users-unsubscribe@wicket.apache.org
> > >> >> For additional commands, e-mail: users-help@wicket.apache.org
> > >> >>
> > >> >>
> > >> >
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > >> For additional commands, e-mail: users-help@wicket.apache.org
> > >>
> > >>
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> > For additional commands, e-mail: users-help@wicket.apache.org
> >
> >
>
Re: Conversation scope in wicket
Posted by Joe Fawzy <jo...@gmail.com>.
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 <ig...@gmail.com>wrote:
> only time will tell
>
> -igor
>
> On Wed, Jun 17, 2009 at 11:59 AM, Joe Fawzy<jo...@gmail.com> 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 <igor.vaynberg@gmail.com
> >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<jo...@gmail.com> 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 <
> igor.vaynberg@gmail.com
> >> >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<jo...@gmail.com>
> 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: users-unsubscribe@wicket.apache.org
> >> >> For additional commands, e-mail: users-help@wicket.apache.org
> >> >>
> >> >>
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Conversation scope in wicket
Posted by Igor Vaynberg <ig...@gmail.com>.
only time will tell
-igor
On Wed, Jun 17, 2009 at 11:59 AM, Joe Fawzy<jo...@gmail.com> 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 <ig...@gmail.com>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<jo...@gmail.com> 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 <igor.vaynberg@gmail.com
>> >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<jo...@gmail.com> 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: users-unsubscribe@wicket.apache.org
>> >> For additional commands, e-mail: users-help@wicket.apache.org
>> >>
>> >>
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Conversation scope in wicket
Posted by Joe Fawzy <jo...@gmail.com>.
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 <ig...@gmail.com>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<jo...@gmail.com> 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 <igor.vaynberg@gmail.com
> >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<jo...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> >> For additional commands, e-mail: users-help@wicket.apache.org
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Conversation scope in wicket
Posted by Igor Vaynberg <ig...@gmail.com>.
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<jo...@gmail.com> 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 <ig...@gmail.com>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<jo...@gmail.com> 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: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Conversation scope in wicket
Posted by Joe Fawzy <jo...@gmail.com>.
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 <ig...@gmail.com>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<jo...@gmail.com> 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: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
Re: Conversation scope in wicket
Posted by Igor Vaynberg <ig...@gmail.com>.
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<jo...@gmail.com> 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: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org