[Design the new POJO MicroContainer] - In/Un callbacks should be happening at Install
by adrian@jboss.org
The In/Uncallbacks were setup to happen at the Configured on the thing being
registered into, this is the wrong default.
We shouldn't be installing into a registry until it has had chance to
go through its lifecycle. e.g. create() can be used to validate configuration is correct
(no missing or inconsistent properties) and fail if there is a problem.
Or the registry may need to do extra work before receiving registrations,
possibly based on the value of two parameters passed during the config stage.
I've changed the default state to be Installed (this is the "no surprises" setting).
If somebody wants it to happen earlier, then can always change it in the xml
or the annotation.
Further, there were are ZERO tests of changing whenRequired and dependentState
for the callbacks.
I created one for changing the dependentState=Instantiated
(fortunately it works :-), but this obviously needs to be tested more systematically.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129159#4129159
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129159
18 years, 1 month
[Design the new POJO MicroContainer] - In/Un callbacks should be happening at Install
by adrian@jboss.org
The In/Uncallbacks were setup to happen at the Configured on the thing being
registered into, this is the wrong default.
We shouldn't be installing into a registry until it has had chance to
go through its lifecycle. e.g. create() can be used to validate configuration is correct
(no missing or inconsistent properties) and fail if there is a problem.
Or the registry may need to do extra work before receiving registrations,
possibly based on the value of two parameters passed during the config stage.
I've changed the default state to be Installed (this is the "no surprises" setting).
If somebody wants it to happen earlier, then can always change it in the xml
or the annotation.
Further, there were are ZERO tests of changing whenRequired and dependentState
for the callbacks.
I created one for changing the dependentState=Instantiated
(fortunately it works :-), but this obviously needs to be tested more systematically.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129158#4129158
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129158
18 years, 1 month
[Design of POJO Server] - Re: EJB/War deployer ordering problem
by pete.muir@jboss.org
Carlo explained to me why this no longer works. In essence, the spec says that if you are accessing EJBs from a servlet, then you must declare your EJBs in web.xml (this is true for all other EJB3 implementations).
JBoss EJB3/AS4/AS4.2 provided an extension to this, such that EJBs were available in global JNDI, and you didn't have to type them all out in web.xml. This was a (nice) piece of value add that JBoss EJB3 provided, and Seam took advantage of.
Carlo, correct me if I'm wrong :)
So, taking this forward - without this, there are no Seam examples that are guaranteed to work in AS5. We'll add a jboss5 configuration to the port of booking example to jee5 so that we have at least one example that runs. And I guess we start converting our examples over to be non-EJB3 so that they run on both JBoss 4.2 and 5.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4129088#4129088
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4129088
18 years, 1 month