August 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3428) JAX-WS dependency mismatch between Picketlink/Security and WISE components

by Tom Fennelly (JIRA)

JAX-WS dependency mismatch between Picketlink/Security and WISE components --------------------------------------------------------------------------- Key: JBESB-3428 URL: https://jira.jboss.org/browse/JBESB-3428 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Security, Web Services Affects Versions: 4.9 Reporter: Tom Fennelly Fix For: 4.9 CP1 JBoss AS5 + Java 6. If you have an esb app that looks like a combo of the security_saml and one of the wise examples.... you'll break. The saml code (Picketlink) requires the jboss-native version of the jaxws jars from the server/client folder, while the wise code requires the jaxws version from the ESB Server? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-3466) Small typo on programmers guide, Annotated Action Classes section

by Jehudi Castro (JIRA)

Small typo on programmers guide, Annotated Action Classes section ----------------------------------------------------------------- Key: JBESB-3466 URL: https://jira.jboss.org/browse/JBESB-3466 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.9 Environment: This is the version of the documentation that I'm looking at: http://jboss.org/jbossesb/docs/4.9/manuals/pdf/Programmers_Guide.pdf Reporter: Jehudi Castro Priority: Trivial Look for the section "4.1.4.2. @Process Method Return Values", page 39 fix the first word on the paragraph: "f the specified ESB Message location contains a value of the wrong type, a MessageDeliverException exception is thrown." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-3344) JAXRRegistryImpl does not unregister services correctly from jUDDI.

by Marek Baluch (JIRA)

JAXRRegistryImpl does not unregister services correctly from jUDDI. ------------------------------------------------------------------- Key: JBESB-3344 URL: https://jira.jboss.org/browse/JBESB-3344 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository, Rosetta Affects Versions: 4.7 CP1, 4.7 CP2 Reporter: Marek Baluch Priority: Blocker JAXRRegistryImpl does not unregister services correctly from jUDDI. Only bindings are deleted but the service itself remains in the registry. These orphaned service records cause also problems when there are more server instances in the cluster. How to reproduce ------------------- Just deploy and undeploy a QS. Then have a look in jUDDI console. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
9
0 / 0

[JBoss JIRA] Created: (JBESB-3460) Documentation - Apply XML and Grammar Patches to Community Docs

by David Le Sage (JIRA)

Documentation - Apply XML and Grammar Patches to Community Docs --------------------------------------------------------------- Key: JBESB-3460 URL: https://jira.jboss.org/browse/JBESB-3460 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.9 CP1 Reporter: David Le Sage Assignee: David Le Sage Fix For: 4.9 CP1 Apply first series of minor XML and grammar patches to community docs, in order to synchronise them with product docs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3405) Investigate an alternate approach for invoking CXF endpoints

by Magesh Kumar B (JIRA)

Investigate an alternate approach for invoking CXF endpoints ------------------------------------------------------------ Key: JBESB-3405 URL: https://jira.jboss.org/browse/JBESB-3405 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Reporter: Magesh Kumar B Fix For: 4.9 CP1 Currently CXFSOAPProcessor uses Dispatch API to invoke endpoints over SOAP/HTTP. See if it is possible to use CXF API to invoke the endpoints internally. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBESB-3469) Unable to unregister duplicate JMS endpoints attached to services

by Raghavan TV (JIRA)

Unable to unregister duplicate JMS endpoints attached to services ----------------------------------------------------------------- Key: JBESB-3469 URL: https://jira.jboss.org/browse/JBESB-3469 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment Affects Versions: 4.7 Environment: JBOSS-ESB-4.7 ORACLE 10G Solaris 10 / WindowsXP / HP-UX 11.x Reporter: Raghavan TV We observe duplicate JMS endpoints that are attached to the services. Tried to undeploy both service and messaging-endpoints but we continue to see duplicate jms endpoints. I've also posted a discussion related to this issue https://community.jboss.org/message/558481#558481 Thanks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1900) Current system date in sql-provider where-condition

by Raghavan TV (JIRA)

Current system date in sql-provider where-condition --------------------------------------------------- Key: JBESB-1900 URL: https://jira.jboss.org/jira/browse/JBESB-1900 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: JBoss ESB 4.3GA + JBoss 4.2.2 or JBOss 4.0.0 + Oracle 10g + Windows Xp or HP-UX 11.0 Reporter: Raghavan TV I have a simple table where I store my Orders. e.g. DB - Oracle 10g Table ORDER_QUEUE ---------------------------------------- ORDER_ID NUMBER(5) FIELD1 VARCHAR2(10) FIELD2 VARCHAR2(10) ORDER_DATE DATE ESB_STATUS VARCHAR2(1) TIMESTAMP_COL DATE ----------------------------------------- My requirement is to process only those records where ORDER_DATE = Current System Date that hosts my AppServer Am trying to work with the sample provided. I updated the where condition as follows and it works fine. <sql-bus busid="helloSQLChannel" > <sql-message-filter tablename="ORDER_QUEUE" status-column="ESB_STATUS" where-condition="TO_DATE(ORDER_DATE,'DD-MON-YYYY') = (SELECT TO_DATE(SYSDATE,'DD-MON-YYYY') FROM DUAL)" message-column="message" message-id-column="ORDER_ID" insert-timestamp-column="TIMESTAMP_COL" /> </sql-bus> [where-condition="TO_CHAR(ORDER_DATE,'DD-MON-YYYY') = (SELECT TO_CHAR(SYSDATE,'DD-MON-YYYY') FROM DUAL)"] But the query is more specific to a Oracle DB. If I decide to change the provider in the future, then this filter will fail! Also if the DB and AppServer are in different TZ, we have a problem Is there some other workaround to use the AppServer Date in the where-condition ? -- 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

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-3468) Propagate http-client-property configuration to SOAPProxyWsdlLoader.newLoader

by Kevin Conner (JIRA)

Propagate http-client-property configuration to SOAPProxyWsdlLoader.newLoader ----------------------------------------------------------------------------- Key: JBESB-3468 URL: https://jira.jboss.org/browse/JBESB-3468 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 CP3 SOAPProxyWsdlLoader.newLoader does not use the correct configuration when invoked from SOAPProxy or SOAPProxyWsdlContractPublisher.. As a consequence it has no visibility of any http-client-property elements that are configured on the action. This should retain current functionality as much as possible, only allowing changes to the WSDL configuration if configured. There will be two mechanisms that can be used to configure the WSDL access through the SOAPProxy use case - introduce wsdl-http-client-property elements for explicit configuration of the WSDL http client - introduce a "wsdlUseHttpClientProperties" property so that the http-client-property elements can also be used wsdl-http-client-property will override http-client-property. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3378) http-client-properties not propagated to HttpMethodParams

by David Ward (JIRA)

http-client-properties not propagated to HttpMethodParams --------------------------------------------------------- Key: JBESB-3378 URL: https://jira.jboss.org/browse/JBESB-3378 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Rosetta, Transports Affects Versions: 4.8 Reporter: David Ward If you set your config like this: <action ... class="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy"> ... <property name="http-client-properties"> <http-client-property name="http.method.retry-handler" value="com.foobar.MyRetryHandler"/> </property> or like this: <action ... class="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy"> ... <property name="file" value="http-client.properties"/> http-client.properties: http.method.retry-handler=com.foobar.MyRetryHandler , your custom retry handler is not picked up. This is NOT a bug in SOAPProxy. The bug is in both POSTHttpMethodFactory and GETHttpMethodFactory, where in the setConfiguration(ConfigTree):void method, the http-client-properties that are available in the passed-in ConfigTree are not set into the HttpMethod's HttpMethodParams. What should happen is that ANY property that starts with "http.method." should be set into the HttpMethodParams. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
14
0 / 0

[JBoss JIRA] Created: (JBESB-3463) Aggregator meta data object is not recreated when updating

by Kevin Conner (JIRA)

Aggregator meta data object is not recreated when updating ---------------------------------------------------------- Key: JBESB-3463 URL: https://jira.jboss.org/browse/JBESB-3463 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.9 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.9 CP1 The storing of the aggregator meta data was recently changed so that it is now saved in the message context, which duplicates references rather than passing by reference, however the value of that entry within the map remains the same. As a result we still use the same underlying object when the message is passed by reference with invm. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2010