[jboss-user] [JBoss Web Services] - JBoss EJB unable invoke webservices by using their class implementation

Douglas Oviche do-not-reply at jboss.com
Mon Nov 8 11:01:13 EST 2010


Douglas Oviche [http://community.jboss.org/people/douglasoviche] created the discussion

"JBoss EJB unable invoke webservices by using their class implementation"

To view the discussion, visit: http://community.jboss.org/message/570095#570095

--------------------------------------------------------------
Hi there guys, 
I am a JEE Architect in Rome Italy and I was engaged to design, architect and deploy a distributed enterprise system based on EJB, JPA and Webservices.
The webservice architecture is based on CXF WS and the entire system must be must be deployed on jboss-5.1.0.GA.
I've used Maven to generate my webservices and they have been created properly by using "wsdl2java". 
 
All webservice endpoints are deployed on different providers machines so that if one wants to make use of these services
that one has to implement its own package by using the WSDLs made available by these different providers.
 
So, as I mentioned already we've decide to generate the whole services by using "wsdl2java" in our pom.xml configuration and pointing at
the WSDL files location. Every single service has been created perfectly.
 
We've also been able to deploy the whole WS package onto apache-tomcat-6.0.18 to test services endpoints, everything is pretty working.
Then, we have created a package of EJB3 where they are just SessionFacade components and each of these ejb provides its own public service(Method)
and within their public services they use the webservice implementation obtained from the maven generation process.
 
All these enterprise beans have been deployed and made available, they are properly invoked by servlets that we are using as test
to simultate the real clients making request onto the jboss platform to request for these services.
 
The whole picture is:
 
1- Webservices CXF package have been created and deployed on tomcat.
   (Spring configuration has displayed the correct webservice creation on tomcat web server)
2- Enterprise Java Beans have been deployed on jboss-5.1.0.GA
   (They are supposed to invoked webservices implementation by using the generated class representing the webservice implementation
    @javax.jws.WebService)
 
3- A testing servlet(Invokes ejb on jboss as)
 
The problem we are facing now is that when servlets invoke a specific enterprise javabeans from apache-tomcat-6.0.18 to jboss-5.1.0.GA
we get the following error:
 
com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/plain Supported ones are: [text/xml]
 
 
Honestly, I would see a better design, deploying these webservices(CXF) on jboss to cut off one of the artifacts or partipants
in terms of number of servers making part of the whole design.
 
My view is:
 
1- WebService(CXF) package to be deployed on Jboss.
2- Enterprise Java Beans which use the webserives implementations to provide these services onto our clients.
3- Servlets to provide testing units in order to mock and simulate future clients requests and traffic.
 
This is it!!  this is how I see things in a proper design solution
 
 
We sadly stuck on this and it's frustating the way things are turning.
We do really appreciate any kind of help by any one of you to tackle this problem.
 
Sincerely
 
Douglas
 
 
 
 
Hi there guys, 
I am a JEE Architect in Rome Italy and I was engaged to design, architect and deploy a distributed enterprise system based on EJB, JPA and Webservices.
The webservice architecture is based on CXF WS and the entire system must be must be deployed on jboss-5.1.0.GA.
I've used Maven to generate my webservices and they have been created properly by using "wsdl2java". 

All webservice endpoints are deployed on different providers machines so that if one wants to make use of these services
that one has to implement its own package by using the WSDLs made available by these different providers.

So, as I mentioned already we've decide to generate the whole services by using "wsdl2java" in our pom.xml configuration and pointing at
the WSDL files location. Every single service has been created perfectly.

We've also been able to deploy the whole WS package onto apache-tomcat-6.0.18 to test services endpoints, everything is pretty working.
Then, we have created a package of EJB3 where they are just SessionFacade components and each of these ejb provides its own public service(Method)
and within their public services they use the webservice implementation obtained from the maven generation process.

All these enterprise beans have been deployed and made available, they are properly invoked by servlets that we are using as test
to simultate the real clients making request onto the jboss platform to request for these services.

The whole picture is:

1- Webservices CXF package have been created and deployed on tomcat.
   (Spring configuration has displayed the correct webservice creation on tomcat web server)
2- Enterprise Java Beans have been deployed on jboss-5.1.0.GA
   (They are supposed to invoked webservices implementation by using the generated class representing the webservice implementation
    @javax.jws.WebService)

3- A testing servlet(Invokes ejb on jboss as)

The problem we are facing now is that when servlets invoke a specific enterprise javabeans from apache-tomcat-6.0.18 to jboss-5.1.0.GA
we get the following error:

*com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/plain Supported ones are: [text/xml]*


Honestly, I would see a better design, deploying these webservices(CXF) on jboss to cut off one of the artifacts or partipants
in terms of number of servers making part of the whole design.

My view is:

1- WebService(CXF) package to be deployed on Jboss.
2- Enterprise Java Beans which use the webserives implementations to provide these services onto our clients.
3- Servlets to provide testing units in order to mock and simulate future clients requests and traffic.

This is it!!  this is how I see things in a proper design solution


We sadly stuck on this and it's frustating the way things are turning.
We do really appreciate any kind of help by any one of you to tackle this problem.

Sincerely

Douglas
--------------------------------------------------------------

Reply to this message by going to Community
[http://community.jboss.org/message/570095#570095]

Start a new discussion in JBoss Web Services at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2044]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-user/attachments/20101108/e320e668/attachment-0001.html 


More information about the jboss-user mailing list