[Design of POJO Server] - Re: Getting the whole cause stack of the deployment exceptio
by pete.muir@jboss.org
"alesj" wrote : "pete.muir(a)jboss.org" wrote :
| | Also, it would be useful to have the name of the MC bean which threw the exception (as we get in contextsInError) - this allows me to discard all non WB related exceptions.
| |
| MC bean name == ControllerContext::getName ;-)
| Where ControllerContext is a parameter here:
|
| | void handleException(T exception, ControllerContext context);
| |
Oops, going blind ;-)
anonymous wrote : "pete.muir(a)jboss.org" wrote :
| | So, what is the best way to attach an exception handler?
| |
| Simply define a WBNotificationListener in some -jboss-beans.xml
| and it will be automagically picked up by MC and added to DeployersImpl.
|
| "pete.muir(a)jboss.org" wrote :
| | Can we add something to the PS API for this?
| |
| No.
| And that's not what Adrian and me are saying PS should do.
| OK, it already has this DeploymentManager, but this looks like it doesn't expose enough.
| It should be the ManagedDeployment that should be able to give you the right exception, no matter how wrapped it is.
|
| Or if MD is not the right place, something else should. Scott, Emanuel?
|
Got it.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248429#4248429
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248429
16 years, 5 months
[Design of POJO Server] - Re: Getting the whole cause stack of the deployment exceptio
by alesj
"pete.muir(a)jboss.org" wrote :
| Also, it would be useful to have the name of the MC bean which threw the exception (as we get in contextsInError) - this allows me to discard all non WB related exceptions.
|
MC bean name == ControllerContext::getName ;-)
Where ControllerContext is a parameter here:
| void handleException(T exception, ControllerContext context);
|
"pete.muir(a)jboss.org" wrote :
| So, what is the best way to attach an exception handler?
|
Simple define a WBNotificationListener in some -jboss-beans.xml
and it will be automagically picked up by MC and added to DeployersImpl.
"pete.muir(a)jboss.org" wrote :
| Can we add something to the PS API for this?
|
No.
And that's not what Adrian and me are saying PS should do.
OK, it already has this DeploymentManager, but this looks like it doesn't expose enough.
It should be the ManagedDeployment that should be able to give you the right exception, no matter how wrapped it is.
Or if MD is not the right place, something else should. Scott, Emanuel?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248426#4248426
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248426
16 years, 5 months
[Design of POJO Server] - Re: Java EE inter-module accessibility for Web Beans
by alesj
"pete.muir(a)jboss.org" wrote :
| Note that the graph can only be changed during deployment, at runtime it is static and we can cache the transitive closure of BDAs a BDA can access which means we have low overhead.
|
I'm still not sure this is sufficient.
Afais we need two distinct BDAs methods
(a) one that is used at initialization -> non-circular
(b) one that exposes accessible BDAs from a current BDA
This way a user could use (b) to examine current BDA and its accessible BDAs for potential WB match; injection points, types, whatever exists in WB, ...
"pete.muir(a)jboss.org" wrote :
| Great. We will add some TCK tests soon to verify this deployment structure, so we'll get results then :-)
I think the best approach is to get some test to fail/expose some issues you cannot handle with the current impl,
and I'll have a look and properly implement that.
The architecture is now in place to easily swap the behavior,
I might even port back the old-new impl you reverted if I see it fits,
or I'll do a complete new hack . :-)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4248416#4248416
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4248416
16 years, 5 months