[JBoss JIRA] Created: (JBWS-1406) WS-Eventing: event notification failure
by Alessio Soldano (JIRA)
WS-Eventing: event notification failure
---------------------------------------
Key: JBWS-1406
URL: http://jira.jboss.com/jira/browse/JBWS-1406
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: ws-eventing
Affects Versions: jbossws-1.0.4
Environment: JBoss 4.0.4.GA, JBossWS 1.0.4.GA
Reporter: Alessio Soldano
Attachments: dsvn.txt
We noticed that event notification failures are completely lost. If an event notification fail (for example because the event sink is down) the current jbossws engine just logs the error and does nothing else. Of course it could be useful at least to keep track of failed notification in order to analyze the problem, send them again later or simply to warn the sink's owner.
--
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, 11 months
[JBoss JIRA] Created: (JBWS-1336) JAXWSDeployerJSE throws NPE
by Anil Saldhana (JIRA)
JAXWSDeployerJSE throws NPE
---------------------------
Key: JBWS-1336
URL: http://jira.jboss.com/jira/browse/JBWS-1336
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jaxws
Reporter: Anil Saldhana
Priority: Critical
Attachments: xacml-requestattrib.war
JAXWSDeployerJSE is throwing a NPE for the attached war.
==============================================================
14:22:14,656 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.Beta (build: CVSTa
g=HEAD date=200611071417)] Started in 27s:188ms
14:22:20,156 INFO [MainDeployer] deploy, url=file:/C:/cygwin/home/asaldhana/jbo
ss-5.0/jboss-head/testsuite/output/lib/xacml-requestattrib.war
14:22:20,187 ERROR [JAXWSDeployerJSE] Cannot process web deployment
java.lang.NullPointerException
at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.hash(ConcurrentReaderHashMap.java:298)
at EDU.oswego.cs.dl.util.concurrent.ConcurrentReaderHashMap.get(ConcurrentReaderHashMap.java:410)
at org.jboss.mx.loading.UnifiedLoaderRepository3.getCachedClass(UnifiedLoaderRepository3.java:194)
at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:394)
at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at org.jboss.ws.integration.jboss50.JAXWSDeployerJSE.isWebServiceDeployment(JAXWSDeployerJSE.java:79)
at org.jboss.ws.integration.jboss50.AbstractDeployer.deploy(AbstractDeployer.java:55)
at org.jboss.ws.integration.jboss50.AbstractJSEDeployer.deploy(AbstractJSEDeployer.java:85)
================================================================
I think the deploer is trying to load a bean that does not exist.
--
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, 11 months
[JBoss JIRA] Created: (JBWS-1399) JBWS-1178 implementation trouble
by Stefano Maestri (JIRA)
JBWS-1178 implementation trouble
--------------------------------
Key: JBWS-1399
URL: http://jira.jboss.com/jira/browse/JBWS-1399
Project: JBoss Web Services
Issue Type: Patch
Security Level: Public (Everyone can see)
Affects Versions: jbossws-1.0.4
Reporter: Stefano Maestri
I got jbossws-1.0.4 and I installed it in my environment (for the description of the environment refer to my original blog post about multiple virtual host:
http://www.javalinux.it/blogs/index.php?title=multiple_virtual_host_and_s... ).
There are some problems
* If I follow instruction in jboss-beans.xml leaving webservicehost as a null string I get this Exception during deploy of jbossws:
Code:
09:11:02,349 ERROR [AbstractKernelController] Error installing to Configured: name=ServiceEndpointMa
nager state=Instantiated mode=Manual requiredState=Create
java.lang.IllegalArgumentException: Null value metadata
at org.jboss.kernel.plugins.config.Configurator.getPropertySetterJoinPoint(Configurator.java
:487)
at org.jboss.kernel.plugins.config.Configurator.getPropertySetterJoinPoint(Configurator.java
:434)
at org.jboss.kernel.plugins.config.Configurator.getPropertySetterJoinPoints(Configurator.jav
a:398)
at org.jboss.kernel.plugins.config.AbstractKernelConfigurator.getPropertySetterJoinPoints(Ab
[...]
*** DEPLOYMENTS IN ERROR:
ServiceEndpointManager -> java.lang.IllegalArgumentException: Null value metadata
If I comment the webServiceHost tag the deploy works correctly. I think here the explaination in the commented part of jboss-beans.xml have to be changed .
* The current implementation only replaces the host name, but not the port used to call the webservice. I think the port replacing is also very important in an environment of complete virtual hosting like our one. Using Linux Virtual Server is normal to virtualize ports. For example we use ports > 1024 on real servers and standard 80/443 ports on virtual servers
* You didn't apply the patch on showServiceEndpointTable method in ServiceEndPointManager. This method is called from context servlets and IMHO have to replace host and ports accordingly to wsdl's replacing. Otherwise you get an horrible list of wsdl pointing to "http://jbossws.undefined.host/..." and of course links do not work
--
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, 11 months
[JBoss JIRA] Created: (JBWS-1333) Fix marshalling of null values in base64Binary, hexBinary
by Thomas Diesler (JIRA)
Fix marshalling of null values in base64Binary, hexBinary
---------------------------------------------------------
Key: JBWS-1333
URL: http://jira.jboss.com/jira/browse/JBWS-1333
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jaxrpc
Reporter: Thomas Diesler
Assigned To: Heiko Braun
Priority: Blocker
Fix For: jbossws-1.0.4
19:53:55,783 ERROR [SOAPFaultExceptionHelper] SOAP request exception
java.lang.IllegalArgumentException: multipart/related stream invalid, no root part was found
at org.jboss.ws.soap.attachment.MultipartRelatedDecoder.decodeMultipartRelatedMessage(MultipartRelatedDecoder.java:153)
at org.jboss.ws.soap.MessageFactoryImpl.createMessageInternal(MessageFactoryImpl.java:185)
at org.jboss.ws.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:145)
/home/tdiesler/svn/jbossws/branches/jbossws-1.0/src/test
[tdiesler@tddell test]$ ant -Dtest=jaxrpc/marshall test
tests-main:
[junit] Running org.jboss.test.ws.jaxrpc.marshall.MarshallDocLitTestCase
[junit] Tests run: 63, Failures: 0, Errors: 0, Time elapsed: 14.64 sec
[junit] Running org.jboss.test.ws.jaxrpc.marshall.MarshallRpcLitDIITestCase
[junit] Tests run: 63, Failures: 0, Errors: 2, Time elapsed: 6.636 sec
[junit] Test org.jboss.test.ws.jaxrpc.marshall.MarshallRpcLitDIITestCase FAILED
[junit] Running org.jboss.test.ws.jaxrpc.marshall.MarshallRpcLitTestCase
[junit] Tests run: 63, Failures: 0, Errors: 1, Time elapsed: 11.84 sec
[junit] Test org.jboss.test.ws.jaxrpc.marshall.MarshallRpcLitTestCase 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, 11 months
[JBoss JIRA] Created: (JBWS-1386) ComplexType with base64Binary property
by Thomas Diesler (JIRA)
ComplexType with base64Binary property
--------------------------------------
Key: JBWS-1386
URL: http://jira.jboss.com/jira/browse/JBWS-1386
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jaxrpc
Reporter: Thomas Diesler
Assigned To: Thomas Diesler
Fix For: jbossws-1.0.5
I am using JBoss 4.0.4 with jbossws 1.0.3GA. I am developing a WS DII client which talks with a third party Web Service. I am having problems serializing one field which is specified as "base64Binary" on the WSDL:
Code:
<xsd:complexType name="BinaryData">
<xsd:sequence>
<xsd:element name="data" type="xsd:base64Binary"
nillable="true"/>
<xsd:element name="mimeType" type="xsd:string"
nillable="true"/>
<xsd:element name="URL" type="xsd:string" nillable="true"/>
<xsd:element name="removeOnUpdate" type="xsd:boolean"
nillable="false"/>
</xsd:sequence>
The "data" field should be sent as a Base64 String. Although, the Request SOAP message has the following data:
Code:
<ns1:data xmlns:ns1="urn:drm/ingest-ex/IngestService/SchemaTypes">
<ns1:data>-1</ns1:data>
<ns1:data>-40</ns1:data>
<ns1:data>-1</ns1:data>
<ns1:data>-32</ns1:data>
......
<ns1:mimeType>image/jpeg</ns1:mimeType>
<ns1:URL xsi:nil="1"/>
<ns1:removeOnUpdate>false</ns1:removeOnUpdate>
</ns1:data>
--
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, 11 months