[Design of JBoss Web Services] - Future directions for JBossWS
by karypid
Hello all,
I am writing to inquire what the plans for the future of JBossWS-Native are. As far as I could find on the net, this stack was born by forking Axis code and modifying it to achieve J2EE compliance and never got re-merged, thus forming a project of its own for quite some time now.
Recently though, JBoss was able to pass the J2EE TCK using JBossWS-CXF. I also read in an interview on DZone http://java.dzone.com/videos/mark-little-tech-chat?mz=3006-jboss with Mark Little, that you guys intend to stop doing everything "in house" and focus on using CXF as an officially supported stack in EAP 5:
anonymous wrote : DZone: At one point it seemed that JBoss was trying to build everything it needed within its own ecosystem. That seems to be changing though.
| Mark Little: ....... For instance, as I mentioned earlier, we're now using the Apache CXF project as our Web Services stack. We still maintain our own Web Services stack at the moment, but the aim is that CXF will become the default Web Services stack at some point in the future.
|
So, is JBossWS-Native going to stick around or is the long-term plan to gradually "drop" it?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249798#4249798
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249798
16 years, 7 months
[Design the new POJO MicroContainer] - Re: Web beans on top of Microcontainer deployment order
by alesj
Perhaps instead of directly extending existing Actions,
you could extract the over-lapping functionality into new super classes?
"kabir.khan(a)jboss.com" wrote :
| *** WebBeansPostConstructAction ???
| I need to invoke WBI.postConstruct()/preDestroy() from somewhere, but am unsure if I should do that as part of CREATE, START or if I need a new state. If I need a new state, where should that go?
|
I looks like you would need two new states.
POST_CONSTRUCT = after INSTANTAITE, before CONFIGURED (only @ install)
PRE_DESTROY = after CREATE, before START (only @ uninstall)
You can simply add new states to Controller, within some WB+MC singleton.
See DeployersImpl for example.
"kabir.khan(a)jboss.com" wrote :
|
| | public boolean resolve(Controller controller)
| | {
| | try
| | {
| | context.getManager().validate(injectionPoint);
| | setIDependOn(injectionPoint);
| | // addDependsOnMe(controller, context);
| | setResolved(true);
| | }
| | catch(ValidationException e)
| | {
| | setResolved(false);
| | }
| |
| | return isResolved();
| | }
| |
|
Pete, could we have here something that doesn't throw exception in order to see if it's resolved.
e.g.
| setResolved(context.getManager().canResolve(injectionPoint));
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249797#4249797
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4249797
16 years, 7 months