[
https://issues.jboss.org/browse/JBIDE-17670?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-17670:
---------------------------------------------
Sorry - I missed the call out to me ;/
I'm not a WS expert but as I read it there is no way of fixing this reliably when
running on Java 7 but it works when running Java 6 or Java 8, correct ?
If that is the case then I would say because we are days away from closing CR1 now is not
the time to have "fun" adding dynamic loading of JAX-WS library when running on
Java 7 but not on others or similar trickery and thus for JBDS 8 say users can use Java 8
to run this and we can look at fixing this in a update after JBDS 8 is released - BUT:
Do we know that running with Java 8 actually fixes the issue ?
And does this affect *all* soa-p interactions ? Is java 7 that broken it cannot do any
soa-p calls ?
Web Service Tester: JAX-WS request doesn't contain definition of
SOAPAction
---------------------------------------------------------------------------
Key: JBIDE-17670
URL:
https://issues.jboss.org/browse/JBIDE-17670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.2.0.Beta2
Reporter: Radoslav RĂ¡bara
Assignee: Brian Fitzpatrick
Priority: Critical
Fix For: 4.2.0.CR1
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)