June 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1830) Deployment support in Eclipse for ESB archives

by John Graham (JIRA)

Deployment support in Eclipse for ESB archives ---------------------------------------------- Key: JBESB-1830 URL: http://jira.jboss.com/jira/browse/JBESB-1830 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tooling Reporter: John Graham Assigned To: John Graham Eclipse tooling support for deploying ESB archives to servers -- 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

16 years

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1826) Eclipse Guvnor tools

by John Graham (JIRA)

Eclipse Guvnor tools -------------------- Key: JBESB-1826 URL: http://jira.jboss.com/jira/browse/JBESB-1826 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tooling Reporter: John Graham Assigned To: John Graham Create tools allowing use of Guvnor repositories in Eclipse -- 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

16 years

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1825) SOA Modeling tools in Eclipse

by John Graham (JIRA)

SOA Modeling tools in Eclipse ----------------------------- Key: JBESB-1825 URL: http://jira.jboss.com/jira/browse/JBESB-1825 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Tooling Reporter: John Graham Assigned To: John Graham Provide SOA Modeling tools in Eclipse -- 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

16 years

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1840) Add message profile specification support to SmooksAction

by Tom Fennelly (JIRA)

Add message profile specification support to SmooksAction --------------------------------------------------------- Key: JBESB-1840 URL: http://jira.jboss.com/jira/browse/JBESB-1840 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.3 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.4 Just something very basic - pick up the profile name from the message or the action config. A number of the examples are actually using this feature of Smooks - performing a different transformation on the message payload based on the profile spec on the message. -- 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

16 years

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1835) Exceptionhandling changes with InVM transport

by Haagen Hasle (JIRA)

Exceptionhandling changes with InVM transport --------------------------------------------- Key: JBESB-1835 URL: http://jira.jboss.com/jira/browse/JBESB-1835 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.3 Environment: the prebuilt jbossesb-server Reporter: Haagen Hasle I've tried to use the new InVM transport instead of JMS. When an exception occurs in my action something strange happens. When I use JMS, my code cathes a FaultMessageException from the call to the ServiceInvoker. When I use InVM transport, the exception seems to disappear. I see that the exception is not swallowd entirely, I see it in message.getFault(). But a FaultMessageException is never thrown from the ServiceInvoker. It's easy to reproduce, just modify the native_client quickstart to use InVM transport, and make sure it throws an exception in MyAction: Change MyAction like this: public Message playWithMessage(Message message) throws Exception { Body msgBody = message.getBody(); String contents = (String) msgBody.get(); if( contents.equalsIgnoreCase("throwexception") ) { throw new ActionProcessingException(new RuntimeException("Throw exception")); } // Reset the message body contents with the response... msgBody.add(("Hello From ESB MyAction: " + contents)); return message; } (And add ActionProcessingException as an import as well.) and change the jboss-esb.xml file to look like this: <?xml version = "1.0" encoding = "UTF-8"?> <jbossesb xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..." parameterReloadSecs="5"> <providers> </providers> <services> <service category="MyServiceCategory" name="MyNativeClientService" description="A WS Frontend speaks natively to the ESB" invmScope="GLOBAL"> <actions> <action name="displayAction" class="org.jboss.soa.esb.samples.quickstart.nativeclient.MyAction" process="displayMessage"> <property name="exceptionMethod" value="exceptionHandler"/> </action> <action name="playAction" class="org.jboss.soa.esb.samples.quickstart.nativeclient.MyAction" process="playWithMessage"> <property name="exceptionMethod" value="exceptionHandler"/> </action> <action name="finalDisplayAction" class="org.jboss.soa.esb.samples.quickstart.nativeclient.MyAction" process="displayMessage"> <property name="exceptionMethod" value="exceptionHandler"/> </action> </actions> </service> </services> </jbossesb> Note that it makes no difference if the action throws an ActionProcessingException, ActionProcessingFaultException or RuntimeException. If you call the WS from SoapUI and debug the application, you will see that the catch-block in the WS is never entered when you use InVM transport, but it is if you switch back to JMS. -- 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

16 years

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-1789) Disable smooks shutdown hook in esb environment

by Kevin Conner (JIRA)

Disable smooks shutdown hook in esb environment ----------------------------------------------- Key: JBESB-1789 URL: http://jira.jboss.com/jira/browse/JBESB-1789 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transformation Service Affects Versions: 4.3 Reporter: Kevin Conner Assigned To: Tom Fennelly Fix For: 4.4 Seen on shutdown when using an esb with SmooksAction java.lang.IllegalStateException: Shutdown in progress at java.lang.Shutdown.remove(Shutdown.java:104) at java.lang.Runtime.removeShutdownHook(Runtime.java:218) at org.milyn.cdr.SmooksResourceConfigurationStore.close(SmooksResourceConfigurationStore.java:374) at org.milyn.Smooks.close(Smooks.java:326) at org.jboss.soa.esb.actions.smooks.SmooksAction.destroy(SmooksAction.java:177) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.handleDestroy(ActionProcessingPipeline.java:552) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.destroy(ActionProcessingPipeline.java:278) -- 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

16 years

2
1
0 / 0

[JBoss JIRA] Created: (JBESB-1836) JBossRemoting CoyoteInvoker not forwarding request Path or Query params to JBossRemotingGatewayListener

by Tom Fennelly (JIRA)

JBossRemoting CoyoteInvoker not forwarding request Path or Query params to JBossRemotingGatewayListener ------------------------------------------------------------------------------------------------------- Key: JBESB-1836 URL: http://jira.jboss.com/jira/browse/JBESB-1836 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.3 Reporter: Tom Fennelly Fix For: 4.4 You can see this by checking the contents of the requestPayload on the InvocationRequest (supplied through the ServerInvocationHandler.invoke method). -- 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

16 years

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-1817) SOAPClient Wiki page needs update

by Ehsan Zanjani (JIRA)

SOAPClient Wiki page needs update --------------------------------- Key: JBESB-1817 URL: http://jira.jboss.com/jira/browse/JBESB-1817 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Environment: wiki page Reporter: Ehsan Zanjani When I changed my namespace to WebService namespace,it worked as well,I think your sample code namespace should change in wikipage <alias name="customerOrder" class="com.acme.order.Order" namespace="http://schemas.acme.com/services/CustomerOrder.xsd" /> [change] <alias name="customerOrder" class="com.acme.order.Order" namespace="http://www.acme.com/OrderManagement" /> for more info look at jboss forum. -- 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

16 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-354) Addition of a helloworld_sftp_action in the quickstarts

by Kevin Conner (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-354?page=all ] Kevin Conner updated JBESB-354: ------------------------------- Fix Version/s: 4.2.1 TP-FP3 (was: 4.2.1 TP-FP2) > Addition of a helloworld_sftp_action in the quickstarts > ------------------------------------------------------- > > Key: JBESB-354 > URL: http://jira.jboss.com/jira/browse/JBESB-354 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Examples > Affects Versions: 4.0 CR1 > Reporter: Bruno Georges > Assigned To: Kevin Conner > Priority: Minor > Fix For: 4.2.1 TP-FP3 > > -- 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

16 years

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-1637) Refactor documentation

by Mark Little (JIRA)

Refactor documentation ---------------------- Key: JBESB-1637 URL: http://jira.jboss.com/jira/browse/JBESB-1637 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 CP1 Reporter: Mark Little Assigned To: Mark Little Priority: Critical Fix For: 4.3 -- 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

16 years

2
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues June 2008