[JBoss JIRA] Commented: (JBWS-1172) Support schema validation for incoming/outgoing messages
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1172?page=comments#action_12407573 ]
Thomas Diesler commented on JBWS-1172:
--------------------------------------
ant -Dtest=org.jboss.test.ws.jaxws.jbws1172.JBWS1172TestCase one-test
> Support schema validation for incoming/outgoing messages
> --------------------------------------------------------
>
> Key: JBWS-1172
> URL: http://jira.jboss.com/jira/browse/JBWS-1172
> Project: JBoss Web Services
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: jbossws-native
> Reporter: Thomas Diesler
> Assigned To: Thomas Diesler
> Fix For: jbossws-native-2.0.4
>
>
> I am trying to use JBOSSWS 1.0.2. and JBOSSAS-4.0.4GA
> I am starting with a WSDL file that contains a schema. I used WSTOOLS to generate the appropriate artifacts
> I would like to use DOCUMENT/LITERAL wrapped style and I would like to turn on schema validation of my XML instances against a schema defined in the WSDL (on receipt of the message the server does the validation ?).
> Looking through the sources, I see that JAXBDeserializer (jbossws-core.jar) calls JAXBUnmarshallerImpl which calls UnmarshallerImpl (jboss-xml-binding.jar) which does the parsing of the XML.
> I do not see any call to UnmarshallerImpl.setSchemaValidation in this call graph. Should this be called to turn on to do Schema Validation ? If so how and where ?
> Is Schema Validation for Document/Literal something that JBOSSWS 1.0.2 supports ?
> How does one turn on XML Schema validation in JBOSSWS ?
--
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
16 years, 9 months
[JBoss JIRA] Created: (JBWS-1702) JAXWS type inheritance
by Thomas Diesler (JIRA)
JAXWS type inheritance
----------------------
Key: JBWS-1702
URL: http://jira.jboss.com/jira/browse/JBWS-1702
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: integration-jbws
Reporter: Thomas Diesler
Fix For: jbossws-2.1.0
I have a problem with the new JBossWS-1.2.1.GA in JBoss 4.2.0.GA and inheritance.
To describe this problem first I have to describe my code structure:
For an example I have three classes (ClassA, ClassB and ClassC). ClassC inherits of ClassB and ClassB inherits of ClassA (ClassA --> ClassB --> ClassC). Now I have a webservice method that returns ClassB. In this method an instance of ClassC is being created and returned. This was not a problem in the former JBossWS version (and also in the other J2EE 4 styled webservices) but now in JBossWS 1.2 I only get returned an object of ClassB but I supposed to get an obejct of ClassC.
Code:
public class ClassA {
private String propA;
// here setter and getter for propA
......
}
public class ClassB extends ClassA {
private String propB;
// here setter and getter for propB
......
}
public class ClassC extends ClassC {
private String propC;
// here setter and getter for propC
......
}
@WebService
@SOAPBinding( style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL, parameterStyle = SO
APBinding.ParameterStyle.WRAPPED )
public class MyWebService {
@WebMethod()
public ClassB getClassB() {
ClassC classC = new ClassC();
classC.setPropA("propA");
return classC;
}
/**
* --> this method is only used to publish ClassC otherwise it is not known
* in this webservice
*/
@WebMethod()
public ClassC getClassC() {
ClassC classC = new ClassC();
classC.setPropA("propA");
return classC;
}
}
}
Now I call getClassB() and the result that I got is an object of ClassB and not of ClassC.
What can I do to get an object of ClassC. I also looked at the returned SOAP message and there you can see that only informations about the ClassB instance are submitted. In JBoss 4.0.5 (JBossWS1.0.3) the SOAP message contains the type of the returned object and all data are being submitted correctly.
I also tried the SOAP parameter style BARE but nothing changed. And whenI use RPC/Literal then I get an error in the .NET Client that an instance of ClassB was expected but got an instance of ClassC. I also tried it with a JAVA client but there was the same occurance.
--
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
16 years, 9 months
[JBoss JIRA] Created: (JBWS-2115) EJB client vehicle not sufficiently isolated
by Thomas Diesler (JIRA)
EJB client vehicle not sufficiently isolated
--------------------------------------------
Key: JBWS-2115
URL: http://jira.jboss.com/jira/browse/JBWS-2115
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Reporter: Thomas Diesler
Assigned To: Thomas Diesler
Fix For: jbossws-1.2.1
The endpoint war contains a SEI
@HandlerChain(file="SimpleEndpoint_handler.xml")
com.sun.ts.tests.jaxws.wsi.w2j.rpc.literal.R2739.SimpleEndpoint
the client vehicles contain a SEI with the same name, but without the @HandlerChain annotation
When the client calls Service.getPort(SimpleEndpoint.class)
the SEI is incorrecly loaded from the endpoint war. All deployments are generated with a loader repository
00:11:43,091 INFO [JAXWSWebServiceMetaDataBuilder] processHandlerChain [SimpleEndpoint_handler.xml] on: com.sun.ts.tests.jaxws.wsi.w2j.rpc.literal.R2739.SimpleEndpoint
00:11:43,091 INFO [JAXWSWebServiceMetaDataBuilder] (vfsfile:/home/tdiesler/svn/jbossas/trunk/build/output/jboss-5.0.0.Beta2/server/cts/tmp/jsr88/WSW2JRLR2739TestService.ear/WSW2JRLR2739TestService_web.war/WEB-INF/classes/ <no signer certificates>)
0
3-15-2007 06:55:49: SVR-ERROR: org.jboss.ws.WSException: Cannot resolve handler file 'SimpleEndpoint_handler.xml' on com.sun.ts.tests.jaxws.wsi.w2j.rpc.literal.R1007.SimpleEndpoint
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.processHandlerChain(JAXWSMetaDataBuilder.java:221)
at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(JAXWSClientMetaDataBuilder.java:201)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:207)
at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:196)
at javax.xml.ws.Service.getPort(Service.java:185)
at com.sun.ts.tests.jaxws.sharedclients.StubContext.createJavaEEStub(StubContext.java:138)
--
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
16 years, 9 months
[JBoss JIRA] Updated: (JBWS-1283) Soap attachments are dropped on server response when added in ejb3 jaxws handler
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1283?page=all ]
Thomas Diesler updated JBWS-1283:
---------------------------------
Summary: Soap attachments are dropped on server response when added in ejb3 jaxws handler (was: Soap attachments were dropped on server responses. Attachment is added on a handler's handleResponse method; however it mysteriously disappeared on the outgoing soap message.)
> Soap attachments are dropped on server response when added in ejb3 jaxws handler
> --------------------------------------------------------------------------------
>
> Key: JBWS-1283
> URL: http://jira.jboss.com/jira/browse/JBWS-1283
> Project: JBoss Web Services
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: jbossws-native
> Affects Versions: jbossws-1.0.2
> Environment: windows, linux, jdk1.5
> Reporter: George Gan
> Assigned To: Heiko Braun
> Fix For: jbossws-2.0.0
>
> Attachments: ServiceEndpointInvoker.java, ServiceEndpointInvokerEJB21.java
>
>
> Soap attachments were dropped on server responses. Attachment can be added on a handler's handleResponse method; however it mysteriously disappeared on the outgoing soap message.
> The problem was in the ServiceEndpointInvoker. It overwrote the SOAPMessage in the MessageContext. In this class, the method invokeServiceEndpoint was overwritten by ServiceEndpointInvokerEJB21, which invokes the EJB via the ServiceEndpointInterceptor. This ServiceEndpointInterceptor invokes the EJB and also the handlers; it creates the correct SOAPMessage and sets it in the ContextContext. Unfortunately, it was overwritten later by the ServiceEndpointInvoker.
> Fixes are attached.
--
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
16 years, 9 months
[JBoss JIRA] Commented: (JBWS-1172) Support schema validation for incoming/outgoing messages
by Thomas Diesler (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1172?page=comments#action_12407487 ]
Thomas Diesler commented on JBWS-1172:
--------------------------------------
please post user comments to the user forum.
> Support schema validation for incoming/outgoing messages
> --------------------------------------------------------
>
> Key: JBWS-1172
> URL: http://jira.jboss.com/jira/browse/JBWS-1172
> Project: JBoss Web Services
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: jbossws-native
> Reporter: Thomas Diesler
> Assigned To: Thomas Diesler
> Fix For: jbossws-native-2.0.4
>
>
> I am trying to use JBOSSWS 1.0.2. and JBOSSAS-4.0.4GA
> I am starting with a WSDL file that contains a schema. I used WSTOOLS to generate the appropriate artifacts
> I would like to use DOCUMENT/LITERAL wrapped style and I would like to turn on schema validation of my XML instances against a schema defined in the WSDL (on receipt of the message the server does the validation ?).
> Looking through the sources, I see that JAXBDeserializer (jbossws-core.jar) calls JAXBUnmarshallerImpl which calls UnmarshallerImpl (jboss-xml-binding.jar) which does the parsing of the XML.
> I do not see any call to UnmarshallerImpl.setSchemaValidation in this call graph. Should this be called to turn on to do Schema Validation ? If so how and where ?
> Is Schema Validation for Document/Literal something that JBOSSWS 1.0.2 supports ?
> How does one turn on XML Schema validation in JBOSSWS ?
--
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
16 years, 9 months
[JBoss JIRA] Commented: (JBWS-1172) Support schema validation for incoming/outgoing messages
by l p (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1172?page=comments#action_12407483 ]
l p commented on JBWS-1172:
---------------------------
Also, when I add this to my webservice:
@SchemaValidation( enabled=true, errorHandler=nl.kb.hrd.dd.karakterisering.impls.ValidationErrorHandler.class, schemaLocation="ergens")
and send an invalid request, nothing happens. The request just gets passed, the handler is not called, and I see no errormessage about the invalid schemaLocation.
A related question: in the jax-ws RI, it is not necessary to specify the schema location. Why is it needed here ?
> Support schema validation for incoming/outgoing messages
> --------------------------------------------------------
>
> Key: JBWS-1172
> URL: http://jira.jboss.com/jira/browse/JBWS-1172
> Project: JBoss Web Services
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: jbossws-native
> Reporter: Thomas Diesler
> Assigned To: Thomas Diesler
> Fix For: jbossws-native-2.0.4
>
>
> I am trying to use JBOSSWS 1.0.2. and JBOSSAS-4.0.4GA
> I am starting with a WSDL file that contains a schema. I used WSTOOLS to generate the appropriate artifacts
> I would like to use DOCUMENT/LITERAL wrapped style and I would like to turn on schema validation of my XML instances against a schema defined in the WSDL (on receipt of the message the server does the validation ?).
> Looking through the sources, I see that JAXBDeserializer (jbossws-core.jar) calls JAXBUnmarshallerImpl which calls UnmarshallerImpl (jboss-xml-binding.jar) which does the parsing of the XML.
> I do not see any call to UnmarshallerImpl.setSchemaValidation in this call graph. Should this be called to turn on to do Schema Validation ? If so how and where ?
> Is Schema Validation for Document/Literal something that JBOSSWS 1.0.2 supports ?
> How does one turn on XML Schema validation in JBOSSWS ?
--
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
16 years, 9 months
[JBoss JIRA] Commented: (JBWS-1172) Support schema validation for incoming/outgoing messages
by l p (JIRA)
[ http://jira.jboss.com/jira/browse/JBWS-1172?page=comments#action_12407479 ]
l p commented on JBWS-1172:
---------------------------
I cannot find any test for the @SchemaValidation annotation on a webservice, is this already supported ?
> Support schema validation for incoming/outgoing messages
> --------------------------------------------------------
>
> Key: JBWS-1172
> URL: http://jira.jboss.com/jira/browse/JBWS-1172
> Project: JBoss Web Services
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: jbossws-native
> Reporter: Thomas Diesler
> Assigned To: Thomas Diesler
> Fix For: jbossws-native-2.0.4
>
>
> I am trying to use JBOSSWS 1.0.2. and JBOSSAS-4.0.4GA
> I am starting with a WSDL file that contains a schema. I used WSTOOLS to generate the appropriate artifacts
> I would like to use DOCUMENT/LITERAL wrapped style and I would like to turn on schema validation of my XML instances against a schema defined in the WSDL (on receipt of the message the server does the validation ?).
> Looking through the sources, I see that JAXBDeserializer (jbossws-core.jar) calls JAXBUnmarshallerImpl which calls UnmarshallerImpl (jboss-xml-binding.jar) which does the parsing of the XML.
> I do not see any call to UnmarshallerImpl.setSchemaValidation in this call graph. Should this be called to turn on to do Schema Validation ? If so how and where ?
> Is Schema Validation for Document/Literal something that JBOSSWS 1.0.2 supports ?
> How does one turn on XML Schema validation in JBOSSWS ?
--
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
16 years, 9 months