August 2007 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-885) Remove ESB specific configuration from jbossesb-server-base.zip

by Kevin Conner (JIRA)

Remove ESB specific configuration from jbossesb-server-base.zip --------------------------------------------------------------- Key: JBESB-885 URL: http://jira.jboss.com/jira/browse/JBESB-885 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 The jbossesb-server-base zip file should not contain any ESB specific configuration, this should always be handled by the build scripts. The current zip needs the WS modifications removing. -- 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

18 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-883) webservice_consumer1 QS does not run

by Kevin Conner (JIRA)

webservice_consumer1 QS does not run ------------------------------------ Key: JBESB-883 URL: http://jira.jboss.com/jira/browse/JBESB-883 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 Webservice_consumer1 fails with CNFE for org.apacheServiceInvoker..ws.scout.registry.ConnectionFactoryImpl There is a typo in the QS. This needs to be fixed and verified. -- 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

18 years, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-876) ServiceInvoker changes To field

by Mark Little (JIRA)

ServiceInvoker changes To field ------------------------------- Key: JBESB-876 URL: http://jira.jboss.com/jira/browse/JBESB-876 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.2 Milestone Release 3 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.1 Intern: "Not sure if this is a bug, but it didn't behave as I expected. If I set a To field in the message header then the ServiceInvoker will change that as it iterates over a series of registered eprs. Wouldn't it be better to try to keep the input message unchanged when deliverSync/deliverAsync return? As far as I can tell, nothing else of the input message is changed by the ESB at the sender side when it tries to deliver." -- 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

18 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-879) documentation: error in action processing pipeline

by Jaroslaw Kijanowski (JIRA)

documentation: error in action processing pipeline -------------------------------------------------- Key: JBESB-879 URL: http://jira.jboss.com/jira/browse/JBESB-879 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Jaroslaw Kijanowski Assigned To: Mark Little The ProgrammersGuide: If an Exception was thrown at any point in the pipeline, processing will be interrupted at that point, an error message will be logged, and contents of the 'exceptionMethod' tag will be analyzed and if present in the current action class, the method will be invoked using the Message returned by the last method in step 3. At present time, if no exceptionMethod was specified, the only output will be the logged error. This should be fixed. If an exception was thrown, the "exceptionMethod" tags of *all* action elements will be analyzed and invocations are made in the reverse order to the processing ones. -- 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

18 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-873) Revise the ServiceInvoker documentation within the ProgrammersGuide.

by Kevin Conner (JIRA)

Revise the ServiceInvoker documentation within the ProgrammersGuide. -------------------------------------------------------------------- Key: JBESB-873 URL: http://jira.jboss.com/jira/browse/JBESB-873 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Mark Little Fix For: 4.2 The ServiceInvoker class has changed recently, the documentation should reflect this. -- 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

18 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-867) Configure jbossesb-server webservices as part of build

by Kevin Conner (JIRA)

Configure jbossesb-server webservices as part of build ------------------------------------------------------ Key: JBESB-867 URL: http://jira.jboss.com/jira/browse/JBESB-867 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 -- 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

18 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-874) install/build.xml no longer applies jaxb intros XSLT

by Kevin Conner (JIRA)

install/build.xml no longer applies jaxb intros XSLT ---------------------------------------------------- Key: JBESB-874 URL: http://jira.jboss.com/jira/browse/JBESB-874 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration, Web Services Affects Versions: 4.2 Milestone Release 3 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.2 A change to the install/build.xml script has resulted in the jaxb intros XSLT being ignored on every invocation. The script was modified to ignore the transformation if a condition was present, unfortunately this condition is always present. -- 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

18 years, 8 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBESB-19) Create HTTP listener/receiver

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-19?page=comments#action_12373398 ] Mark Little commented on JBESB-19: ---------------------------------- Ask in the forums please. > Create HTTP listener/receiver > ----------------------------- > > Key: JBESB-19 > URL: http://jira.jboss.com/jira/browse/JBESB-19 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Release Process > Reporter: Mark Little > Assigned To: Johan Kumps > Fix For: 4.0 > > Attachments: AbstractConnectorServlet.java, NoEndpointSpecifiedException.java, RestConnectorServlet.java > > Time Spent: 1 day > Remaining Estimate: 0 minutes > > Either create one or leverage something that already exists (though for inclusion with JBossESB it should have a small footprint, i.e., not drag in a load of other non-essential classes). > What this means is that we need an HTTP-server side stack so that clients can send HTTP requests (PUT, POST, GET) and the ESB will interpret them appropriately. Currently JDK libraries provide only the client-side to HTTP interactions and no server-side. -- 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

18 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-19) Create HTTP listener/receiver

by Sonny Coccera (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-19?page=comments#action_12373329 ] Sonny Coccera commented on JBESB-19: ------------------------------------ Have these classes or has this functionality been added to the newest version of the JBoss ESB? I can't find these classes anywhere and there are no examples of using synchronous HTTP directly (except for a separate service which uses the ESB directly). > Create HTTP listener/receiver > ----------------------------- > > Key: JBESB-19 > URL: http://jira.jboss.com/jira/browse/JBESB-19 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Release Process > Reporter: Mark Little > Assigned To: Johan Kumps > Fix For: 4.0 > > Attachments: AbstractConnectorServlet.java, NoEndpointSpecifiedException.java, RestConnectorServlet.java > > Time Spent: 1 day > Remaining Estimate: 0 minutes > > Either create one or leverage something that already exists (though for inclusion with JBossESB it should have a small footprint, i.e., not drag in a load of other non-essential classes). > What this means is that we need an HTTP-server side stack so that clients can send HTTP requests (PUT, POST, GET) and the ESB will interpret them appropriately. Currently JDK libraries provide only the client-side to HTTP interactions and no server-side. -- 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

18 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-845) HSQLDB Problem when starting up second ESB instance

by Tom Cunningham (JIRA)

HSQLDB Problem when starting up second ESB instance --------------------------------------------------- Key: JBESB-845 URL: http://jira.jboss.com/jira/browse/JBESB-845 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Environment: Mac OS X Reporter: Tom Cunningham Assigned To: Tom Cunningham Priority: Critical Fix For: 4.2 When starting up a second ESB instance, I see the following error: 12:00:49,049 INFO [STDOUT] [Server@30d644]: Loaded properties from [/Users/tcunning/esb/jboss-4.2.1.GA/bin/server.properties] 12:00:49,050 INFO [STDOUT] [Server@30d644]: Initiating startup sequence... 12:00:49,053 ERROR [STDERR] [Server@30d644]: [Thread[HSQLDB Server @30d644,5,jboss]]: run()/openServerSocket(): 12:00:49,053 ERROR [STDERR] java.net.BindException: Address already in use at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359) at java.net.ServerSocket.bind(ServerSocket.java:319) at java.net.ServerSocket.<init>(ServerSocket.java:185) at org.hsqldb.HsqlSocketFactory.createServerSocket(Unknown Source) at org.hsqldb.Server.openServerSocket(Unknown Source) at org.hsqldb.Server.run(Unknown Source) at org.hsqldb.Server.access$000(Unknown Source) at org.hsqldb.Server$ServerThread.run(Unknown Source) Here's my steps to reproduce : 1) Install ESB on a fresh AS 2) Make a copy of the "default" directory called "second" 3) Edit server/default/conf/jboss-service.xml - change ServerName to ports-default and point StoreURL to wherever you are going to put your sample-bindings.xml file 4) Edit server/second/conf/jboss-service.xml - change ServerName to ports-01 and point StoreURL to wherever you are going to put your sample-bindings.xml file 5) Edit server/second/deploy/jbossesb.sar/esb.juddi.properties - change java.naming.provider.url to look at port 1199 6) Start first server 7) ./run.sh -c second >From my understanding, the -b option isn't needed if we're using the port-bindings. -- 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

18 years, 8 months

3
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues August 2007