[JBoss JIRA] Created: (JBWS-2655) no soap 1.2 inline multireferences support
by Wojciech Oczkowski (JIRA)
no soap 1.2 inline multireferences support
------------------------------------------
Key: JBWS-2655
URL: https://jira.jboss.org/jira/browse/JBWS-2655
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.2
Environment: debian, jboss-4.2, sun-java-6
Reporter: Wojciech Oczkowski
jbossws doesn't seem to support inline multireferences from soap 1.2 while consuming webservices from other enviroments (php for example)
result like:
<item>
<name>item1</name>
<product enc:id="ref1">
<name>product1</name>
</product>
</item>
<item>
<name>item2</name>
<product enc:ref="#ref1"/>
</item>
is unmarshaled with item2 object with product object filled with null's
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBWS-2687) JBossWS commandline tools requires Sun JDK to work. This dependency must be removed
by Richard Opalka (JIRA)
JBossWS commandline tools requires Sun JDK to work. This dependency must be removed
-----------------------------------------------------------------------------------
Key: JBWS-2687
URL: https://jira.jboss.org/jira/browse/JBWS-2687
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.2
Reporter: Richard Opalka
Assignee: Alessio Soldano
Priority: Critical
Fix For: jbossws-native-3.2.0
One of the goals for the next SOA-P CP is to see the whole platform certified with OpenJDK 1.6
I tried to run JBossWS on OpenJDK 1.6 and found the following dependency in our code:
---
[ERROR] com.sun.tools.javac.Main is not available in the classpath, requires Suns JDK version 5.0 or latter.
compilation failed, errors should have been reported
Failed to invoke WsImport
java.lang.IllegalStateException: WsImport invocation failed. Try the verbose switch for more information
at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:233)
at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:222)
at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:80)
---
This dependency causes our command line tools (at least wsconsume) doesn't work on Open JDK :(
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBWS-2749) Update Hudson jobs because of JDK1.5 is finishing EOL transition period
by Alessio Soldano (JIRA)
Update Hudson jobs because of JDK1.5 is finishing EOL transition period
-----------------------------------------------------------------------
Key: JBWS-2749
URL: https://jira.jboss.org/jira/browse/JBWS-2749
Project: JBoss Web Services
Issue Type: Task
Security Level: Public (Everyone can see)
Components: productization
Reporter: Alessio Soldano
Fix For: jbossws-cxf-3.2.1, jbossws-native-3.2.1, jbossws-metro-3.2.1
J2SE 5.0 is in its Java Technology End of Life (EOL) transition period. The EOL transition period began April 8th, 2008 and will complete October 30th, 2009, when J2SE 5.0 will have reached its End of Service Life (EOSL).
This means we're going to run QA using JDK 1.6 only:
- remove JDK 5 jobs from hudson
- rename JDK 6 jobs (useless JDK6 postfix)
- build AS and run AS testsuite with JDK 6
- make sure the latest JDK 6 update is being used (currently u15)
- update release notes to make clear which version of the jdk the project is tested with
This btw should give us some time (on hudson machine) to run a few jobs (NOT ALL JOBS, perhaps just one for each container-stack couple) with Open JDK.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months