[JBoss JIRA] Created: (JBESB-1553) SOAPClient action remappes objects with null strings to empty strings
by Jiri Pechanec (JIRA)
SOAPClient action remappes objects with null strings to empty strings
---------------------------------------------------------------------
Key: JBESB-1553
URL: http://jira.jboss.com/jira/browse/JBESB-1553
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Web Services
Affects Versions: 4.2.1 CP1
Reporter: Jiri Pechanec
Assigned To: Kevin Conner
…
[View More]Fix For: 4.2.1 CP2
Use webservice_consumer2 quickstart and use the attached files - contains enhanced equals and toString defintions. Make sure that option1 is used.
The object with following contents is sent to processing to ivoke web service
id = 101 lineItems = [Line Item ID= 1 Price=10.0 Ship To=aname, Line Item ID= 2 Price=20.0 Ship To=aname2] shipTo = null
But in the web service processing method the contents is
id = 101 lineItems = [Line Item ID= 1 Price=10.0 Ship To=aname, Line Item ID= 2 Price=20.0 Ship To=aname2] shipTo =
The difference is in shipTo property which was set tu null on the input but comes to web service as empty string.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[View Less]
14 years, 9 months
[JBoss JIRA] Created: (JBESB-2574) OGNLUtils.assertIsCollection fails
by jarkko Lietolahti (JIRA)
OGNLUtils.assertIsCollection fails
----------------------------------
Key: JBESB-2574
URL: https://jira.jboss.org/jira/browse/JBESB-2574
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 4.5
Reporter: jarkko Lietolahti
The method
private static boolean assertIsCollection(Element element) {
if(element.getAttributeNS(JBOSSESB_SOAP_NS, IS_COLLECTION_ATTRIB).…
[View More]equals("true")) {
// It's already been attributed... no need to check for the soapui comment...
return true;
}
Comment firstComment = (Comment) YADOMUtil.getFirstChildByType(element, Node.COMMENT_NODE);
// TODO: Get Ole (soapUI) to add an attribute to the collection element - better than looking for this comment.
if(firstComment != null && firstComment.getTextContent().indexOf("1 or more repetitions") != -1) {
return true;
}
return false;
}
Especially row;
Comment firstComment = (Comment) YADOMUtil.getFirstChildByType(element, Node.COMMENT_NODE);
is causing a grief.
Given an WSDL like below;
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" >
<soapenv:Header/>
<soapenv:Body>
<QueryRequest>
<username>?</username>
<password>?</password>
<Customer id="?" telcoid="?">
</Customer>
<!--1 or more repetitions:-->
<productIds>?</productIds>
<isLookup>?</isLookup>
<maxWaitTime>?</maxWaitTime>
</QueryRequest>
</soapenv:Body>
</soapenv:Envelope>
OGNLUtils creates ognlExpression QueryRequest[0] for all the elements below QueryRequest. E.g. ognl for username, password etc is "QueryRequest[0]" when in reality it should be QueryRequest.username , QueryRequest.password etc..
This is caused by the array element LATER in the WSDL;
--
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
[View Less]
14 years, 10 months
[JBoss JIRA] Created: (JBESB-2489) JMS bus with topic cannot be used in jms-jca-provider
by Martin Vecera (JIRA)
JMS bus with topic cannot be used in jms-jca-provider
-----------------------------------------------------
Key: JBESB-2489
URL: https://jira.jboss.org/jira/browse/JBESB-2489
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.4 CP2
Reporter: Martin Vecera
JMS bus based on a topic cannot be used within jms-jca-provider. On deployment the …
[View More]following exception occurs:
009-03-25 09:46:45,904 WARN [org.jboss.resource.adapter.jms.inflow.JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@3efbb1d8(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)6333934d destination=queue/pt_qs_nojbm_notifier_topictest_gw isTopic=true tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=1 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
java.lang.ClassCastException: Object at 'queue/pt_qs_nojbm_notifier_topictest_gw' in context {java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, hostKey=localhost:1100, jnp.partitionName=DefaultPartition, jnp.discoveryTimeout=5000, jnp.discoveryGroup=230.0.0.4, jnp.disableDiscovery=false, java.naming.provider.url=localhost:1100, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interfaces, jnp.maxRetries=1, jnp.discoveryPort=1102, jnp.discoveryTTL=16} is not an instance of [class=javax.jms.Topic classloader=org.jboss.mx.loading.UnifiedClassLoader3@6f9bb25a{ url=null ,addedOrder=2} interfaces={interface=javax.jms.Destination classloader=org.jboss.mx.loading.UnifiedClassLoader3@6f9bb25a{ url=null ,addedOrder=2}}] object class is [class=org.jboss.jms.destination.JBossQueue classloader=org.jboss.mx.loading.UnifiedClassLoader3@6f9bb25a{ url=null ,addedOrder=2} interfaces={interface=javax.jms.Queue classloader=org.jboss.mx.loading.UnifiedClassLoader3@6f9bb25a{ url=null ,addedOrder=2}}]
at org.jboss.util.naming.Util.checkObject(Util.java:329)
at org.jboss.util.naming.Util.lookup(Util.java:216)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:409)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:316)
at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:635)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756)
at java.lang.Thread.run(Thread.java:595)
Then on usage:
2009-03-25 09:46:55,926 INFO [org.jboss.resource.adapter.jms.inflow.JmsActivation] Attempting to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@3efbb1d8(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)6333934d destination=queue/pt_qs_nojbm_notifier_topictest_gw isTopic=true tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=1 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
2009-03-25 09:46:55,931 ERROR [org.jboss.resource.adapter.jms.inflow.JmsActivation] Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@3efbb1d8(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)6333934d destination=queue/pt_qs_nojbm_notifier_topictest_gw isTopic=true tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=1 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
java.lang.ClassCastException: Object at 'queue/pt_qs_nojbm_notifier_topictest_gw' in context {java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, hostKey=localhost:1100, jnp.partitionName=DefaultPartition, jnp.discoveryTimeout=5000, jnp.discoveryGroup=230.0.0.4, jnp.disableDiscovery=false, java.naming.provider.url=localhost:1100, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interfaces, jnp.maxRetries=1, jnp.discoveryPort=1102, jnp.discoveryTTL=16} is not an instance of [class=javax.jms.Topic classloader=org.jboss.mx.loading.UnifiedClassLoader3@6f9bb25a{ url=null ,addedOrder=2} interfaces={interface=javax.jms.Destination classloader=org.jboss.mx.loading.UnifiedClassLoader3@6f9bb25a{ url=null ,addedOrder=2}}] object class is [class=org.jboss.jms.destination.JBossQueue classloader=org.jboss.mx.loading.UnifiedClassLoader3@6f9bb25a{ url=null ,addedOrder=2} interfaces={interface=javax.jms.Queue classloader=org.jboss.mx.loading.UnifiedClassLoader3@6f9bb25a{ url=null ,addedOrder=2}}]
at org.jboss.util.naming.Util.checkObject(Util.java:329)
at org.jboss.util.naming.Util.lookup(Util.java:216)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:409)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:316)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:259)
at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:639)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756)
at java.lang.Thread.run(Thread.java:595)
--
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
[View Less]
14 years, 10 months
[JBoss JIRA] Created: (JBESB-2554) HttpRouter stores http headers of request in body instead of headers from http response
by Jurgen Van Bouchaute (JIRA)
HttpRouter stores http headers of request in body instead of headers from http response
----------------------------------------------------------------------------------------
Key: JBESB-2554
URL: https://jira.jboss.org/jira/browse/JBESB-2554
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Adapters
Affects Versions: 4.5
Environment: Windows Vista Ultimate, Sun JRE 1.…
[View More]6.10, JBOSS ESB 4.5-GA
Reporter: Jurgen Van Bouchaute
Priority: Minor
org.jboss.soa.esb.actions.routing.http.HttpRouter using http method "POST"
stores HTTP headers from the request in the Message body instead of headers from the response :
private void attachResponseDetails(Message message, HttpMethodBase method, int responseCode) {
HttpResponse response = new HttpResponse(responseCode);
response.setEncoding(method.getResponseCharSet());
response.setLength(method.getResponseContentLength());
>>>>> Header[] responseHeaders = method.getRequestHeaders(); <<<<<<<
for(Header responseHeader : responseHeaders) {
response.addHeader(new HttpHeader(responseHeader.getName(), responseHeader.getValue()));
}
message.getBody().add(HttpResponse.RESPONSE_KEY, response);
}
--
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
[View Less]
14 years, 10 months