[JBoss AS7 Development] - Re: Load on startup is ignored - JaxWS webservice is always initialized first
4:43 p.m.
rushead [http://community.jboss.org/people/rushead] created the discussion
"Re: Load on startup is ignored - JaxWS webservice is always initialized first"
To view the discussion, visit: http://community.jboss.org/message/617919#617919
--------------------------------------------------------------
Thank you very much.
Now I understand the behavior, and the differences between 5.1 and 7 :)
I'm using the @PostConstruct annotation now, which works fine for me.
My only problem now is (in my special case), that I think the webservice should be
destroyed if the configuration can not be loaded in the @PostConstruct method.
Is there any way to invoke that the webservice should be distroyed (within the
@PostConstruct method)?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/617919#617919]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
5:12 p.m.
Alessio Soldano [http://community.jboss.org/people/asoldano] created the discussion
"Re: Load on startup is ignored - JaxWS webservice is always initialized first"
To view the discussion, visit: http://community.jboss.org/message/617931#617931
--------------------------------------------------------------
rushead wrote:
Thank you very much.
Now I understand the behavior, and the differences between 5.1 and 7 :)
No
problem :-)
I'm using the @PostConstruct annotation now, which works fine for
me.
My only problem now is (in my special case), that I think the webservice should be
destroyed if the configuration can not be loaded in the @PostConstruct method.
Is there any way to invoke that the webservice should be distroyed (within the
@PostConstruct method)?
mmh... not really. Basically, you're deploying a war
unit, so the lifecycle of the stuff in there is controlled by that unit being deployed and
undeployed. You might throw an exception in the @PostConstruct annotated method, but I
guess that would cause the whole unit deployment to fail (not sure though, this should be
verified).
That might come with some additional complexity, but this requirement would suggest trying
the Endpoint publish API approach; it seems you really need to programmatically control
the ws endpoint lifecycle.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/617931#617931]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
12:32 p.m.
rushead [http://community.jboss.org/people/rushead] created the discussion
"Re: Load on startup is ignored - JaxWS webservice is always initialized first"
To view the discussion, visit: http://community.jboss.org/message/618038#618038
--------------------------------------------------------------
I now throw an Exception in the @PostConstruct.
It does not causes the failure of the whole deployment, which is now a good solution for
me.
The only thing which irritates me is that I am only allowed to declare that the method
throws "Exception", I'm not allowed to declare a custom implementation of
Exception (in my case "ConfigurationException)".
Caused by: org.jboss.ws.common.injection.InjectionException: Method annotated with
@interface javax.annotation.PostConstruct annotation cannot throw checked exceptions:
public void servlet.hello.helloservlet.HelloServletImpl.initSettings() throws
servlet.hello.helloservlet.exceptions.ConfigurationException
at
org.jboss.ws.common.injection.finders.ReflectionUtils.assertNoCheckedExceptionsAreThrown(ReflectionUtils.java:185)
at
org.jboss.ws.common.injection.finders.AbstractPostConstructPreDestroyAnnotatedMethodFinder.validate(AbstractPostConstructPreDestroyAnnotatedMethodFinder.java:67)
at
org.jboss.ws.common.injection.finders.PostConstructMethodFinder.validate(PostConstructMethodFinder.java:46)
at
org.jboss.ws.common.injection.finders.AbstractPostConstructPreDestroyAnnotatedMethodFinder.validate(AbstractPostConstructPreDestroyAnnotatedMethodFinder.java:35)
at
org.jboss.ws.common.reflection.AbstractClassProcessor.process(AbstractClassProcessor.java:54)
at
org.jboss.ws.common.injection.InjectionHelper.callPostConstructMethod(InjectionHelper.java:169)
at
org.jboss.ws.common.invocation.InvocationHandlerJAXWS.onEndpointInstantiated(InvocationHandlerJAXWS.java:71)
at
org.jboss.ws.common.invocation.AbstractInvocationHandlerJSE.init(AbstractInvocationHandlerJSE.java:63)
at
org.jboss.ws.common.invocation.AbstractInvocationHandlerJSE.invoke(AbstractInvocationHandlerJSE.java:97)
at org.jboss.wsf.stack.cxf.AbstractInvoker._invokeInternal(AbstractInvoker.java:169)
... 32 more
That's no problem, I just don't know why "Exception" is not a catched
exception...
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/618038#618038]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
7:04 p.m.
Alessio Soldano [http://community.jboss.org/people/asoldano] created the discussion
"Re: Load on startup is ignored - JaxWS webservice is always initialized first"
To view the discussion, visit: http://community.jboss.org/message/618187#618187
--------------------------------------------------------------
http://download.oracle.com/javaee/5/api/javax/annotation/PostConstruct.html
http://download.oracle.com/javaee/5/api/javax/annotation/PostConstruct.html
"the method must not throw a checked exception"
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/618187#618187]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
8:58 a.m.
rushead [http://community.jboss.org/people/rushead] created the discussion
"Re: Load on startup is ignored - JaxWS webservice is always initialized first"
To view the discussion, visit: http://community.jboss.org/message/618281#618281
--------------------------------------------------------------
I know that I'm not allowed to throw a checked exception.
What is irritating me is that I am allowed to declare "throws Exception" - I
thought only Exceptions which extend RuntimException are unchecked exceptions. Therefore
the superclass "Exception" should be a checked exception too.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/618281#618281]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
10:59 a.m.
Alessio Soldano [http://community.jboss.org/people/asoldano] created the discussion
"Re: Load on startup is ignored - JaxWS webservice is always initialized first"
To view the discussion, visit: http://community.jboss.org/message/618298#618298
--------------------------------------------------------------
Well, this is not really an issue then ;-) I mean, you're not allowed to throw checked
exception, so I don't see anything wrong in you not being allowed to throw your
ConfigurationException unless it's a RuntimeException.
We need to check if you can actually declare "throws Exception" and go with
that, in any case that's an edge case. The code for the validation in any case is as
follows:
public static void assertNoCheckedExceptionsAreThrown(final Method method, Class<?
extends Annotation> annotation)
{
Class<?>[] declaredExceptions = method.getExceptionTypes();
for (int i = 0; i < declaredExceptions.length; i++)
{
Class<?> exception = declaredExceptions[i];
if (!exception.isAssignableFrom(RuntimeException.class))
{
throw new InjectionException(BundleUtils.getMessage(bundle,
"METHOD_CANNOT_THROW_CHECKED_EXCEPTIONS", new Object[]{
getAnnotationMessage(annotation) , method}));
}
}
}
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/618298#618298]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
11:13 a.m.
rushead [http://community.jboss.org/people/rushead] created the discussion
"Re: Load on startup is ignored - JaxWS webservice is always initialized first"
To view the discussion, visit: http://community.jboss.org/message/618303#618303
--------------------------------------------------------------
Alessio Soldano schrieb:
We need to check if you can actually declare "throws Exception" and go with
that, in any case that's an edge case.
Yes, it works.
That's the way I implemented it now (which does not cause an Exception when the war is
deployed):
@PostConstruct
public void initSettings() throws Exception {
// here I am throwing my ConfigurationException if the xml cannot be
read/parsed
}
If i declare my custom (catched) Exception it throws Exception I posted above:
@PostConstruct
public void initSettings() throws ConfigurationException {
// here I am throwing my ConfigurationException if the xml cannot be
read/parsed
}
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/618303#618303]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4906
days inactive
4908
days old
jboss-dev-forums@lists.jboss.org
6 comments
2 participants
participants (2)
-
Alessio Soldano -
rushead