[JBossWS] - NullPointerException from JBossXSEntityResolver
by kazcor
Hi *,
I know, I'm going to open a second topic on this, although there's already a similar problem posted here: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110298#4110298.
However, in my case I'm using the opposite direction. I've set up a webservice using an underlying EJB(3) for the implementation. The SEI contains only one method, which uses a message that was compiled before from various schemas (containing UBL2,e-GIF) by using JAXB2.1. Once that webservice is deployed on JBoss he is trying to map all these classes back to XSDs and I receive the same NPE:
| java.lang.NullPointerException
| at org.jboss.ws.metadata.wsdl.xmlschema.JBossXSEntityResolver.getXMLInputSource(JBossXSEntityResolver.java:167)
| at org.jboss.ws.metadata.wsdl.xmlschema.JBossXSEntityResolver.resolveEntity(JBossXSEntityResolver.java:135)
| at org.apache.xerces.impl.XMLEntityManager.resolveEntity(Unknown Source)
| at org.apache.xerces.impl.xs.XMLSchemaLoader.resolveDocument(Unknown Source)
| at org.apache.xerces.impl.xs.traversers.XSDHandler.resolveSchema(Unknown Source)
| at org.apache.xerces.impl.xs.traversers.XSDHandler.constructTrees(Unknown Source)
| at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown Source)
| ....
|
I'm using JBoss4.2.2GA. Is this bug already confirmed?
I'm going to try to work around this problem by using a WSDL generated by wsprovide and doing wsconsume on it to receive the necessary interfaces for the implementation, but if that is really working, it's not a nice way of solving this issue.
Any help is highly appreciated :)
Thanks,
Max
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124794#4124794
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4124794
17 years, 1 month
[JBossWS] - Re: How can I use session sope in jbossws?
by froden
Thanks for your reply, mjhammel, Using the approach described in your links, I managed to get the session object. I can now set and retrieve variables from session as long as the client has the JSESSIONID http header field set correctly.
However, I still have some unresolved issues with this.
In my application, I have a JSF page where users can log in. The page uses a seam component, in which I have the following code (somewhat simplified):
@Stateless
| @Name("authenticator")
| public class AuthenticatorAction {
|
| @EJB
| ProfileDAO profileDAO;
|
| @RequestParameter
| String username;
|
| @RequestParameter
| String password;
|
| @In(required=false)
| @Out(required=false, scope=SESSION)
| private Profile authenticatedProfile;
|
| public String login() {
| Profile p = profileDAO.getUser(username, password);
| authenticatedProfile = profile;
| }
| }
This works fine, and the Profile object is put into the session scope (ie can be fetched in other seam components over different page loads etc).
The question is, how can I retreive the profile object in my web service? Doing a
session.getAttribute("authenticatedProfile")
does not work. In fact,
System.out.println((session.getValueNames()).length);
reveals that there are no variables stored in the session!
Any ideas?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124775#4124775
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4124775
17 years, 1 month
[JBossWS] - JBOSSWS 2.0.3 - Deplyoment Failed.
by zeeshan.javeed
Hi ,
I just shift to new JBOSSWS 2.0.3 from 2.0.2.
During the deployment.. I am getting this error.
11:52:04,482 DEBUG [EndpointMetaData] Configure SOAPBinding
11:52:04,503 ERROR [MainDeployer] Could not start deployment: file:/C:/Office/jboss-4.0.5.GA/server/default/deploy/ips-wipe.war/
java.lang.NoSuchMethodError: org.jboss.ws.metadata.config.CommonConfig.getRMMetaData()Lorg/jboss/ws/extensions/wsrm/config/RMConfig;
at org.jboss.ws.extensions.wsrm.server.RMDeploymentAspect.create(RMDeploymentAspect.java:52)
at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
at org.jboss.wsf.container.jboss40.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
at org.jboss.wsf.container.jboss40.DeployerInterceptor.start(DeployerInterceptor.java:90)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
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 $Proxy38.start(Unknown Source)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor59.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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 $Proxy8.deploy(Unknown Source)
Any idea,
why this happening ??
Although the wsdl file is published and i can call it in browser.
Regards,
Zeeshan
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124717#4124717
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4124717
17 years, 1 month
[JBossWS] - Wstools WSDL generation problem
by ibrahim_theo
All,
I have developed existing web services based on JAX-RPC1.1 with Jboss403.
I've decided migration of jboss to 4.2.1 and jbossws2.0.2.
The existing WSDLs were generated with wscompile.
I decided to use wstools to regenerate them.
I am getting the following error:
Exception in thread "main" java.lang.IllegalArgumentException: Could not locate a constructor with the following types: class com.un
.imis.common.exception.IMISWsException [class [Ljava.lang.String;, class [Ljava.lang.String;, class java.lang.String]
at org.jboss.ws.tools.schema.SchemaTypeCreator.getComplexTypeForJavaException(SchemaTypeCreator.java:781)
at org.jboss.ws.tools.schema.SchemaTypeCreator.getType(SchemaTypeCreator.java:270)
at org.jboss.ws.tools.schema.SchemaTypeCreator.generateType(SchemaTypeCreator.java:133)
at org.jboss.ws.tools.JavaToXSD.generateForSingleType(JavaToXSD.java:114)
at org.jboss.ws.tools.helpers.JavaToWSDLHelper.generateType(JavaToWSDLHelper.java:360)
at org.jboss.ws.tools.helpers.JavaToWSDLHelper.generateTypesForXSD(JavaToWSDLHelper.java:161)
at org.jboss.ws.tools.helpers.JavaToWSDLHelper.processOperation(JavaToWSDLHelper.java:109)
at org.jboss.ws.tools.wsdl.WSDLGenerator.processEndpoint(WSDLGenerator.java:114)
at org.jboss.ws.tools.helpers.JavaToWSDLHelper.processEndpoint(JavaToWSDLHelper.java:166)
at org.jboss.ws.tools.wsdl.WSDLGenerator.processService(WSDLGenerator.java:404)
at org.jboss.ws.tools.wsdl.WSDLGenerator.generate(WSDLGenerator.java:452)
at org.jboss.ws.tools.JavaToWSDL11.handleJavaToWSDLGeneration(JavaToWSDL11.java:210)
at org.jboss.ws.tools.JavaToWSDL11.generate(JavaToWSDL11.java:162)
at org.jboss.ws.tools.JavaToWSDL.generate(JavaToWSDL.java:322)
at org.jboss.ws.tools.helpers.ToolsHelper.handleJavaToWSDLGeneration(ToolsHelper.java:121)
at org.jboss.ws.tools.WSTools.process(WSTools.java:143)
at org.jboss.ws.tools.WSTools.generate(WSTools.java:69)
at org.jboss.ws.tools.WSTools.generate(WSTools.java:123)
at org.jboss.ws.tools.WSTools.main(WSTools.java:58)
any idea?
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4124617#4124617
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4124617
17 years, 1 month