[JBoss JIRA] Created: (JBWS-1314) Precursor to streaming optimizations, elimination of xmlFragment
by Thomas Diesler (JIRA)
Precursor to streaming optimizations, elimination of xmlFragment
----------------------------------------------------------------
Key: JBWS-1314
URL: http://jira.jboss.com/jira/browse/JBWS-1314
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jaxws
Reporter: Thomas Diesler
Fix For: jbossws-2.0.1
At some point, we should remove the xml string fragment processing phase. It's not needed in our long term streaming optimization plan, and it adds unneeded performance overhead in the current design.
Instead we could pass the corresponding DOM chunk directly to the marshalling layer. JAXB supports this using javax.xml.transform.Source, and it wouldn't be difficult to enhance JBossXB to do the same. This would also be more robust because it would eliminate the xml escape processing that we duplicate from a standard XML parser (see [JBWS-1240] for an example).
--
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, 10 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, 11 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
17 years, 2 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
17 years, 3 months
[JBoss JIRA] Created: (JBWS-1472) Address in WSDL is now always replaced regardless of 'alwaysModifySOAPAddress' value.
by Darran Lofthouse (JIRA)
Address in WSDL is now always replaced regardless of 'alwaysModifySOAPAddress' value.
-------------------------------------------------------------------------------------
Key: JBWS-1472
URL: http://jira.jboss.com/jira/browse/JBWS-1472
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jbossws-1.0.4, jbossws-1.2.0
Reporter: Darran Lofthouse
Assigned To: Darran Lofthouse
Fix For: jbossws-1.2.1
Address in WSDL is now always replaced regardless of 'alwaysModifySOAPAddress' value.
If the property 'webServiceHost' is commented out the address is always replaced with the address used by the calling client.
If the 'webServiceHost' proprty is set then this value the address in the WSDL is always replaced with this value.
It should be possible to keep the original behaviour which allowed the address to be set in the WSDL and this address would always be returned so the three required scenarios are: -
1 - Use the hostname specified in the -beans.xml.
2 - Use the hostname already in the WSDL.
3 - Use the hostname of the calling client.
The output of http://localhost:8080/jbossws/services should also use the same addresses.
The Jira tasks which caused this change in behaviour are JBWS-1399 and JBWS-1178.
--
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
17 years, 5 months
[JBoss JIRA] Created: (JBWS-1335) Unmarshalling of SimpleTypes fails in jbossws-1.0.0.GA
by Igor Stuyver (JIRA)
Unmarshalling of SimpleTypes fails in jbossws-1.0.0.GA
------------------------------------------------------
Key: JBWS-1335
URL: http://jira.jboss.com/jira/browse/JBWS-1335
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jaxb
Affects Versions: jbossws-1.0.0
Environment: JBoss 4.0.4.GA/jbossws-1.0.0.GA/wscompile
Reporter: Igor Stuyver
This bug report is a follow up for http://jira.jboss.com/jira/browse/JBWS-761
We are experiencing simular problems but on JBoss 4.0.4.GA. The only difference is that we have an interface (created by XmlBeans) with the same package/classname JBossWS is looking for for mapping its simpleType.
We have following simple type declared:
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
targetNamespace="http://my.project/schema/common"
elementFormDefault="qualified">
<xs:simpleType name="LanguageCode">
<xs:restriction base="xs:string">
<xs:minLength value="2"/>
<xs:maxLength value="2"/>
</xs:restriction>
</xs:simpleType>
</xs:schema>
This simple type is used in the WSDL file and in a seperate XSD file. Of this seperate XSD file, XMLBeans (http://xmlbeans.apache.org/) are created for easy use of XML in our application.
We use an ejb-service-ref to call the webservice from an enterprise bean. In the response an element of type LanguageCode is present, in the generated POJO's (sun's wscompile) the element is declared as a String.
During unmarshalling of the xml, following error occurs:
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Neither fromValue(java.lang.String p) nor fromValue(java.lang.String p1, javax.xml.namespace.NamespaceContext p2) were found in interface project.my.schema.common.LanguageCode
at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtUtil.invokeUnmarshalMethod(RtUtil.java:522)
at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtCharactersHandler.unmarshal(RtCharactersHandler.java:104)
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:592)
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endElement(SundayContentHandler.java:130)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.endElement(SaxJBossXBParser.java:271)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(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:137)
For me it seems that during unmarchalling, a class is searched to map the SimpleType to. Not a class but an interface is found and used from the created XMLBeans. The above exceptions is the result.
Following the SUN forum (http://forum.java.sun.com/thread.jspa?threadID=716435) the simple type should be mapped to the Java type the base type of the SimpleType is mapped to, String is this example. During unmarshalling JBossWS is still looking for a class to map the SimpleType to instead of mapping it to String directly.
--
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
17 years, 6 months