[JBossWS] - Deployment failure
by l.gh
Hi guys,
I'm now deploying my POJO style EJB3 as a webservice. And it can be done successfully on Jboss4.0.5 but seriously it failed on Jboss4.2.1. I'm going to find a solution by Google but seems no similar way to solve it. Could anybody of you experts give me an opinion please?
Here I attached logs pushed into Jboss console.
| 12:21:09,330 ERROR [MainDeployer] Could not create deployment: file:/C:/devenv/jboss-4.2.0.GA/server/janes-dev/deploy/jm-lmi-place-ejb.jar
| org.jboss.deployment.DeploymentException: Cannot create service endpoint; - nested throwable: (java.lang.IllegalStateException: Cannot build JAXB context)
| at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
| at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:83)
| at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
| at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy34.create(Unknown Source)
| at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy9.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
| Caused by: java.lang.IllegalStateException: Cannot build JAXB context
| at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.createJAXBContext(JAXWSMetaDataBuilder.java:879)
| at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:128)
| at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:49)
| at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderEJB3.buildMetaData(JAXWSMetaDataBuilderEJB3.java:77)
| at org.jboss.ws.core.server.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:92)
| at org.jboss.ws.integration.jboss42.DeployerInterceptor.createServiceEndpoint(DeployerInterceptor.java:127)
| at org.jboss.ws.integration.jboss42.DeployerInterceptorEJB.createServiceEndpoint(DeployerInterceptorEJB.java:43)
| at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:78)
| ... 28 more
| Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts of IllegalAnnotationExceptions
| java.util.List is an interface, and JAXB can't handle interfaces.
| this problem is related to the following location:
| at java.util.List
|
| at com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:66)
| at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:361)
| at com.sun.xml.bind.v2.runtime.JAXBContextImpl.<init>(JAXBContextImpl.java:217)
| at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:76)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:76)
| at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.createJAXBContext(JAXWSMetaDataBuilder.java:875)
| ... 35 more
|
Source code looks like:
| @Remote
| @WebService
| @SOAPBinding(style=Style.RPC)
| public interface PlaceOperator {
| public List getList(HashMap map);
| }
|
| @Stateless
| @WebService(endpointInterface = "com.janes.discoveryxml.ejb.PlaceOperator")
| public class PlaceOperatorBean implements PlaceOperator{
|
| public List getList(HashMap map) {
| xxx
| return null;
| }
|
| }
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096014#4096014
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096014
16 years, 8 months
[JBossWS] - Re: Web seervice with authentication and wsconsume
by Christy
anonymous wrote : Yes, you need to also specify the authMethod and transportGuarantee. You can also take a look at the samples, in particular the jaxws-samples-context features this
I'm sorry, I'm here again. I still have the same problem, WSDL pritected with password.
Please look at my code once again:
Web service code:
@WebService
@SOAPBinding(style = SOAPBinding.Style.RPC)
@WebContext(authMethod = "BASIC", transportGuarantee="NONE", secureWSDLAccess = false)
@SecurityDomain("e2edmwsSecurity")
@Stateless
public class e2edm_metadata_ws implements e2edmnwsInterface{
}
web.xml file:
<servlet-name>e2edm_metadata_ws</servlet-name>
<servlet-class>metadata.e2edm.e2edm_metadata_ws</servlet-class>
<servlet-mapping>
<servlet-name>e2edm_metadata_ws</servlet-name>
<url-pattern>/e2edmws</url-pattern>
</servlet-mapping>
<security-constraint>
<web-resource-collection>
<web-resource-name>e2edm_metadata_ws_security</web-resource-name>
<url-pattern>/</url-pattern>
<http-method>POST</http-method>
</web-resource-collection>
<auth-constraint>
<role-name>ws</role-name>
</auth-constraint>
</security-constraint>
<login-config>
<auth-method>BASIC</auth-method>
<realm-name>e2edmwsSecurity</realm-name>
</login-config>
<security-role>
<role-name>ws</role-name>
</security-role>
jbossweb.xml:
<jboss-web>
<security-domain>java:/jaas/e2edmwsSecurity</security-domain>
</jboss-web>
Why I still have WSDL with password? Thank you!!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095895#4095895
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4095895
16 years, 8 months