List Info

Thread: Created: (JBWS-1944) jbossws-native ignores @XmlSchema annotation on p




Created: (JBWS-1944) jbossws-native ignores @XmlSchema annotation on p
country flaguser name
United States
2007-12-29 13:31:43
jbossws-native ignores XmlSchema annotation on package-info.java
------------------------------------------------------------
-----

                 Key: JBWS-1944
                 URL: http://ji
ra.jboss.com/jira/browse/JBWS-1944
             Project: JBoss Web Services
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: jbossws-jaxws
    Affects Versions:  jbossws-2.0.2, jbossws-2.0.1.SP2, 
jbossws-2.0.1.SP1, jbossws-2.0.1
         Environment: Microsoft Windows XP Home SP2, x86
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build
1.5.0_06-b05)
Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode)

            Reporter: Artur Karazniewicz


Seems that current implementations of jbossws-native ignores
XmlSchema annotation on package in
package-info.java.

Please find my test case attached. 

Generated Schema is as follows:


{code:title=TestWebService.java endpoint}
package org.acme.service;

import javax.jws.WebService;
import javax.ejb.Stateless;

WebService()
Stateless()
public class TestWebSevice {
    public void perform(Parms params) {
    }
}


{code:title=Params.java payload}
package org.acme.service;

public class Parms {
    public String val;
}


{code:title=package-info.java}
XmlSchema(namespace="http://www.acme.org
/service", elementFormDefault=XmlNsForm.QUALIFIED)
package org.acme.service;

import javax.xml.bind.annotation.XmlNsForm;
import javax.xml.bind.annotation.XmlSchema;


generated WSDL:

{code:title=TestWebService WSDL}
<definitions name='TestWebSeviceService'
targetNamespace='http://service.acme.org/
' xmlns='http://schemas.xmlso
ap.org/wsdl/' xmlns:soap='http://schemas.
xmlsoap.org/wsdl/soap/' xmlns:tns='http://service.acme.org/
' xmlnssd='<
a
href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/20
01/XMLSchema'>
 <types>
  <xs:schema targetNamespace='http://service.acme.org/
' version='1.0' xmlns:tns='http://service.acme.org/
' xmlnss='http://www.w3.org/20
01/XMLSchema'>
   <xs:element name='perform' type='tns:perform'/>
   <xs:element name='performResponse'
type='tns:performResponse'/>
   <xs:complexType name='perform'>
    <xs:sequence>
     <xs:element minOccurs='0' name='arg0'
type='tns:parms'/>
    </xs:sequence>

   </xs:complexType>
   <xs:complexType name='parms'>
    <xs:sequence>
     <xs:element minOccurs='0' name='val'
type='xs:string'/>
    </xs:sequence>
   </xs:complexType>
   <xs:complexType name='performResponse'>
    <xs:sequence/>
   </xs:complexType>

  </xs:schema>
 </types>
 <message name='TestWebSevice_perform'>
  <part element='tns:perform'
name='perform'></part>
 </message>
 <message name='TestWebSevice_performResponse'>
  <part element='tns:performResponse'
name='performResponse'></part>
 </message>
 <portType name='TestWebSevice'>

  <operation name='perform' parameterOrder='perform'>
   <input
message='tns:TestWebSevice_perform'></input>
   <output
message='tns:TestWebSevice_performResponse'></output&g
t;
  </operation>
 </portType>
 <binding name='TestWebSeviceBinding'
type='tns:TestWebSevice'>
  <soap:binding style='document' transport='http://schemas.x
mlsoap.org/soap/http'/>
  <operation name='perform'>
   <soap:operation soapAction=''/>

   <input>
    <soap:body use='literal'/>
   </input>
   <output>
    <soap:body use='literal'/>
   </output>
  </operation>
 </binding>
 <service name='TestWebSeviceService'>

  <port binding='tns:TestWebSeviceBinding'
name='TestWebSevicePort'>
   <soap:address location='http://127.0
.0.1:8080/test/TestWebSevice'/>
  </port>
 </service>
</definitions>


I have checked the same codebase against glassfish v2 with
metro, and relevant part of WSDL (i.e. XSD) looks like
below. Note *elementFormDefault="qualified"* and
*targetNamespace="http://www.acme.or
g/service"*

{code:title=TestWebService XSD from GlassFish v2 and Metro}
<?xml version="1.0"
encoding="UTF-8"?>
<!-- Published by JAX-WS RI at http://jax-ws.dev.java.ne
t. RI's version is JAX-WS RI 2.1.2-hudson-182-RC1.
-->

<xs:schema xmlnss=&qu
ot;http://www.w3.
org/2001/XMLSchema"
elementFormDefault="qualified"
version="1.0" targetNamespace="http://www.acme
.org/service">

<xs:complexType name="parms">
<xs:sequence>
<xs:element name="val"
type="xs:string"
minOccurs="0"></xs:element>
</xs:sequence>
</xs:complexType>
</xs:schema>


-- 
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.atl
assian.com/software/jira

        
_______________________________________________
jbossws-issues mailing list
jbossws-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossws-issues

Updated: (JBWS-1944) jbossws-native ignores @XmlSchema annotation on p
country flaguser name
United States
2007-12-29 13:34:43
     [ 
http://jira.jboss.com/jira/browse/JBWS-1944?page=all ]

Artur Karazniewicz updated JBWS-1944:
-------------------------------------

    Attachment: test-case.tgz

Test case files.

> jbossws-native ignores XmlSchema annotation on
package-info.java
>
------------------------------------------------------------
-----
>
>                 Key: JBWS-1944
>                 URL: http://ji
ra.jboss.com/jira/browse/JBWS-1944
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-jaxws
>    Affects Versions:  jbossws-2.0.2, jbossws-2.0.1.SP2,
 jbossws-2.0.1.SP1, jbossws-2.0.1
>         Environment: Microsoft Windows XP Home SP2,
x86
> java version "1.5.0_06"
> Java(TM) 2 Runtime Environment, Standard Edition (build
1.5.0_06-b05)
> Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed
mode)
>            Reporter: Artur Karazniewicz
>         Attachments: test-case.tgz
>
>
> Seems that current implementations of jbossws-native
ignores XmlSchema annotation on package in
package-info.java.
> Please find my test case attached. 
> Generated Schema is as follows:
> {code:title=TestWebService.java endpoint}
> package org.acme.service;
> import javax.jws.WebService;
> import javax.ejb.Stateless;
> WebService()
> Stateless()
> public class TestWebSevice {
>     public void perform(Parms params) {
>     }
> }
> 
> {code:title=Params.java payload}
> package org.acme.service;
> public class Parms {
>     public String val;
> }
> 
> {code:title=package-info.java}
> XmlSchema(namespace="http://www.acme.org
/service", elementFormDefault=XmlNsForm.QUALIFIED)
> package org.acme.service;
> import javax.xml.bind.annotation.XmlNsForm;
> import javax.xml.bind.annotation.XmlSchema;
> 
> generated WSDL:
> {code:title=TestWebService WSDL}
> <definitions name='TestWebSeviceService'
targetNamespace='http://service.acme.org/
' xmlns='http://schemas.xmlso
ap.org/wsdl/' xmlns:soap='http://schemas.
xmlsoap.org/wsdl/soap/' xmlns:tns='http://service.acme.org/
' xmlnssd='<
a
href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/20
01/XMLSchema'>
>  <types>
>   <xs:schema targetNamespace='http://service.acme.org/
' version='1.0' xmlns:tns='http://service.acme.org/
' xmlnss='http://www.w3.org/20
01/XMLSchema'>
>    <xs:element name='perform'
type='tns:perform'/>
>    <xs:element name='performResponse'
type='tns:performResponse'/>
>    <xs:complexType name='perform'>
>     <xs:sequence>
>      <xs:element minOccurs='0' name='arg0'
type='tns:parms'/>
>     </xs:sequence>
>    </xs:complexType>
>    <xs:complexType name='parms'>
>     <xs:sequence>
>      <xs:element minOccurs='0' name='val'
type='xs:string'/>
>     </xs:sequence>
>    </xs:complexType>
>    <xs:complexType name='performResponse'>
>     <xs:sequence/>
>    </xs:complexType>
>   </xs:schema>
>  </types>
>  <message name='TestWebSevice_perform'>
>   <part element='tns:perform'
name='perform'></part>
>  </message>
>  <message name='TestWebSevice_performResponse'>
>   <part element='tns:performResponse'
name='performResponse'></part>
>  </message>
>  <portType name='TestWebSevice'>
>   <operation name='perform'
parameterOrder='perform'>
>    <input
message='tns:TestWebSevice_perform'></input>
>    <output
message='tns:TestWebSevice_performResponse'></output&g
t;
>   </operation>
>  </portType>
>  <binding name='TestWebSeviceBinding'
type='tns:TestWebSevice'>
>   <soap:binding style='document' transport='http://schemas.x
mlsoap.org/soap/http'/>
>   <operation name='perform'>
>    <soap:operation soapAction=''/>
>    <input>
>     <soap:body use='literal'/>
>    </input>
>    <output>
>     <soap:body use='literal'/>
>    </output>
>   </operation>
>  </binding>
>  <service name='TestWebSeviceService'>
>   <port binding='tns:TestWebSeviceBinding'
name='TestWebSevicePort'>
>    <soap:address location='http://127.0
.0.1:8080/test/TestWebSevice'/>
>   </port>
>  </service>
> </definitions>
> 
> I have checked the same codebase against glassfish v2
with metro, and relevant part of WSDL (i.e. XSD) looks like
below. Note *elementFormDefault="qualified"* and
*targetNamespace="http://www.acme.or
g/service"*
> {code:title=TestWebService XSD from GlassFish v2 and
Metro}
> <?xml version="1.0"
encoding="UTF-8"?>
> <!-- Published by JAX-WS RI at http://jax-ws.dev.java.ne
t. RI's version is JAX-WS RI 2.1.2-hudson-182-RC1.
-->
> <xs:schema xmlnss=&qu
ot;http://www.w3.
org/2001/XMLSchema"
elementFormDefault="qualified"
version="1.0" targetNamespace="http://www.acme
.org/service">
> <xs:complexType name="parms">
> <xs:sequence>
> <xs:element name="val"
type="xs:string"
minOccurs="0"></xs:element>
> </xs:sequence>
> </xs:complexType>
> </xs:schema>
> 

-- 
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.atl
assian.com/software/jira

        
_______________________________________________
jbossws-issues mailing list
jbossws-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossws-issues

Commented: (JBWS-1944) jbossws-native ignores @XmlSchema annotation on
country flaguser name
United States
2007-12-30 08:48:44
    [ http://jira.jboss.com/jira/browse/JBWS-
1944?page=comments#action_12393565 ] 
            
Artur Karazniewicz commented on JBWS-1944:
------------------------------------------

Ok, I tried the same codebase against geronimo and got:

java.lang.ClassFormatError: Illegal class modifiers 
in class package-info: 0x1600

This seems to explain my issue. I compiled code with JSE 6.0
with -target 1.5, and got hitted by this known issue...
Anyhow, seems that JBoss classloader just ignores file in
this casa (?).

When compiled with JSE 5.0 everything works fine.

Plese close this "issue".


> jbossws-native ignores XmlSchema annotation on
package-info.java
>
------------------------------------------------------------
-----
>
>                 Key: JBWS-1944
>                 URL: http://ji
ra.jboss.com/jira/browse/JBWS-1944
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-jaxws
>    Affects Versions: jbossws-2.0.1,  jbossws-2.0.2, 
jbossws-2.0.1.SP1, jbossws-2.0.1.SP2
>         Environment: Microsoft Windows XP Home SP2,
x86
> java version "1.5.0_06"
> Java(TM) 2 Runtime Environment, Standard Edition (build
1.5.0_06-b05)
> Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed
mode)
>            Reporter: Artur Karazniewicz
>         Attachments: test-case.tgz
>
>
> Seems that current implementations of jbossws-native
ignores XmlSchema annotation on package in
package-info.java.
> Please find my test case attached. 
> Generated Schema is as follows:
> {code:title=TestWebService.java endpoint}
> package org.acme.service;
> import javax.jws.WebService;
> import javax.ejb.Stateless;
> WebService()
> Stateless()
> public class TestWebSevice {
>     public void perform(Parms params) {
>     }
> }
> 
> {code:title=Params.java payload}
> package org.acme.service;
> public class Parms {
>     public String val;
> }
> 
> {code:title=package-info.java}
> XmlSchema(namespace="http://www.acme.org
/service", elementFormDefault=XmlNsForm.QUALIFIED)
> package org.acme.service;
> import javax.xml.bind.annotation.XmlNsForm;
> import javax.xml.bind.annotation.XmlSchema;
> 
> generated WSDL:
> {code:title=TestWebService WSDL}
> <definitions name='TestWebSeviceService'
targetNamespace='http://service.acme.org/
' xmlns='http://schemas.xmlso
ap.org/wsdl/' xmlns:soap='http://schemas.
xmlsoap.org/wsdl/soap/' xmlns:tns='http://service.acme.org/
' xmlnssd='<
a
href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/20
01/XMLSchema'>
>  <types>
>   <xs:schema targetNamespace='http://service.acme.org/
' version='1.0' xmlns:tns='http://service.acme.org/
' xmlnss='http://www.w3.org/20
01/XMLSchema'>
>    <xs:element name='perform'
type='tns:perform'/>
>    <xs:element name='performResponse'
type='tns:performResponse'/>
>    <xs:complexType name='perform'>
>     <xs:sequence>
>      <xs:element minOccurs='0' name='arg0'
type='tns:parms'/>
>     </xs:sequence>
>    </xs:complexType>
>    <xs:complexType name='parms'>
>     <xs:sequence>
>      <xs:element minOccurs='0' name='val'
type='xs:string'/>
>     </xs:sequence>
>    </xs:complexType>
>    <xs:complexType name='performResponse'>
>     <xs:sequence/>
>    </xs:complexType>
>   </xs:schema>
>  </types>
>  <message name='TestWebSevice_perform'>
>   <part element='tns:perform'
name='perform'></part>
>  </message>
>  <message name='TestWebSevice_performResponse'>
>   <part element='tns:performResponse'
name='performResponse'></part>
>  </message>
>  <portType name='TestWebSevice'>
>   <operation name='perform'
parameterOrder='perform'>
>    <input
message='tns:TestWebSevice_perform'></input>
>    <output
message='tns:TestWebSevice_performResponse'></output&g
t;
>   </operation>
>  </portType>
>  <binding name='TestWebSeviceBinding'
type='tns:TestWebSevice'>
>   <soap:binding style='document' transport='http://schemas.x
mlsoap.org/soap/http'/>
>   <operation name='perform'>
>    <soap:operation soapAction=''/>
>    <input>
>     <soap:body use='literal'/>
>    </input>
>    <output>
>     <soap:body use='literal'/>
>    </output>
>   </operation>
>  </binding>
>  <service name='TestWebSeviceService'>
>   <port binding='tns:TestWebSeviceBinding'
name='TestWebSevicePort'>
>    <soap:address location='http://127.0
.0.1:8080/test/TestWebSevice'/>
>   </port>
>  </service>
> </definitions>
> 
> I have checked the same codebase against glassfish v2
with metro, and relevant part of WSDL (i.e. XSD) looks like
below. Note *elementFormDefault="qualified"* and
*targetNamespace="http://www.acme.or
g/service"*
> {code:title=TestWebService XSD from GlassFish v2 and
Metro}
> <?xml version="1.0"
encoding="UTF-8"?>
> <!-- Published by JAX-WS RI at http://jax-ws.dev.java.ne
t. RI's version is JAX-WS RI 2.1.2-hudson-182-RC1.
-->
> <xs:schema xmlnss=&qu
ot;http://www.w3.
org/2001/XMLSchema"
elementFormDefault="qualified"
version="1.0" targetNamespace="http://www.acme
.org/service">
> <xs:complexType name="parms">
> <xs:sequence>
> <xs:element name="val"
type="xs:string"
minOccurs="0"></xs:element>
> </xs:sequence>
> </xs:complexType>
> </xs:schema>
> 

-- 
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.atl
assian.com/software/jira

        
_______________________________________________
jbossws-issues mailing list
jbossws-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossws-issues

[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )