[JBoss JIRA] (JBESB-3520) JON Plug-In: Wrong description used for ESB Service Entities
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBESB-3520?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on JBESB-3520:
------------------------------------------------
Heiko W. Rupp <hrupp(a)redhat.com> changed the Status of [bug 645856|https://bugzilla.redhat.com/show_bug.cgi?id=645856] from VERIFIED to CLOSED
> JON Plug-In: Wrong description used for ESB Service Entities
> ------------------------------------------------------------
>
> Key: JBESB-3520
> URL: https://issues.jboss.org/browse/JBESB-3520
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Management
> Affects Versions: 4.9
> Environment: JON Plug-In deployed in JON 2.4
> JON Plug-In deployed in SOA-P 5.0.0 (admin-console)
> JON Plug-In deployed in SOA-P 5.0.2 (admin-console)
> Reporter: Larry O'Leary
> Assignee: Kevin Conner
> Fix For: 4.9 CP1
>
> Attachments: Case_00023652-jbossesb-master.patch
>
>
> Viewing an ESB service entity in admin-console shows the same description for all services within a service deployment. For example:
> <host> -> JBossAS Servers -> JBoss AS 5 (default) -> JBoss ESB -> Deployments -> jbossesb.esb -> Services -> DeadLetterService Service
> - and -
> <host> -> JBossAS Servers -> JBoss AS 5 (default) -> JBoss ESB -> Deployments -> jbossesb.esb -> Services -> RedeliverService Service
> Show the same description. In this case the description shown is for the RedeliverService Service.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBESB-3947) SoapUI SOAPClient doesn't pick up HttpClient properties if "wsdl" specifies local file ("file://...")
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBESB-3947?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on JBESB-3947:
------------------------------------------------
Tadayoshi Sato <tasato(a)redhat.com> made a comment on [bug 1000866|https://bugzilla.redhat.com/show_bug.cgi?id=1000866]
Description of problem:
Platform BZ for https://issues.jboss.org/browse/JBESB-3947
In the soapUI version of SOAPClient, when hosting a WSDL locally (i.e. "file://..."), the Apache HttpClient which is used in SOAPClient does not pick up the proxy server settings:
<action name="soapui-client-action" class="org.jboss.soa.esb.actions.soap.SOAPClient">
<property name="wsdl" value="file:///opt/jboss-soa-p-5.3.1/jboss-as/samples/quickstarts/webservice_consumer1/HelloWorldWS.wsdl" />
<property name="http-client-properties">
<http-client-property name="http.proxyHost" value="192.168.0.101"/>
<http-client-property name="http.proxyPort" value="18080"/>
</property>
...
</action>
> SoapUI SOAPClient doesn't pick up HttpClient properties if "wsdl" specifies local file ("file://...")
> -----------------------------------------------------------------------------------------------------
>
> Key: JBESB-3947
> URL: https://issues.jboss.org/browse/JBESB-3947
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Services
> Affects Versions: 4.12
> Reporter: Tadayoshi Sato
>
> In the soapUI version of {{SOAPClient}}, when hosting a WSDL locally (i.e. {{"file://...")}}, the Apache HttpClient which is used in {{SOAPClient}} does not pick up the proxy server settings:
> {code:xml}
> <action name="soapui-client-action" class="org.jboss.soa.esb.actions.soap.SOAPClient">
> <property name="wsdl" value="file:///opt/jboss-soa-p-5.3.1/jboss-as/samples/quickstarts/webservice_consumer1/HelloWorldWS.wsdl" />
> <property name="http-client-properties">
> <http-client-property name="http.proxyHost" value="192.168.0.101"/>
> <http-client-property name="http.proxyPort" value="18080"/>
> </property>
> ...
> </action>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBESB-3947) SoapUI SOAPClient doesn't pick up HttpClient properties if "wsdl" specifies local file ("file://...")
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBESB-3947?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated JBESB-3947:
-------------------------------------------
Bugzilla Update: Perform
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1000866
> SoapUI SOAPClient doesn't pick up HttpClient properties if "wsdl" specifies local file ("file://...")
> -----------------------------------------------------------------------------------------------------
>
> Key: JBESB-3947
> URL: https://issues.jboss.org/browse/JBESB-3947
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Services
> Affects Versions: 4.12
> Reporter: Tadayoshi Sato
>
> In the soapUI version of {{SOAPClient}}, when hosting a WSDL locally (i.e. {{"file://...")}}, the Apache HttpClient which is used in {{SOAPClient}} does not pick up the proxy server settings:
> {code:xml}
> <action name="soapui-client-action" class="org.jboss.soa.esb.actions.soap.SOAPClient">
> <property name="wsdl" value="file:///opt/jboss-soa-p-5.3.1/jboss-as/samples/quickstarts/webservice_consumer1/HelloWorldWS.wsdl" />
> <property name="http-client-properties">
> <http-client-property name="http.proxyHost" value="192.168.0.101"/>
> <http-client-property name="http.proxyPort" value="18080"/>
> </property>
> ...
> </action>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBESB-3947) SoapUI SOAPClient doesn't pick up HttpClient properties if "wsdl" specifies local file ("file://...")
by Tadayoshi Sato (JIRA)
[ https://issues.jboss.org/browse/JBESB-3947?page=com.atlassian.jira.plugin... ]
Tadayoshi Sato updated JBESB-3947:
----------------------------------
Workaround Description:
You can configure the {{"target-host-url"}} property explicitly to avoid this issue, as follows:
{code:xml}
<action name="soapui-client-action" class="org.jboss.soa.esb.actions.soap.SOAPClient">
...
<property name="http-client-properties">
<http-client-property name="target-host-url" value="http://127.0.0.1:8080/"/> <!-- the endpoint URL specified in WSDL -->
<http-client-property name="http.proxyHost" value="192.168.0.101"/>
<http-client-property name="http.proxyPort" value="18080"/>
</property>
{code}
Workaround: Workaround Exists
> SoapUI SOAPClient doesn't pick up HttpClient properties if "wsdl" specifies local file ("file://...")
> -----------------------------------------------------------------------------------------------------
>
> Key: JBESB-3947
> URL: https://issues.jboss.org/browse/JBESB-3947
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Services
> Affects Versions: 4.12
> Reporter: Tadayoshi Sato
>
> In the soapUI version of {{SOAPClient}}, when hosting a WSDL locally (i.e. {{"file://...")}}, the Apache HttpClient which is used in {{SOAPClient}} does not pick up the proxy server settings:
> {code:xml}
> <action name="soapui-client-action" class="org.jboss.soa.esb.actions.soap.SOAPClient">
> <property name="wsdl" value="file:///opt/jboss-soa-p-5.3.1/jboss-as/samples/quickstarts/webservice_consumer1/HelloWorldWS.wsdl" />
> <property name="http-client-properties">
> <http-client-property name="http.proxyHost" value="192.168.0.101"/>
> <http-client-property name="http.proxyPort" value="18080"/>
> </property>
> ...
> </action>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBESB-3947) SoapUI SOAPClient doesn't pick up HttpClient properties if "wsdl" specifies local file ("file://...")
by Tadayoshi Sato (JIRA)
[ https://issues.jboss.org/browse/JBESB-3947?page=com.atlassian.jira.plugin... ]
Tadayoshi Sato commented on JBESB-3947:
---------------------------------------
The root cause is clear: in {{SOAPClient.extractHttpClientProps(ConfigTree)}} method it sets the HttpClient's {{"target-host-url"}} property to the value of {{"wsdl"}}; and the {{HttpProtocol}} configurator looks up this property and initialises HttpClient based on the other properties only if the property starts with {{"http"}}. So if the {{"target-host-url"}} property starts with {{"file"}} the HttpClient initialisation doesn't occur.
> SoapUI SOAPClient doesn't pick up HttpClient properties if "wsdl" specifies local file ("file://...")
> -----------------------------------------------------------------------------------------------------
>
> Key: JBESB-3947
> URL: https://issues.jboss.org/browse/JBESB-3947
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Services
> Affects Versions: 4.12
> Reporter: Tadayoshi Sato
>
> In the soapUI version of {{SOAPClient}}, when hosting a WSDL locally (i.e. {{"file://...")}}, the Apache HttpClient which is used in {{SOAPClient}} does not pick up the proxy server settings:
> {code:xml}
> <action name="soapui-client-action" class="org.jboss.soa.esb.actions.soap.SOAPClient">
> <property name="wsdl" value="file:///opt/jboss-soa-p-5.3.1/jboss-as/samples/quickstarts/webservice_consumer1/HelloWorldWS.wsdl" />
> <property name="http-client-properties">
> <http-client-property name="http.proxyHost" value="192.168.0.101"/>
> <http-client-property name="http.proxyPort" value="18080"/>
> </property>
> ...
> </action>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBESB-3947) SoapUI SOAPClient doesn't pick up HttpClient properties if "wsdl" specifies local file ("file://...")
by Tadayoshi Sato (JIRA)
[ https://issues.jboss.org/browse/JBESB-3947?page=com.atlassian.jira.plugin... ]
Tadayoshi Sato updated JBESB-3947:
----------------------------------
Description:
In the soapUI version of {{SOAPClient}}, when hosting a WSDL locally (i.e. {{"file://...")}}, the Apache HttpClient which is used in {{SOAPClient}} does not pick up the proxy server settings:
{code:xml}
<action name="soapui-client-action" class="org.jboss.soa.esb.actions.soap.SOAPClient">
<property name="wsdl" value="file:///opt/jboss-soa-p-5.3.1/jboss-as/samples/quickstarts/webservice_consumer1/HelloWorldWS.wsdl" />
<property name="http-client-properties">
<http-client-property name="http.proxyHost" value="192.168.0.101"/>
<http-client-property name="http.proxyPort" value="18080"/>
</property>
...
</action>
{code}
was:
In the soapUI version of {{SOAPClient}}, when hosting a WSDL locally (i.e. {{"file://...")}}, the Apache HttpClient which is used in {{SOAPClient}} does not pick up the proxy server settings:
{code:xml}
<action name="soapui-client-action" class="org.jboss.soa.esb.actions.soap.SOAPClient">
<property name="wsdl" value="file:///opt/jboss-soa-p-5.3.1/jboss-as/samples/quickstarts/webservice_consumer1/HelloWorldWS.wsdl" />
<property name="http-client-properties">
<http-client-property name="http.proxyHost" value="192.168.0.101"/>
<http-client-property name="http.proxyPort" value="18080"/>
</property>
...
</action>
{code}
> SoapUI SOAPClient doesn't pick up HttpClient properties if "wsdl" specifies local file ("file://...")
> -----------------------------------------------------------------------------------------------------
>
> Key: JBESB-3947
> URL: https://issues.jboss.org/browse/JBESB-3947
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Services
> Affects Versions: 4.12
> Reporter: Tadayoshi Sato
>
> In the soapUI version of {{SOAPClient}}, when hosting a WSDL locally (i.e. {{"file://...")}}, the Apache HttpClient which is used in {{SOAPClient}} does not pick up the proxy server settings:
> {code:xml}
> <action name="soapui-client-action" class="org.jboss.soa.esb.actions.soap.SOAPClient">
> <property name="wsdl" value="file:///opt/jboss-soa-p-5.3.1/jboss-as/samples/quickstarts/webservice_consumer1/HelloWorldWS.wsdl" />
> <property name="http-client-properties">
> <http-client-property name="http.proxyHost" value="192.168.0.101"/>
> <http-client-property name="http.proxyPort" value="18080"/>
> </property>
> ...
> </action>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBESB-3947) SoapUI SOAPClient doesn't pick up HttpClient properties if "wsdl" specifies local file ("file://...")
by Tadayoshi Sato (JIRA)
Tadayoshi Sato created JBESB-3947:
-------------------------------------
Summary: SoapUI SOAPClient doesn't pick up HttpClient properties if "wsdl" specifies local file ("file://...")
Key: JBESB-3947
URL: https://issues.jboss.org/browse/JBESB-3947
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.12
Reporter: Tadayoshi Sato
In the soapUI version of {{SOAPClient}}, when hosting a WSDL locally (i.e. {{"file://...")}}, the Apache HttpClient which is used in {{SOAPClient}} does not pick up the proxy server settings:
{code:xml}
<action name="soapui-client-action" class="org.jboss.soa.esb.actions.soap.SOAPClient">
<property name="wsdl" value="file:///opt/jboss-soa-p-5.3.1/jboss-as/samples/quickstarts/webservice_consumer1/HelloWorldWS.wsdl" />
<property name="http-client-properties">
<http-client-property name="http.proxyHost" value="192.168.0.101"/>
<http-client-property name="http.proxyPort" value="18080"/>
</property>
...
</action>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (JBESB-3946) SOA-P 5.3.1 needs to support SOAP 1.2 Authentication
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBESB-3946?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on JBESB-3946:
------------------------------------------------
Rick Wagner <rwagner(a)redhat.com> changed the Status of [bug 991136|https://bugzilla.redhat.com/show_bug.cgi?id=991136] from NEW to CLOSED
> SOA-P 5.3.1 needs to support SOAP 1.2 Authentication
> ----------------------------------------------------
>
> Key: JBESB-3946
> URL: https://issues.jboss.org/browse/JBESB-3946
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Services
> Affects Versions: 4.11
> Reporter: Tom Cunningham
> Fix For: 4.11 CP3
>
>
> From case :
> We want to use SOAP 1.2 with JBoss ESB, but some of the classes are not compatible implemented.
> In "SoapExtractionUtil" hard coded QNames are used!
> Code snippet:
> public static boolean isStartOfHeader(final XMLEvent event)
> {
> return event.isStartElement() && ((StartElement)event).getName().equals(SOAP_HEADER_QNAME);
> }
> When this is used by the "UsernameTokenExtractor", in the method "extractSecurityInfo" and the security is no longer useable when using SOAP 1.2!!!
> Code snippet:
> public AuthenticationRequest extractSecurityInfo(final String soap)
> throws ExtractionException {
> if (soap == null || !soap.startsWith("<"))
> return null;
> XMLEventReader xmlReader = null;
> User user = null;
> Set<Object> credentials = new HashSet<Object>();
> try {
> xmlReader = XML_INPUT_FACTORY
> .createXMLEventReader(new StringReader(soap));
> while (xmlReader.hasNext()) {
> XMLEvent xmlEvent = xmlReader.nextEvent();
> if (isStartOfHeader(xmlEvent)) {
> We need to support "SOAP 1.2" to communicate with customers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (JBESB-3946) SOA-P 5.3.1 needs to support SOAP 1.2 Authentication
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBESB-3946?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on JBESB-3946:
------------------------------------------------
Rick Wagner <rwagner(a)redhat.com> made a comment on [bug 991136|https://bugzilla.redhat.com/show_bug.cgi?id=991136]
Closing this BZ, we can fix 5.3.1 with the next Roll up via BZ991461.
> SOA-P 5.3.1 needs to support SOAP 1.2 Authentication
> ----------------------------------------------------
>
> Key: JBESB-3946
> URL: https://issues.jboss.org/browse/JBESB-3946
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Services
> Affects Versions: 4.11
> Reporter: Tom Cunningham
> Fix For: 4.11 CP3
>
>
> From case :
> We want to use SOAP 1.2 with JBoss ESB, but some of the classes are not compatible implemented.
> In "SoapExtractionUtil" hard coded QNames are used!
> Code snippet:
> public static boolean isStartOfHeader(final XMLEvent event)
> {
> return event.isStartElement() && ((StartElement)event).getName().equals(SOAP_HEADER_QNAME);
> }
> When this is used by the "UsernameTokenExtractor", in the method "extractSecurityInfo" and the security is no longer useable when using SOAP 1.2!!!
> Code snippet:
> public AuthenticationRequest extractSecurityInfo(final String soap)
> throws ExtractionException {
> if (soap == null || !soap.startsWith("<"))
> return null;
> XMLEventReader xmlReader = null;
> User user = null;
> Set<Object> credentials = new HashSet<Object>();
> try {
> xmlReader = XML_INPUT_FACTORY
> .createXMLEventReader(new StringReader(soap));
> while (xmlReader.hasNext()) {
> XMLEvent xmlEvent = xmlReader.nextEvent();
> if (isStartOfHeader(xmlEvent)) {
> We need to support "SOAP 1.2" to communicate with customers.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
