[JBoss AS7 Development] - Re: Load on startup is ignored - JaxWS webservice is always initialized first
12:49 a.m.
Jim Ma [http://community.jboss.org/people/jim.ma] 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/617278#617278
--------------------------------------------------------------
* Why is the ServletContextListener called when all Servlets are
instantiated?
You probably misundertood by the following webservice deployer output:
12:13:26,227 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder]
(MSC service thread 1-2) Add Service
id=HelloServlet
address= http://localhost:8080/helloServlet/HelloServlet
http://localhost:8080/helloServlet/HelloServlet
implementor=servlet.hello.helloservlet.HelloServletImpl
invoker=org.jboss.wsf.stack.cxf.InvokerJSE
serviceName={ http://helloservlet.hello.servlet/
http://helloservlet.hello.servlet/}HelloServletImplService
portName={ http://helloservlet.hello.servlet/
http://helloservlet.hello.servlet/}HelloServletImplPort
wsdlLocation=null
mtomEnabled=false
12:13:26,228 INFO [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service
thread 1-2) register: jboss.ws:context=helloServlet,endpoint=HelloServlet
12:13:29,986 INFO [stdout] (MSC service thread 1-2) HelloServlet is instantiated!
12:13:29,991 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC
service thread 1-2) Creating Service { http://helloservlet.hello.servlet/
http://helloservlet.hello.servlet/}HelloServletImplService from class
servlet.hello.helloservlet.HelloServlet
12:13:30,023 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-2) Setting
the server's publish address to be http://localhost:8080/helloServlet/HelloServlet
http://localhost:8080/helloServlet/HelloServlet
12:13:30,024 WARN [org.jboss.wsf.stack.cxf.resolver.JBossWSResourceResolver] (MSC
service thread 1-2) Cannot resolve resource: cxf
12:13:30,030 INFO [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service
thread 1-2) WSDL published to:
file:/home/jimma/x1/code/git-client/maerqiang-work/jboss-as/build/target/jboss-as-7.1.0.Alpha1-SNAPSHOT/standalone/data/wsdl/helloServlet.war/HelloServletImplService.wsdl
12:13:31,517 INFO [org.jboss.as.webservices.service.EndpointService] (MSC service thread
1-10) Starting service jboss.ws.endpoint.helloServlet.HelloServlet
As you see the
HelloServletImpl.class (configured in web.xml
<servlet-class>servlet.hello.helloservlet.HelloServletImpl</servlet-class>) is
not a real servlet class, the webservie deployer will modify the web.xml and start the
endpoint impl before the real servlet - org.jboss.wsf.stack.cxf.CXFServletExt which
servers the servlt transport initialize and start to work. These webservice deployers
which output above message are executed before the web deployer to create WebContext .
That's why you see it is executed after the HelloServlet is Initialized. But
ServletContextListener is actually executed as expected before the real servlets are
initialized. Here in your war file is after CXFServletExt and Startup are initialized.
* *Why is "<load-on-startup>" ignored when the
implementation differ only in the WS implementation?*
It is not ignored. The <load-on-startup> configured to HelloServlet is
passed to org.jboss.wsf.stack.cxf.CXFServletExt. I tried with your example it works
properly.
rushead wrote:
* Last but not least: What is the best and usual way to initialize a custom environment
for several servlets in a war file?
I did not get what you want to initialize from the source code(maybe I missed
something), so I am not sure if do the initialize work in a real servlet and inject
something with WebServiceContext can help. Here is some documentation about how to access
MessageContext and/or Http request and response:
http://cxf.apache.org/docs/servlet-transport.html
http://cxf.apache.org/docs/servlet-transport.html
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/617278#617278]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
5:44 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/617355#617355
--------------------------------------------------------------
Thank you for your response.
But I have some more questions:
Jim Ma schrieb:
> * *Why is "<load-on-startup>" ignored when the implementation differ
only in the WS implementation?*
>
It is not ignored. The <load-on-startup> configured to HelloServlet is passed to
org.jboss.wsf.stack.cxf.CXFServletExt. I tried with your example it works properly.
I think I misunderstood the difference between the "real" servlets and the
"fake" servlets.
Both mechanisms (<load-on-startup> and ServletContextListener#contextInitialized)
worked for me with JBoss AS 5.1 so that the HelloServlet (JaxWS implementation) was
instantiated after the ServletContextListner was called / after the StartupServlet was
initialized.
In my opinion it should not make a difference if I implement a "real" servlet
(using "implements Servlet") or using JaxWS to build a Webservice.
Jim Ma schrieb:
> rushead wrote:
> * Last but not least: What is the best and usual way to initialize a custom
environment for several servlets in a war file?
>
I did not get what you want to initialize from the source code(maybe I missed something),
so I am not sure if do the initialize work in a real servlet and inject something with
WebServiceContext can help. Here is some documentation about how to access MessageContext
and/or Http request and response: http://cxf.apache.org/docs/servlet-transport.html
http://cxf.apache.org/docs/servlet-transport.html
I am trying to initialize a
custom application context and resource management which is used in all my servlets and
webservices (sometimes even in the constructor to load the configuration).
The problem is, that i have to initialize the context/resource management before the
servlets and webservices are instantiated (of course).
What is the common way to solve this problem?
And why did it work in JBoss AS 5.1 and does not work anymore in the current AS 7?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/617355#617355]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
5:27 a.m.
Jim Ma [http://community.jboss.org/people/jim.ma] 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/617579#617579
--------------------------------------------------------------
As7 is built from scratch and there are a lot of changes in deployer and service
container. I understood your problem and will look at if we can change it to the same
behavior as in AS 5.1.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/617579#617579]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
7:04 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/617597#617597
--------------------------------------------------------------
This would be great, thanks.
But is there any other way to solve my problem?
Or what is the common way to call a custom environment initialization before the
initialization of the webservices and servlets has started?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/617597#617597]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
2:32 a.m.
Jim Ma [http://community.jboss.org/people/jim.ma] 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/617795#617795
--------------------------------------------------------------
If you do not have to call the custom initialization before the webservice constructor ,
this could help:
* call custom environment initialization in a ServletContextListener
* Get servletContext from injected webServiceContext like:
@WebService
public class HelloServletImpl implements HelloServlet {
@Resource
public WebServiceContext wsContext;
public HelloServletImpl() {
System.out.println("HelloServlet is instantiated!");
}
@Override
public String newOperation(final String in) {
// TODO Auto-generated method stub
ServletContext servletContext =
(ServletContext)
wsContext.getMessageContext().get(MessageContext.SERVLET_CONTEXT);
System.out.println(servletContext.getAttribute("TEST"));
return (String)servletContext.getAttribute("TEST");
}
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/617795#617795]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
3:41 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/617814#617814
--------------------------------------------------------------
Unfortunately that's exactly my problem.
I want to load the configuration (which is stored in an xml file) when the webservice is
constructed.
Therefore I need the already initialized custom environment...
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/617814#617814]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
5:04 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/617824#617824
--------------------------------------------------------------
Hi rushead,
the WS endpoints is actually started during the deployment phase, which ends with
rewriting (for POJO endpoints) [1] or creation (for EJB3 endpoints) of the webapp web.xml
descriptor and start of the web transport layer. The servlet stuff is indeed just the
transport layer/view of the webservice endpoint and is just the mean for serving HTTP
requests to the webservice endpoints. The endpoint is thus created regardless of /
independently from the servlet layer and the jbossws endpoint servlet delegates to the
actual ws endpoints at runtime.
Expecting the servlet context to be available when the POJO endpoint bean is instanciated
if unfortunately a wrong assumption here. Similarly, I bet you would not expect to have
the servlet stuff available when an EJB3 WS endpoint is created in the case of EJB3
endpoints.
So unless there's a specification requirement (and I really believe there's not
such req) mandating actually creating the endpoint after the web transport is up, this is
not going to be modified, as this a design decision and it granted multiple benefits. Btw,
AS6 was already based on this afair.
This said, you can probably achieve the behaviour you need differently, below are a couple
of idea:
- you can modify your ws endpoint impl to call a given method when the first invocation
comes; if your endpoint is being served on HTTP transport only, the servlet context and
such will for sure be available
- you could also provide a configuration lookup mechanism that do not rely on the servlet
init params (for instance lookup/read a conf or prop file in the deployment, use the
ServiceLoader API, etc) and read your configuration in a @PostConstruct annotated method
of the endpoint implementation
- if you still need to bound your endpoint creation to the servlet, you can have a custom
servlet that programmatically starts a WS endpoint, either by the JAXWS
Enpdoint.publish(..) API or through the EndpointPublisher API that is included in the
current AS 7.1.0.Alpha1-SNAPSHOT version (that's still to be released, sorry)
[1] your web.xml is rewritten by replacing the reference to the ws endpoint bean with the
actual jbossws endpoint servlet; the endpoint bean class is passed to the endpoint servlet
as a parameter
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/617824#617824]
Start a new discussion in JBoss AS7 Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&...]
4654
days inactive
4656
days old
jboss-dev-forums@lists.jboss.org
6 comments
3 participants
participants (3)
-
Alessio Soldano -
Jim Ma
-
rushead