Yes, some annotation for conversation would be nice.
I think it would be nice also to see an attractive example application
(separated from others) where Orchestra is used in conjunction with
-Facelets
-Spring 2.5, and where every bean is configured with annotations, conversation
and session
Hi!
I think it would be nice also to see an attractive example
application (separated from others) where Orchestra is used in
conjunction with
Absolutely, you might not being able to imagine how much I'd appreaciate
such a demo application.
Any plan to volunteer? :-)
-minimal
Hi,
On Feb 6, 2008 9:08 AM, alberto [EMAIL PROTECTED] wrote:
Yes, some annotation for conversation would be nice.
I think it would be nice also to see an attractive example application
(separated from others) where Orchestra is used in conjunction with
here is a simple demo that shows some
Hi!
Are there any plans about migration over Spring 2.5 in Orchestra?
Orchestra itself is compatible with Spring 2.5. We use this combination
in our projects.
I'd like to see if Spring 2.5 can simplify orchestra configuration and
if we can now completely declare bean throught annotations.
What
Are there any plans about migration over Spring 2.5 in Orchestra?
I'd like to see if Spring 2.5 can simplify orchestra configuration and if we
can now completely declare bean throught annotations.
And do you think it is possible to have proxy scoped bean using annotation?
Alberto Gori
Mario Ivankovits [EMAIL PROTECTED] schrieb:
Hi!
Are there any plans about migration over Spring 2.5 in Orchestra?
Orchestra itself is compatible with Spring 2.5. We use this combination
in our projects.
I'd like to see if Spring 2.5 can simplify orchestra configuration and
if we
I presume you mean marking beans with something like
@Conversation(lifetime=access, name=myConversation)
or
@Scope(scope=conversation.access, name=myConversation)
or
@Conversation(scope=access, name=myConversation)
Yes that would be cool.
It's debatable whether the annotation should be
7 matches
Mail list logo
