[JBoss JIRA] Created: (JBWS-1654) ServiceDElegate requires non portable method getPortClassMap
by Thomas Diesler (JIRA)
ServiceDElegate requires non portable method getPortClassMap
------------------------------------------------------------
Key: JBWS-1654
URL: http://jira.jboss.com/jira/browse/JBWS-1654
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: integration-xfire
Reporter: Thomas Diesler
java.lang.IllegalStateException: Could not initialize Service.
at org.codehaus.xfire.jaxws.ServiceDelegate.<init>(ServiceDelegate.java:77)
at org.codehaus.xfire.jaxws.Provider.createServiceDelegate(Provider.java:32)
at javax.xml.ws.Service.<init>(Service.java:57)
at org.jboss.test.ws.jaxws.eardeployment.TestEndpointService.<init>(TestEndpointService.java:37)
at org.jboss.test.ws.jaxws.eardeployment.EarTestCase.testJSEEndpoint(EarTestCase.java:64)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:23)
Caused by: java.lang.NoSuchMethodException: org.jboss.test.ws.jaxws.eardeployment.TestEndpointService.getPortClassMap()
at java.lang.Class.getMethod(Class.java:1581)
at org.codehaus.xfire.jaxws.ServiceDelegate.<init>(ServiceDelegate.java:60)
--
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, 3 months
[JBoss JIRA] Created: (JBWS-1505) Methods defined in an interface superclass don't appear in WSDL.
by Iaacov Rosenberg (JIRA)
Methods defined in an interface superclass don't appear in WSDL.
----------------------------------------------------------------
Key: JBWS-1505
URL: http://jira.jboss.com/jira/browse/JBWS-1505
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-1.0.4
Environment: JBoss 4.0.5 GA, JRE 1.5.0_10, WinXP
Reporter: Iaacov Rosenberg
Given the following scenario:
public interface Intf1 {
public int getMember1();
public void setMember1(int member1);
}
public interface Intf2 extends Intf1 {
public int getMember2();
public void setMember2(int member2);
}
Whenever JBossWS uses reflection, either when generating the WSDL file or when returning values that implement Intf2, only members defined in Intf2 (i.e. Member2) are processed, while ignoring inherited members.
This only happens with interfaces. Inherited classes are processed correctly.
--
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, 4 months
[JBoss JIRA] Created: (JBWS-1324) JMS Endpoint - Message delivery starts before endpoint is ready.
by Darran Lofthouse (JIRA)
JMS Endpoint - Message delivery starts before endpoint is ready.
----------------------------------------------------------------
Key: JBWS-1324
URL: http://jira.jboss.com/jira/browse/JBWS-1324
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jaxrpc
Affects Versions: jbossws-1.0.3
Reporter: Darran Lofthouse
Fix For: jbossws-1.0.6
For most endpoints we need the EJB to be initialised before we initialise the web service, this way we know the session bean will be ready to process requests before the first request from a client is received.
For message driven beans we need the web service to be initialised before the first message is processed by the MDB, however the same logic is used as is used for session beans so it is possible that the first message will be received while the web service is still being initialised.
--
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, 4 months
[JBoss JIRA] Created: (JBWS-1630) wstools error when using xsd:extension in schema
by Balaji Hari (JIRA)
wstools error when using xsd:extension in schema
------------------------------------------------
Key: JBWS-1630
URL: http://jira.jboss.com/jira/browse/JBWS-1630
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: wstools
Affects Versions: jbossws-1.2.1
Reporter: Balaji Hari
We have the following type extension defined in schema. When runnning wstools against WSDL its looking for wrong QName and throws NullpointerException.
<xsd:simpleType name="NetExplosiveWeightType">
<xsd:restriction base="xsd:decimal">
<xsd:whiteSpace value="collapse" />
<xsd:totalDigits value="9" />
<xsd:fractionDigits value="2" />
</xsd:restriction>
</xsd:simpleType>
<xsd:element name="NetExplosiveWeight">
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="tns:NetExplosiveWeightType">
<xsd:attribute name="uom" use="required">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:whiteSpace value="collapse" />
<xsd:minLength value="1" />
<xsd:maxLength value="2" />
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
Exception in thread "main" java.lang.NullPointerException
at org.jboss.ws.tools.XSDTypeToJava.getVARList(XSDTypeToJava.java:204)
at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:149)
at org.jboss.ws.tools.XSDTypeToJava.createVARforXSElementDeclaration(XSDTypeToJava.java:599)
at org.jboss.ws.tools.XSDTypeToJava.createVARsForElements(XSDTypeToJava.java:522)
at org.jboss.ws.tools.XSDTypeToJava.createVARsforXSParticle(XSDTypeToJava.java:449)
at org.jboss.ws.tools.XSDTypeToJava.getVARList(XSDTypeToJava.java:248)
at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:149)
at org.jboss.ws.tools.XSDTypeToJava.createJavaFile(XSDTypeToJava.java:113)
at org.jboss.ws.tools.WSDLToJava.generateJavaSource(WSDLToJava.java:759)
at org.jboss.ws.tools.WSDLToJava.generateJavaSource(WSDLToJava.java:752)
at org.jboss.ws.tools.WSDLToJava.generateParameter(WSDLToJava.java:577)
at org.jboss.ws.tools.WSDLToJava.appendParameters(WSDLToJava.java:431)
at org.jboss.ws.tools.WSDLToJava.appendDocParameters(WSDLToJava.java:387)
at org.jboss.ws.tools.WSDLToJava.appendMethods(WSDLToJava.java:291)
at org.jboss.ws.tools.WSDLToJava.createSEIFile(WSDLToJava.java:589)
at org.jboss.ws.tools.WSDLToJava.createSEI(WSDLToJava.java:619)
at org.jboss.ws.tools.WSDLToJava.generateSEI(WSDLToJava.java:187)
at org.jboss.ws.tools.helpers.ToolsHelper.handleWSDLToJavaGeneration(ToolsHelper.java:304)
at org.jboss.ws.tools.WSTools.process(WSTools.java:137)
at org.jboss.ws.tools.WSTools.generate(WSTools.java:69)
at org.jboss.ws.tools.WSTools.generate(WSTools.java:119)
at org.jboss.ws.tools.WSTools.main(WSTools.java:58)
--
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, 5 months
[JBoss JIRA] Created: (JBWS-1330) Fix jaxrpc wsse tests for jbossws-5.0
by Thomas Diesler (JIRA)
Fix jaxrpc wsse tests for jbossws-5.0
-------------------------------------
Key: JBWS-1330
URL: http://jira.jboss.com/jira/browse/JBWS-1330
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Fix For: jbossws-2.0.0.CR2
[tdiesler@tdvaio test]$ ant -Dtest=jaxrpc/wsse test
tests-main:
[junit] Running org.jboss.test.ws.jaxrpc.wsse.MicrosoftInteropTestCase
[junit] FIXME: [JBWS-1130] Consolidate namespace declarations
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 2.863 sec
[junit] Running org.jboss.test.ws.jaxrpc.wsse.NotEncodedTestCase
[junit] Tests run: 1, Failures: 1, Errors: 0, Time elapsed: 3.536 sec
[junit] Test org.jboss.test.ws.jaxrpc.wsse.NotEncodedTestCase FAILED
[junit] Running org.jboss.test.ws.jaxrpc.wsse.RoundTripTestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 3.289 sec
[junit] Running org.jboss.test.ws.jaxrpc.wsse.RpcTestCase
[junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 6.722 sec
[junit] Test org.jboss.test.ws.jaxrpc.wsse.RpcTestCase FAILED
[junit] Running org.jboss.test.ws.jaxrpc.wsse.SignEncryptFaultTestCase
[junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 7.19 sec
[junit] Test org.jboss.test.ws.jaxrpc.wsse.SignEncryptFaultTestCase FAILED
[junit] Running org.jboss.test.ws.jaxrpc.wsse.SignFaultTestCase
[junit] Tests run: 2, Failures: 0, Errors: 2, Time elapsed: 5.947 sec
[junit] Test org.jboss.test.ws.jaxrpc.wsse.SignFaultTestCase FAILED
[junit] Running org.jboss.test.ws.jaxrpc.wsse.SimpleSignEncryptTestCase
[junit] Tests run: 2, Failures: 0, Errors: 1, Time elapsed: 6.581 sec
[junit] Test org.jboss.test.ws.jaxrpc.wsse.SimpleSignEncryptTestCase FAILED
[junit] Running org.jboss.test.ws.jaxrpc.wsse.StorePassEncryptTestCase
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 5.452 sec
[junit] Test org.jboss.test.ws.jaxrpc.wsse.StorePassEncryptTestCase FAILED
[junit] Running org.jboss.test.ws.jaxrpc.wsse.SunInteropTestCase
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.382 sec
[junit] Running org.jboss.test.ws.jaxrpc.wsse.UsernameTestCase
[junit] Tests run: 3, Failures: 0, Errors: 3, Time elapsed: 0.431 sec
[junit] Test org.jboss.test.ws.jaxrpc.wsse.UsernameTestCase FAILED
[junit] Running org.jboss.test.ws.jaxrpc.wsse.WebClientTestCase
[junit] [JBAS-3824] Fix ENC for EJB2.1 and Servlets
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.524 sec
[junit] Running org.jboss.test.ws.jaxrpc.wsse.signup.AccountSignupTestCase
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 4.64 sec
[junit] Test org.jboss.test.ws.jaxrpc.wsse.signup.AccountSignupTestCase FAILED
--
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, 7 months
[JBoss JIRA] Created: (JBWS-1453) WSDl To Java - Invalid name for generated class if complex type name contains a period.
by Darran Lofthouse (JIRA)
WSDl To Java - Invalid name for generated class if complex type name contains a period.
---------------------------------------------------------------------------------------
Key: JBWS-1453
URL: http://jira.jboss.com/jira/browse/JBWS-1453
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: wstools
Affects Versions: jbossws-1.2.0.CR2
Reporter: Darran Lofthouse
Assigned To: Darran Lofthouse
Fix For: jbossws-1.2.1
The following compex type: -
<complexType name='String.Array'>
<sequence>
<element maxOccurs='unbounded' minOccurs='0' name='value' nillable='true' type='string'/>
</sequence>
</complexType>
Causes the following class to be generated: -
package org.jboss.support.phonebook;
public class String.Array
{
protected java.lang.String[] value;
public String.Array(){}
public String.Array(java.lang.String[] value){
this.value=value;
}
public java.lang.String[] getValue() { return value ;}
public void setValue(java.lang.String[] value){ this.value=value; }
}
This class name is invalid and the period needs to be replaced.
--
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, 8 months