[Brian Hammond]

I am running MyEclipse 8.5 on Linux to develop web services using JBoss 4.3.0.

When I click on “Launch SOAP Web Services Explorer” nothing happens — the explorer doesn’t open. I’ve checked that my web service is deployed. What am I doing wrong? Is there some setting I need to set to get the explorer to work?

I have a client app that I’m using to query a simple service. The wsdl validates when I create the web service client, and all the files seem to be created. However, when I run the client, I get this error:
” com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html;charset=utf-8 Supported ones are: [text/xml]”
I’ve examined all the xml files and I don’t see any references to html anywhere. This is puzzling, because it was working earlier today. Have I inadvertently changed some MyEclipse setting or is this a glitch in JBoss?

Thank you for your help,
Brian

[support-shalini]

Brian,
Are there any errors logged in the log file, located at workspace dir > .metadata > .log, when you launch SOAP web service explorer? Please clear your log file, save it and then launch the SOAP explorer to get the relevant errors.

” com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html;charset=utf-8 Supported ones are: [text/xml]”

This could be caused when using soap11. Can you try changing the binding to 12 as suggested in the following link –
1. http://old.nabble.com/Unsupported-Content-Type:-text-xml–charset%3D%22utf-8%22-td22676562.html
Let me know if that works for you.

[Brian Hammond]

The log file says there’s no local browser, which is probably true. No big deal; I can write small test clients that work under Tomcat. On the second problem: I haven’t found where to specify the version of soap yet. Tomcat works just fine, but the same client fails when I use Jboss. I’m thinking that my edition of Jboss (4.3.0) may be the problem. Possibly it only accepts soap1.1. Still digging on that one.

Thanks for the help,
Brian

[support-shalini]

Brian,
I could not replicate this at my end using JBoss 4.2.3GA. The same client worked as expected on both tomcat and JBoss.
Can you list out the steps in detail to replicate your issue?

[Brian Hammond]

I found the problem. When I tried to connect to Jboss, I was getting back an html page with an error message. This wasn’t xml, so I got an error that it was invalid content. I used Fiddler to take a look at the html and found out that my web service hadn’t deployed completely. I don’t have that fixed yet, but at least I’m closer.

Thanks for the help,
Brian

[support-shalini]

Brian,

web service hadn’t deployed completely

Are there any errors in log file when deploying the webservice?

[Brian Hammond]

I found some errors at the time that the deploy was taking place.
2010-05-28 07:36:46,727 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner] Incomplete Deployment listing:

— Incompletely deployed packages —
org.jboss.deployment.DeploymentInfo@3bce0f22 { url=file:/home/bhammond/RTSOA/JBoss/JBoss-SOA-4.3.0_GA/jboss-as/server/default/deploy/Leg2.war/ }
deployer: MBeanProxyExt[jboss.web:service=WebServer]
status: Deployment FAILED reason: URL file:/home/bhammond/RTSOA/JBoss/JBoss-SOA-4.3.0_GA/jboss-as/server/default/deploy/Leg2.war/ deployment failed
state: FAILED
watch: file:/home/bhammond/RTSOA/JBoss/JBoss-SOA-4.3.0_GA/jboss-as/server/default/deploy/Leg2.war/WEB-INF/web.xml
altDD: null
lastDeployed: 1275046592058
lastModified: 1274987451000
mbeans:

— MBeans waiting for other MBeans —
ObjectName: jboss.web.deployment:war=Leg2.war,id=1003360034
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/home/bhammond/RTSOA/JBoss/JBoss-SOA-4.3.0_GA/jboss-as/server/default/deploy/Leg2.war/ deployment failed

— MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM —
ObjectName: jboss.web.deployment:war=Leg2.war,id=1003360034
State: FAILED
Reason: org.jboss.deployment.DeploymentException: URL file:/home/bhammond/RTSOA/JBoss/JBoss-SOA-4.3.0_GA/jboss-as/server/default/deploy/Leg2.war/ deployment failed

Those were the first errors, then there were a few more a little bit later. I don’t know if they’re related.
2010-05-28 07:36:46,775 INFO [org.apache.coyote.http11.Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
2010-05-28 07:36:54,957 INFO [org.hibernate.impl.SessionFactoryObjectFactory] Bound factory to JNDI name: java:/hibernate/MonitoringSessionFactory
2010-05-28 07:36:54,957 WARN [org.hibernate.impl.SessionFactoryObjectFactory] InitialContext did not implement EventContext
2010-05-28 08:37:30,234 INFO [org.jboss.web.tomcat.service.TomcatDeployer] deploy, ctxPath=/Leg2, warUrl=…/deploy/Leg2.war/
2010-05-28 08:37:30,294 ERROR [STDERR] May 28, 2010 8:37:30 AM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing
2010-05-28 08:37:30,981 ERROR [STDERR] May 28, 2010 8:37:30 AM com.sun.xml.ws.transport.http.servlet.WSServletDelegate <init>
INFO: WSSERVLET14: JAX-WS servlet initializing
2010-05-28 08:37:51,623 ERROR [STDERR] May 28, 2010 8:37:51 AM com.sun.xml.ws.transport.http.servlet.WSServletDelegate doPost
SEVERE: caught throwable
java.lang.NoClassDefFoundError: com/sun/xml/messaging/saaj/soap/AttachmentPartImpl

[Brian Hammond]

I installed JBoss 5.1.0. It’s giving me a different set of errors and warnings:
2010-06-01 09:23:09,138 WARN [org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator] (ResourceDiscoveryComponent.invoker.daemon-2) Cannot create String name from non-Simple property: ManagedProperty{JNDIName,JNDIName,metaType=SimpleMetaType:java.lang.String}, value=null
2010-06-01 09:23:09,144 WARN [org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator] (ResourceDiscoveryComponent.invoker.daemon-2) Cannot create String name from non-Simple property: ManagedProperty{JNDIName,JNDIName,metaType=SimpleMetaType:java.lang.String}, value=null
2010-06-01 09:23:27,591 INFO [org.hibernate.validator.Version] (http-0.0.0.0-8080-4) Hibernate Validator 3.1.0.GA
2010-06-01 09:23:27,601 INFO [org.hibernate.annotations.common.Version] (http-0.0.0.0-8080-4) Hibernate Commons Annotations 3.1.0.GA
2010-06-01 09:39:24,986 WARN [org.jboss.wsf.container.jboss50.deployer.JAXWSDeployerHookPreJSE] (HDScanner) Cannot load servlet class: com.sun.xml.ws.transport.http.servlet.WSServlet
2010-06-01 09:39:25,065 INFO [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner) deploy, ctxPath=/Leg2
2010-06-01 09:39:25,089 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/Leg2]] (HDScanner) Error configuring application listener of class com.sun.xml.ws.transport.http.servlet.WSServletContextListener
java.lang.ClassNotFoundException: com.sun.xml.ws.transport.http.servlet.WSServletContextListener
This was just after I installed, so I haven’t moved anything from its install location.

[support-shalini]

Brian,

java.lang.NoClassDefFoundError: com/sun/xml/messaging/saaj/soap/AttachmentPartImpl

Can you try the workaround given in the following link –
http://community.jboss.org/message/339896#339896
Let me know how that works for you.

[Brian Hammond]

I tried copying saaj-impl.jar and saaj.jar to the client directory, but that didn’t help. I ended up re-installing JBoss, which seems to have solved the problem. Somehow, I must have gotten a bad build the first time.
Thanks for your help,
Brian

[support-shalini]

Brian,

I ended up re-installing JBoss, which seems to have solved the problem.

Good to know that you are all set.
Do let us know if you have any issues.

[Author]

Posts