March 2014 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3966) Unable to use Sql-Message-Filter with out Status Column

by Dheeraj Chintalapudi (JIRA)

Dheeraj Chintalapudi created JBESB-3966: ------------------------------------------- Summary: Unable to use Sql-Message-Filter with out Status Column Key: JBESB-3966 URL: https://issues.jboss.org/browse/JBESB-3966 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Application Server Environment: Jboss Esb Reporter: Dheeraj Chintalapudi Priority: Blocker Hi Team, I am working on Jboss Esb with Mysql Db Connection. I have been seeing from past 1 week. the sample example given are working for only column with status column please provide the info how to remove status column attribute from jbossesb-1.0.1.xsd thanks Dheeraj -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBESB-3950) SOAPClient generates empty objects for not-required fields

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3950?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3950: ------------------------------------------------ Rick Wagner <rwagner(a)redhat.com> changed the Status of [bug 998677|https://bugzilla.redhat.com/show_bug.cgi?id=998677] from ON_QA to VERIFIED > SOAPClient generates empty objects for not-required fields > ---------------------------------------------------------- > > Key: JBESB-3950 > URL: https://issues.jboss.org/browse/JBESB-3950 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 4.11 CP3 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP3 > > > From Musharraf Hussein : > I have a case [1] where customer is having a problem with the way "SOAPClient" generates SOAP messages to invoke the backend WebServices. Actually it is observed that if a complex type of message (element in SOAP message) contains a 'null' then 'SOAPClient' sends an empty element (as well as an empty child element). According to the customer this shouldn't happen and ESB should rather omit the entire parent-child elements altogether, as it is causing them an NPE in their code. This is how executing their test case (attached) look like. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBESB-3941) ESB ignoring transacted flag on EPR element

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3941?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3941: ------------------------------------------------ Rick Wagner <rwagner(a)redhat.com> changed the Status of [bug 980802|https://bugzilla.redhat.com/show_bug.cgi?id=980802] from NEW to ASSIGNED > ESB ignoring transacted flag on EPR element > ------------------------------------------- > > Key: JBESB-3941 > URL: https://issues.jboss.org/browse/JBESB-3941 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.12 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP3 > > > Description of problem: > For example > > <jbossesb-listeners > > deployment="Quickstart_JMS_Transacted.esb" > > parameterReloadSecs="5"> > > <listener > > busIdRef="quickstartEsbChannel" > > listenerClass="org.jboss.soa.esb.listeners.message.MessageAwareListener" > > maxThreads="1" > > mep="OneWay" > > name="jmssecured" > > service-category="JMSSecuredESB" > > service-description="JMS Secured quickstart sample" > > service-name="SimpleListener"> > > <EPR > > acknowledge-mode="AUTO_ACKNOWLEDGE" > > connection-factory="XAConnectionFactory" > > destination-name="queue/quickstart_jms_transacted_Request_esb" > > destination-type="queue" > > persistent="true" > > protocol="jms" > > transacted="true"/> > If you set a breakpoint on the MessageAwareListener where it retrieves the value for 'transacted', i.e. "transactional = _config.getBooleanAttribute(ListenerTagNames.TRANSACTED_TAG, false) ;", and if you then in Eclipse Debug mode analyse the 'this._config' (the ConfigTree variable), you can see that that ConfigTree does not have a 'transacted' key in its '_attributes' map. However, one of the Child ConfigTrees of this Listener tree, the 'EPR' ConfigTree, does have a 'transacted = true' value in it's tree. However, _config.getBooleanAttribute(..) does not do a recursive search through the child ConfigTrees (and it probably shouldn't, I'm not sure how this was designed), which explains why it does not return 'true'. > > I have a proposed hack/fix that would resolve this. > > > > In MessageAwareListener line 169. Replace > > > > From > > transactional = _config.getBooleanAttribute(ListenerTagNames.TRANSACTED_TAG, false) ; > > To > > transactional = _config.getChildren("EPR")[0]..getBooleanAttribute(ListenerTagNames.TRANSACTED_TAG, false) ; -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBESB-3932) JmsConnectionPool reverts to non-xa when transaction has expired

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3932?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3932: ------------------------------------------------ Rick Wagner <rwagner(a)redhat.com> changed the Status of [bug 980799|https://bugzilla.redhat.com/show_bug.cgi?id=980799] from ON_QA to VERIFIED > JmsConnectionPool reverts to non-xa when transaction has expired > ---------------------------------------------------------------- > > Key: JBESB-3932 > URL: https://issues.jboss.org/browse/JBESB-3932 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Transports > Affects Versions: 4.10 CP1 > Reporter: Kevin Conner > Assignee: Tom Cunningham > Fix For: 4.11 CP3 > > Attachments: JBESB-3932.diff > > > The JmsConnectionPool test for whether to create a non-XA session or XA session does not take into account an expired transaction. The test checks for active transactions and, it not found, falls back to the non-XA API. > The test should only check for an existing transaction, whether active or not, and allow the TransactionManager to fail when invoked. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBESB-3945) Bpm5Processor does not support processes containing sub-processes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3945?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3945: ------------------------------------------------ Rick Wagner <rwagner(a)redhat.com> changed the Status of [bug 980530|https://bugzilla.redhat.com/show_bug.cgi?id=980530] from ON_QA to VERIFIED > Bpm5Processor does not support processes containing sub-processes > ----------------------------------------------------------------- > > Key: JBESB-3945 > URL: https://issues.jboss.org/browse/JBESB-3945 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Process flow > Affects Versions: 4.11 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP3 > > > Bpm5Processor (or rather AbstractBpm5Action) adds the configured process definitions to the knowledgebase: > kbuilder.add(ResourceFactory.newClassPathResource(processDefName), ResourceType.BPMN2); > But there is no support for processes which are calling sub-processes. The class should be extended to read a list of process definition names from the configuration, and add them all to the kbase, so that process->sub-process invocation is possible from Bpm5Processor. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBESB-2265) Wise action don't work with BASIC auth

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-2265?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-2265: ------------------------------------------------ Rick Wagner <rwagner(a)redhat.com> changed the Status of [bug 987197|https://bugzilla.redhat.com/show_bug.cgi?id=987197] from ON_QA to VERIFIED > Wise action don't work with BASIC auth > -------------------------------------- > > Key: JBESB-2265 > URL: https://issues.jboss.org/browse/JBESB-2265 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 4.4 > Reporter: Stefano Maestri > Assignee: Tom Cunningham > Fix For: 4.11 CP3 > > Attachments: jboss-esb.xml, soap.esb.tgz, Wise0.xml > > -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBESB-3955) 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-3955?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3955: ------------------------------------------------ Rick Wagner <rwagner(a)redhat.com> changed the Status of [bug 1000866|https://bugzilla.redhat.com/show_bug.cgi?id=1000866] from ON_QA to VERIFIED > SoapUI SOAPClient doesn't pick up HttpClient properties if "wsdl" specifies local file ("file://...") > ----------------------------------------------------------------------------------------------------- > > Key: JBESB-3955 > URL: https://issues.jboss.org/browse/JBESB-3955 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 4.12 > Reporter: Tadayoshi Sato > Assignee: Tom Cunningham > Fix For: 4.11 CP3 > > > 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, 1 month

1
0
0 / 0

[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: ------------------------------------------------ Rick Wagner <rwagner(a)redhat.com> changed the Status of [bug 1000866|https://bugzilla.redhat.com/show_bug.cgi?id=1000866] from ON_QA to VERIFIED > 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 > Assignee: Tadayoshi Sato > Fix For: 4.13 > > > 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, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues March 2014