March 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-494) Version mismatch between ESB 4.2MR1 - and JBoss Messaging server

by Len DiMaggio (JIRA)

Version mismatch between ESB 4.2MR1 - and JBoss Messaging server ---------------------------------------------------------------- Key: JBESB-494 URL: http://jira.jboss.com/jira/browse/JBESB-494 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 1 Environment: jbossesb-4.2 (from src: jbossesb-4.2MR1-src.zip) jboss-4.0.5.GA (from src: jboss-4.0.5.GA-src.tar.gz) JBoss Messaging server (jboss-messaging-1.0.1.SP4-src) Sun Java 1.5 RHEL5 Reporter: Len DiMaggio Assigned To: Mark Little This JIRA tracks the issue raised in ESB user forum: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033350#4033350 According to Kurt, the versionID mismatch is due to patched jar files. This JIRA is thin on details - Kurt, can you elaborate? Thanks! runtest: [echo] Runs Test JMS Sender [java] Exception in thread "main" javax.naming.CommunicationException [Root exception is java.io.InvalidClassException: org.jboss.jms.client.delegate.DelegateSupport; local class incompatible: stream classdesc serialVersionUID = 8005108339439737469, local class serialVersionUID = -1723908125830723356] -- 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

17 years, 1 month

2
2
0 / 0

[JBoss JIRA] Updated: (JBESB-398) The use of java.net.URL doesnt allow support for protcols such as ftps, sftp. Refactor to use URI instead.

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-398?page=all ] Mark Little updated JBESB-398: ------------------------------ Component/s: Rosetta Transports > The use of java.net.URL doesnt allow support for protcols such as ftps, sftp. Refactor to use URI instead. > ----------------------------------------------------------------------------------------------------------- > > Key: JBESB-398 > URL: http://jira.jboss.com/jira/browse/JBESB-398 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta, Transports > Affects Versions: 4.0 CR1 > Reporter: Bruno Georges > Assigned To: Mark Little > Fix For: 4.2 Milestone Release 2 > > Original Estimate: 2 days > Time Spent: 30 minutes > Remaining Estimate: 1 day, 7 hours, 30 minutes > > Exception is thrown when using sftp/ftps protocols. > java.net.MalformedURLException: unknown protocol: sftp > Mark: We should really be using URIs everywhere since EPRs are based on WS-A, which is URI/IRI based. -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-418) Catch-All/Otherwise/Default for CBR

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-418?page=all ] Mark Little updated JBESB-418: ------------------------------ Component/s: Content Based Routing > Catch-All/Otherwise/Default for CBR > ----------------------------------- > > Key: JBESB-418 > URL: http://jira.jboss.com/jira/browse/JBESB-418 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Content Based Routing > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Kurt Stam > Priority: Critical > Fix For: 4.2 Milestone Release 2 > > > For CBR, it currently has no exception handling. -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-437) Beans based configuration option for actions

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-437?page=comments#action_12357603 ] Mark Little commented on JBESB-437: ----------------------------------- Don't worry about it. > Beans based configuration option for actions > -------------------------------------------- > > Key: JBESB-437 > URL: http://jira.jboss.com/jira/browse/JBESB-437 > Project: JBoss ESB > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: Configuration > Reporter: Rex Sheridan > Assigned To: Rex Sheridan > Priority: Minor > Fix For: 4.2 Milestone Release 2 > > Attachments: ActionBeanConfigurator.java, ActionProcessingPipeline.java, BeanConfigurator.java, FTPEprEditor.java, JbpmProcessAction.java, NotificationTarget.java, NotifyFTP.java > > > This is a first pass at a beans based configuration approach for actions and notification targets. -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-437) Beans based configuration option for actions

by Rex Sheridan (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-437?page=comments#action_12357601 ] Rex Sheridan commented on JBESB-437: ------------------------------------ I know, I know :-) I currently have higher priority stuff going on at my company. > Beans based configuration option for actions > -------------------------------------------- > > Key: JBESB-437 > URL: http://jira.jboss.com/jira/browse/JBESB-437 > Project: JBoss ESB > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: Configuration > Reporter: Rex Sheridan > Assigned To: Rex Sheridan > Priority: Minor > Fix For: 4.2 Milestone Release 2 > > Attachments: ActionBeanConfigurator.java, ActionProcessingPipeline.java, BeanConfigurator.java, FTPEprEditor.java, JbpmProcessAction.java, NotificationTarget.java, NotifyFTP.java > > > This is a first pass at a beans based configuration approach for actions and notification targets. -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Assigned: (JBESB-437) Beans based configuration option for actions

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-437?page=all ] Mark Little reassigned JBESB-437: --------------------------------- Assignee: Rex Sheridan (was: Kevin Conner) Since you now have JIRA access :-) > Beans based configuration option for actions > -------------------------------------------- > > Key: JBESB-437 > URL: http://jira.jboss.com/jira/browse/JBESB-437 > Project: JBoss ESB > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: Configuration > Reporter: Rex Sheridan > Assigned To: Rex Sheridan > Priority: Minor > Fix For: 4.2 Milestone Release 2 > > Attachments: ActionBeanConfigurator.java, ActionProcessingPipeline.java, BeanConfigurator.java, FTPEprEditor.java, JbpmProcessAction.java, NotificationTarget.java, NotifyFTP.java > > > This is a first pass at a beans based configuration approach for actions and notification targets. -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-437) Beans based configuration option for actions

by Rex Sheridan (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-437?page=comments#action_12357599 ] Rex Sheridan commented on JBESB-437: ------------------------------------ I don't really understand how ConfigTree().childPropertyList() would solve the problem. ConfigTree is a pull based configuration approach as opposed to a push based one. I simply want my action class to look like the following: class MyAction { private String someProp; private int count; public Message process(Message message) throws Exception { .... } public void setSomeProp(String val) { this.someProp = val; } public void setCount(int val) { this.count = val; } } And the configuration would look similar to: <action name="anAction" class="MyAction"> <property name="someProp" value="foo"></property> <property name="count" value="5"></property> </action> Notice how MyAction doesn't take a ConfigTree in its constructor. Its values are populated automatically just by following JavaBean conventions. > Beans based configuration option for actions > -------------------------------------------- > > Key: JBESB-437 > URL: http://jira.jboss.com/jira/browse/JBESB-437 > Project: JBoss ESB > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: Configuration > Reporter: Rex Sheridan > Assigned To: Kevin Conner > Priority: Minor > Fix For: 4.2 Milestone Release 2 > > Attachments: ActionBeanConfigurator.java, ActionProcessingPipeline.java, BeanConfigurator.java, FTPEprEditor.java, JbpmProcessAction.java, NotificationTarget.java, NotifyFTP.java > > > This is a first pass at a beans based configuration approach for actions and notification targets. -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-417) Service lifecycle

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-417?page=all ] Mark Little updated JBESB-417: ------------------------------ Fix Version/s: 4.2 Milestone Release 2 > Service lifecycle > ----------------- > > Key: JBESB-417 > URL: http://jira.jboss.com/jira/browse/JBESB-417 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Management, Rosetta > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 5.0 Milestone Release 1, 4.2 Milestone Release 2 > > > Both simple lifecycle on single bus as well as dev, test, staging, production management -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-437) Beans based configuration option for actions

by Esteban Schifman (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-437?page=comments#action_12357597 ] Esteban Schifman commented on JBESB-437: ---------------------------------------- Perhaps the ConfigTree().childPropertyList() is all there is to it > Beans based configuration option for actions > -------------------------------------------- > > Key: JBESB-437 > URL: http://jira.jboss.com/jira/browse/JBESB-437 > Project: JBoss ESB > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: Configuration > Reporter: Rex Sheridan > Assigned To: Kevin Conner > Priority: Minor > Fix For: 4.2 Milestone Release 2 > > Attachments: ActionBeanConfigurator.java, ActionProcessingPipeline.java, BeanConfigurator.java, FTPEprEditor.java, JbpmProcessAction.java, NotificationTarget.java, NotifyFTP.java > > > This is a first pass at a beans based configuration approach for actions and notification targets. -- 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

17 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-438) Controlled shutdown

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-438?page=all ] Mark Little updated JBESB-438: ------------------------------ Fix Version/s: 5.0 Milestone Release 1 (was: 5.0) > Controlled shutdown > ------------------- > > Key: JBESB-438 > URL: http://jira.jboss.com/jira/browse/JBESB-438 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Rosetta, Transports > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Kevin Conner > Fix For: 4.2 Milestone Release 2, 5.0 Milestone Release 1 > > > During a controlled shutdown, the ESB should prevent any further message inflow but allow all messages being processed/delivered to finish. -- 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

17 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 2007