[JBoss JIRA] (WFLY-4013) The value of the bound attribute in socket-binding-group messaging is always false
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-4013?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-4013:
-----------------------------------------------
Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1156360|https://bugzilla.redhat.com/show_bug.cgi?id=1156360] from NEW to MODIFIED
> The value of the bound attribute in socket-binding-group messaging is always false
> ----------------------------------------------------------------------------------
>
> Key: WFLY-4013
> URL: https://issues.jboss.org/browse/WFLY-4013
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: JBoss AS7 7.2.0.Final
> Environment: JBoss EAP 6.3.1.
> Reporter: Tom Ross
> Assignee: Jeff Mesnil
> Fix For: 9.0.0.Beta1
>
>
> The value of bound attribute in messaging socket group is always false.
> {noformat}
> /socket-binding-group=standard-sockets/socket-binding=messaging:read-resource(include-runtime=true, recursive=true)
> {
> "outcome" => "success",
> "result" => {
> "bound" => false,
> "bound-address" => undefined,
> "bound-port" => undefined,
> "client-mappings" => undefined,
> "fixed-port" => false,
> "interface" => undefined,
> "multicast-address" => undefined,
> "multicast-port" => undefined,
> "name" => "messaging",
> "port" => 5445
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years
[JBoss JIRA] (WFLY-4137) Wrong content type (text/xml) in outgoing multipart SOAPMessage (expected multipart/related; ...)
by Tomas Hofman (JIRA)
[ https://issues.jboss.org/browse/WFLY-4137?page=com.atlassian.jira.plugin.... ]
Tomas Hofman updated WFLY-4137:
-------------------------------
Description:
Clone of EAP6 issue https://bugzilla.redhat.com/show_bug.cgi?id=1167348 - WF is also susceptible.
Description of problem:
There is wrong content type (text/xml) in multipart SOAPMessage when sending it using javax.xml.soap API. So target system is unable to parse it.
How reproducible:
always
Additional info:
It's also wrong in EAP 6.2.
EAP 6.1 is OK.
There is a patch attached in BZ-1167348 for JBossWS CXF 4.3.3. The same fix should be also applied to JBossWS CXF 5.0.0 which is used by Wildfly.
was:
Clone of EAP6 issue https://bugzilla.redhat.com/show_bug.cgi?id=1167348 - WF is also susceptible.
Description of problem:
There is wrong content type (text/xml) in multipart SOAPMessage when sending it using javax.xml.soap API. So target system is unable to parse it.
How reproducible:
always
Additional info:
It's also wrong in EAP 6.2.
EAP 6.1 is OK.
There is a patch attached in BZ-1167348 for JBoss CXF 4.3.3. The same fix should be also applied to JBoss CXF 5.0.0 which is used by Wildfly.
> Wrong content type (text/xml) in outgoing multipart SOAPMessage (expected multipart/related; ...)
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-4137
> URL: https://issues.jboss.org/browse/WFLY-4137
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 9.0.0.Alpha1
> Reporter: Tomas Hofman
> Assignee: Tomas Hofman
>
> Clone of EAP6 issue https://bugzilla.redhat.com/show_bug.cgi?id=1167348 - WF is also susceptible.
> Description of problem:
> There is wrong content type (text/xml) in multipart SOAPMessage when sending it using javax.xml.soap API. So target system is unable to parse it.
> How reproducible:
> always
> Additional info:
> It's also wrong in EAP 6.2.
> EAP 6.1 is OK.
> There is a patch attached in BZ-1167348 for JBossWS CXF 4.3.3. The same fix should be also applied to JBossWS CXF 5.0.0 which is used by Wildfly.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years
[JBoss JIRA] (DROOLS-199) The entire kie 6.3 build should move maven from 3.0.5 to 3.2.x
by Michael Biarnes Kiefer (JIRA)
[ https://issues.jboss.org/browse/DROOLS-199?page=com.atlassian.jira.plugin... ]
Michael Biarnes Kiefer commented on DROOLS-199:
-----------------------------------------------
tried to update tycho version to 0.21.0 and build droolsjbpm-toold with maven 3.2.3 but it is still not compiling: https://gist.github.com/mbiarnes/f7341948b7a2602ecc71
> The entire kie 6.3 build should move maven from 3.0.5 to 3.2.x
> --------------------------------------------------------------
>
> Key: DROOLS-199
> URL: https://issues.jboss.org/browse/DROOLS-199
> Project: Drools
> Issue Type: Task
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
> Priority: Critical
>
> Old description:
> To reproduce:
> - Install maven 3.1.0
> - Run mvn-all.sh clean install -Dfull
> Note: Any changes to the pom must still allow them to run with 3.0.5 too.
> 1) At least droolsjbpm-tools (drools-eclipse) is guaranteed to fail because it uses an older tycho version and only tycho 0.18.1 is compatible with maven 3.1.0 according to the tycho mailing list.
> So the maven tycho plugin will need to be upgraded to 0.18.1 (which works with maven 3.0.5 too - so they say).
> 2) There might be other surprises...
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
10 years