[JBoss JIRA] Updated: (JBWS-1369) CTS: Error parsing jboss-web.xml
by Jason T. Greene (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1369?page=all ]
Jason T. Greene updated JBWS-1369:
----------------------------------
Summary: CTS: Error parsing jboss-web.xml (was: Error parsing jboss-web.xml)
> CTS: Error parsing jboss-web.xml
> --------------------------------
>
> Key: JBWS-1369
> URL: http://jira.jboss.com/jira/browse/JBWS-1369
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jaxws
> Reporter: Rajesh Rajasekaran
> Assigned To: Jason T. Greene
> Fix For: jbossws-2.0.0.CR2
>
>
> Test: com\sun\ts\tests\webservices\deploy\beanMirrorSEI
> The same error occurs with most of the webservices tests
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.4//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_4_0.dtd">
> <jboss-web>
> <security-domain>java:/jaas/cts</security-domain>
> <class-loading>
> <loader-repository>jboss.cts:loader=BeanMirrorSEI_web.war
> <loader-repository-config>java2ParentDelegation=false</loader-repository-config>
> </loader-repository>
> </class-loading>
> <webservice-description>
> <webservice-description-name>BeanMirrorSEI</webservice-description-name>
> <wsdl-publish-location>http://localhost:8180/BeanMirrorSEIWeb/ws4ee/beanMirrorSEI?WSDL</wsdl-publish-location>
> </webservice-description>
> </jboss-web>
> 2006-11-10 14:13:24,859 ERROR [org.jboss.deployment.JBossWebAppParsingDeployer] Error during deployment: jar:file:/C:/jboss-5.0.0.Beta/server/cts/tmp/jsr88/BeanMirrorSEI.ear!/BeanMirrorSEI_web.war
> org.jboss.deployers.spi.DeploymentException: Error parsing meta data BeanMirrorSEI_web.war/WEB-INF/jboss-web.xml
> at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
> at org.jboss.deployers.plugins.deployers.helpers.ObjectModelFactoryDeployer.parse(ObjectModelFactoryDeployer.java:87)
> at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.parse(AbstractParsingDeployer.java:145)
> Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: jar:file:/C:/DOCUME~1/RRAJAS~1/LOCALS~1/Temp/nestedjar23270.tmp!/WEB-INF/jboss-web.xml@15,13
> at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:164)
> at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:180)
> at org.jboss.deployers.plugins.deployers.helpers.ObjectModelFactoryDeployer.parse(ObjectModelFactoryDeployer.java:83)
> ... 58 more
> Caused by: org.xml.sax.SAXException: The content of element type "jboss-web" must match "(class-loading?,security-domain?,context-root?,virtual-host*,use-session-cookies?,replication-config?,resource-env-ref*,resource-ref*,security-role*,ejb-ref*,ejb-local-ref*,message-destination-ref*,message-destination*,webservice-description*,service-ref*,depends*,servlet*,authenticators*)". @ jar:file:/C:/DOCUME~1/RRAJAS~1/LOCALS~1/Temp/nestedjar23270.tmp!/WEB-INF/jboss-web.xml[15,13]
> at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:348)
> at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years
[JBoss JIRA] Updated: (JBWS-1373) CTS: Deployment problems with WebServiceContext tests
by Jason T. Greene (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1373?page=all ]
Jason T. Greene updated JBWS-1373:
----------------------------------
Summary: CTS: Deployment problems with WebServiceContext tests (was: Deployment problems with WebServiceContext tests)
> CTS: Deployment problems with WebServiceContext tests
> -----------------------------------------------------
>
> Key: JBWS-1373
> URL: http://jira.jboss.com/jira/browse/JBWS-1373
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jaxws
> Reporter: Jason T. Greene
> Fix For: jbossws-2.0.0.CR2
>
>
> 14:46:47,609 ERROR [JBossClientParsingDeployer] Error during deployment: jar:file:/C:/jboss-temp/jsr88/WSWebServiceContext_wsappclient_vehicle.ear!/WSWebServiceContext_wsappclient_vehicle_client.jar
> org.jboss.deployers.spi.DeploymentException: Error parsing meta data WSWebServiceContext_wsappclient_vehicle_client.jar/META-INF/jboss-client.xml
> Caused by: org.xml.sax.SAXException: Element type "port-component-ref" must be declared. @ jar:file:/c:/DOCUME~1/jgreene/LOCALS~1/Temp/nestedjar57375.tmp!/META-INF/jboss.xml[12,29]
> at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:348)
> at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
> at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
> at org.apache.xerces.impl.dtd.XMLDTDValidator.handleStartElement(Unknown Source)
> at org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
> at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
> at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
> at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
> at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:160)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years
[JBoss JIRA] Updated: (JBWS-1372) CTS: DOC/LIT wrapped fails to deploy / fails to create wrapper
by Jason T. Greene (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1372?page=all ]
Jason T. Greene updated JBWS-1372:
----------------------------------
Summary: CTS: DOC/LIT wrapped fails to deploy / fails to create wrapper (was: DOC/LIT wrapped fails to deploy / fails to create wrapper)
> CTS: DOC/LIT wrapped fails to deploy / fails to create wrapper
> --------------------------------------------------------------
>
> Key: JBWS-1372
> URL: http://jira.jboss.com/jira/browse/JBWS-1372
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jaxws
> Reporter: Heiko Braun
> Assigned To: Jason T. Greene
> Fix For: jbossws-2.0.0.CR2
>
>
> org.jboss.ws.WSException: Could not generate wrapper type: java.lang.jaxws.HashCode
> at org.jboss.ws.jaxws.DynamicWrapperGenerator.generate(DynamicWrapperGenerator.java:111)
> at org.jboss.ws.deployment.JSR181MetaDataBuilder.processWebMethod(JSR181MetaDataBuilder.java:530)
> at org.jboss.ws.deployment.JSR181MetaDataBuilder.processWebMethods(JSR181MetaDataBuilder.java:378)
> at org.jboss.ws.deployment.JSR181MetaDataBuilder.setupEndpointFromAnnotations(JSR181MetaDataBuilder.java:196)
> at org.jboss.ws.deployment.JSR181MetaDataBuilderEJB3.buildMetaData(JSR181MetaDataBuilderEJB3.java:75)
> at org.jboss.ws.deployment.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:104)
> Caused by: javassist.CannotCompileException: by java.lang.SecurityException: Prohibited package name: java.lang.jaxws
> at javassist.ClassPool.toClass(ClassPool.java:906)
> at javassist.ClassPool.toClass(ClassPool.java:846)
> at org.jboss.ws.jaxws.DynamicWrapperGenerator.generate(DynamicWrapperGenerator.java:107)
> ... 59 more
> Caused by: java.lang.SecurityException: Prohibited package name: java.lang.jaxws
> at java.lang.ClassLoader.preDefineClass(ClassLoader.java:479)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:614)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:465)
> 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:585)
> at javassist.ClassPool.toClass(ClassPool.java:898)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years
[JBoss JIRA] Updated: (JBWS-1371) CTS: Clarification: Accessing JAX-WS service from JNDI
by Jason T. Greene (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1371?page=all ]
Jason T. Greene updated JBWS-1371:
----------------------------------
Summary: CTS: Clarification: Accessing JAX-WS service from JNDI (was: Clarification: Accessing JAX-WS service from JNDI)
> CTS: Clarification: Accessing JAX-WS service from JNDI
> ------------------------------------------------------
>
> Key: JBWS-1371
> URL: http://jira.jboss.com/jira/browse/JBWS-1371
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jaxws
> Reporter: Heiko Braun
> Assigned To: Thomas Diesler
> Fix For: jbossws-2.0.0.CR2
>
>
> I am accessing a service (EJB3+JSR181) from JNDI. This fails with the following exception:
> Caused by: java.lang.IllegalArgumentException: The SEI does not implement java.rmi.Remote: org.jboss.test.ws.jaxws.samples.retail.OrderMgmt
> at org.jboss.ws.jaxrpc.ServiceObjectFactory.getObjectInstance(ServiceObjectFactory.java:274)
> at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304)
> at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1131)
> at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1148)
> Q1) Why is jaxrpc.ServiceObjectFactory being used?
> Q2) AFAIK the Remote interface is not required under EJB3
> So, is this approach wrong in gerneral, or do i miss something here?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years
[JBoss JIRA] Updated: (JBWS-1370) CTS: Cannot obtain xmlType for bare request/response object
by Jason T. Greene (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1370?page=all ]
Jason T. Greene updated JBWS-1370:
----------------------------------
Summary: CTS: Cannot obtain xmlType for bare request/response object (was: Cannot obtain xmlType for bare request/response object)
> CTS: Cannot obtain xmlType for bare request/response object
> -----------------------------------------------------------
>
> Key: JBWS-1370
> URL: http://jira.jboss.com/jira/browse/JBWS-1370
> Project: JBoss Web Services
> Issue Type: Bug
> Components: jaxws
> Environment: jaxws/api/javax_xml_ws/AsyncHandler/Client.java#HandleResponseJAXBTest_from_wsappclient
> Reporter: Thomas Diesler
> Assigned To: Jason T. Greene
> Fix For: jbossws-2.0.0.CR2
>
>
> 19:02:04,844 WARN [JSR181MetaDataBuilder] Cannot obtain xml type for: [xmlName={http://helloservice.org/types}HelloRequest,javaName=com.sun.ts.t...]
> 19:02:04,845 WARN [JSR181MetaDataBuilder] Cannot obtain xml type for: [xmlName={http://helloservice.org/types}HelloResponse,javaName=com.sun.ts....]
> 19:02:04,845 WARN [JSR181MetaDataBuilder] Cannot obtain xml type for: [xmlName={http://helloservice.org/types}HelloOneWayRequest,javaName=com.su...]
> private void populateXmlType(ParameterMetaData paramMetaData)
> {
> EndpointMetaData epMetaData = paramMetaData.getOperationMetaData().getEndpointMetaData();
> TypesMetaData types = epMetaData.getServiceMetaData().getTypesMetaData();
> JAXBRIContext jaxbCtx = getJAXBContext(epMetaData);
> QName xmlName = paramMetaData.getXmlName();
> QName xmlType = paramMetaData.getXmlType();
> Class javaType = paramMetaData.getJavaType();
> String javaName = paramMetaData.getJavaTypeName();
> if (xmlType == null)
> {
> xmlType = jaxbCtx.getTypeName(new TypeReference(xmlName, javaType));
> if (xmlType == null)
> log.warn("Cannot obtain xml type for: [xmlName=" + xmlName + ",javaName=" + javaName + "]");
>
> if (xmlType != null)
> {
> paramMetaData.setXmlType(xmlType);
> types.addTypeMapping(new TypeMappingMetaData(types, xmlType, javaName));
> }
> }
> }
> The stack relies on xmlType beeing available. Here I warn, but really an exception should be thrown when the xmlType cannot be derrived.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years