I want suggest a second approach for the same feature:
@Observer(String[] value, boolean create)
Where the "boolean create" indicate if that component should be create when it
not exists.
I dig a little on Seam code and conclude that this is very easy to do. This
information could be setted on
Done!
http://jira.jboss.org/jira/browse/JBSEAM-579
Thanks,
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992745#3992745
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992745
__
Add a feature request to JIRA, sounds like a good idea.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992683#3992683
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992683
___
I try this and it works good!
I alter Events from Seam Core to:
|private void eventProcessing(boolean create, String type, Object...
parameters)
|{
| log.debug("Processing event:" + type);
| List list = listeners.get(type);
| if (list!=null)
| {
|
I realize now that I misundestood the concept of this kind of event.
Originally, my idea was that I should create Components in one conversation
context and a raised event just reached this created components that observe it.
But, this doesn't work that way!
Reading the Seam code (this help a l
nice, very nice... now, my code can be much more loosely and pretty...
thanks a lot,
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986253#3986253
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986253
_
Events are processed in the scope of the conversation that raised them (except
for async events).
Anyway, the docs are outofdate, the latest releases do actually support
arbitrary event objects.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986220#3986220
