Cool! I hope you get in touch with Clint (Wicket), Peter (SE) and Shane (remoting) here an exchange ideas as I would image you share features (and challenges) between the projects...
Nice, I will mention this on our blog.
Yes. We shall exchange more ideas. Now I am
fightingwith the ConversationScope. I am referencing Wicket implementation and try to get some hints. I will keep posting here the results and issues met during the integration. Just in case, if need private email contact, here is the address: henrichen AT zkoss DOT org.
I'm prototyping with an API for a ConversationManager that will make integration with non-JSF frameworks a bit easier.
That is great. Can you notify me when available? Thanks.
first at all, I think ZK and WEld are both yery cool Frameworks.
In last weeks I played with them and created a Integration where conversations are also running know.
Yesterday i sent you those code snippets. I would be pleased, if you like it and want to publish it with zk or either propose a weld integration.
i think the most important issues when you think of refactoring ConversationManager should be:
- add lifecycle methods for creating and destroy transient conversations
- configuration of BeanStores backing indipendent of the context itself.
- a creation method for BeanStores
Last but not least i propose a lifecycle tracing concept, wich could be gerat when developing glue stuff.
Are you on the weld-dev discussion list? I thought we'd take it up there.
I think guys the integration is far from being done.I have been straggling to make the two wars to work with jboss 6 As final. The problems are various:
1)First i have a noclassdefound exception due to the AbstractMapContext don't exist.I add the dependency in my pom.xml.BUT then:
2)I get an error with the slf4j since core obviously is using a different version from the one being used
in JBoss. So that sounds to me in some kind of deadlock. As i have discussed with henrichen i am about to commit my findings in the wiki/issue tracker.
I think a better more clear separation and loosely coupling of jars should have taken place.I am really disappointed by jboss guys...since instead of going forward and create minimalistic dependencies frameworks as we move forward they tend to couple alot(i.e. check dependency in google things even in richfaces)...If we don't change that...spring is always a nice alternative and let me tell you that i manage to do what i wanted with spring and zk.But since weld is a jsr - 299 implementation, i would go for a better design.At your disposal for any clarification