October 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2910) Backwards incompatibility in deployment

by Lukáš Petrovický (JIRA)

Backwards incompatibility in deployment --------------------------------------- Key: JBESB-2910 URL: https://jira.jboss.org/jira/browse/JBESB-2910 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Services Affects Versions: 4.7 Reporter: Lukáš Petrovický Behavior of a scenario where an ESB archive contains a WAR archive has significantly changed. On SOA-P 5.0.0 ER1, if the WAR doesn't include a WEB-INF/jboss-web.xml file containing a <context-root /> specifying the context root for the web service, the endpoint becomes available with a different context root (and URL) than before. This can be observed for example with the webservice_consumer1 QS. If the stock QS is used, deploying its ESB archive produces following in the log: 2009-10-26 08:19:13,597 INFO [org.jboss.wsf.framework.management.DefaultEndpointRegistry] (HDScanner) register: jboss.ws:context=Quickstart_webservice_consumer1,endpoint=HelloWorldWS That is the SOA-P 4.x behavior. However, when the WAR's jboss-web.xml file is removed (and thus the context root isn't defined), following is produced in the log: 2009-10-26 08:16:10,275 INFO [org.jboss.wsf.framework.management.DefaultEndpointRegistry] (HDScanner) register: jboss.ws:context=Quickstart_webservice_consumer1-Quickstart_webservice_consumer1,endpoint=HelloWorldWS If this is an intentional incompatibility, it needs to be well documented. -- 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

16 years, 6 months

2
2
0 / 0

[JBoss JIRA] Updated: (JBESB-2813) Lazy lookup of EJBs in EJBProcessor

by Kevin Conner (JIRA)

[ https://jira.jboss.org/jira/browse/JBESB-2813?page=com.atlassian.jira.plu... ] Kevin Conner updated JBESB-2813: -------------------------------- Assignee: (was: Daniel Bevenius) Changing to lazy lookup means that the error happens at runtime rather than at deployment time. We can certainly look at making this behaviour optional but the default will definitely be deployment time errors. > Lazy lookup of EJBs in EJBProcessor > ----------------------------------- > > Key: JBESB-2813 > URL: https://jira.jboss.org/jira/browse/JBESB-2813 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Adapters > Affects Versions: 4.4, 4.5, 4.6 > Reporter: Martin Putz > Attachments: EJBProcessor.java > > > EJBProcessor performs lookup of remote EJBs at application startup. If the lookup fails, EJBProcessor throws an exception, so that the whole application cannot start. > This should be changed to a lazy lookup. -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-2899) Remove support for "production" config

by Kevin Conner (JIRA)

Remove support for "production" config -------------------------------------- Key: JBESB-2899 URL: https://jira.jboss.org/jira/browse/JBESB-2899 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.6 Reporter: Kevin Conner Fix For: 4.7 This is no longer part of the EAP/platform build, it is back to "default". -- 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

16 years, 6 months

1
9
0 / 0

[JBoss JIRA] Commented: (JBESB-2813) Lazy lookup of EJBs in EJBProcessor

by Noel Rocher (JIRA)

[ https://jira.jboss.org/jira/browse/JBESB-2813?page=com.atlassian.jira.plu... ] Noel Rocher commented on JBESB-2813: ------------------------------------ Please review and modify as you need. Some tests are needed in order to validate this version in the QA environment. I'm still doing some tests, but this is an urgent feature request. > Lazy lookup of EJBs in EJBProcessor > ----------------------------------- > > Key: JBESB-2813 > URL: https://jira.jboss.org/jira/browse/JBESB-2813 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Adapters > Affects Versions: 4.4, 4.5, 4.6 > Reporter: Martin Putz > Assignee: Daniel Bevenius > Attachments: EJBProcessor.java > > > EJBProcessor performs lookup of remote EJBs at application startup. If the lookup fails, EJBProcessor throws an exception, so that the whole application cannot start. > This should be changed to a lazy lookup. -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-2813) Lazy lookup of EJBs in EJBProcessor

by Noel Rocher (JIRA)

[ https://jira.jboss.org/jira/browse/JBESB-2813?page=com.atlassian.jira.plu... ] Noel Rocher updated JBESB-2813: ------------------------------- Attachment: EJBProcessor.java EJBProcessor new version proposition > Lazy lookup of EJBs in EJBProcessor > ----------------------------------- > > Key: JBESB-2813 > URL: https://jira.jboss.org/jira/browse/JBESB-2813 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Adapters > Affects Versions: 4.4, 4.5, 4.6 > Reporter: Martin Putz > Assignee: Daniel Bevenius > Attachments: EJBProcessor.java > > > EJBProcessor performs lookup of remote EJBs at application startup. If the lookup fails, EJBProcessor throws an exception, so that the whole application cannot start. > This should be changed to a lazy lookup. -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-2900) Continue behaviour for stateful rules sessions no longer works

by Kevin Conner (JIRA)

Continue behaviour for stateful rules sessions no longer works -------------------------------------------------------------- Key: JBESB-2900 URL: https://jira.jboss.org/jira/browse/JBESB-2900 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.6 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 The continue behaviour for stateful rules sessions no longer behaves as originally intended. Each invocation is now continuing the execution of the previous session, irrespective of the value of continuation. -- 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

16 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2887) facts retracted from session when in stateful mode

by Jaroslaw Kijanowski (JIRA)

facts retracted from session when in stateful mode -------------------------------------------------- Key: JBESB-2887 URL: https://jira.jboss.org/jira/browse/JBESB-2887 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.6 Environment: trunk rev 29538 Reporter: Jaroslaw Kijanowski Assignee: Daniel Bevenius I have a simple rule: when $si:SensorInfo($id:id) from entry-point "SensorEntryPoint" $s:Sensor(id == $id) from entry-point "SensorEntryPoint" then System.out.println("SI = "+$si.getAvg()+"; S = "+$s.getValue()); end The BRP is configured in stateful mode. The first message is sent. This sets 'dispose' and 'continue' to false and adds 2 objects (Sensor and SensorInfo) to the body. Rule fire. The second message is sent. This sets 'dispose' to false and 'continue' to true and adds 1 object (Sensor) to the body. Rule does not fire, but should. The third message is sent. This sets 'dispose' and 'continue' to true and adds 1 object (Sensor) to the body. Rule does not fire, but should. It looks like the SensorInfo object has been removed from the session, hence the rule did not fire. -- 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

16 years, 6 months

2
15
0 / 0

[JBoss JIRA] Created: (JBESB-2895) AS5 installation writes into common/lib

by Kevin Conner (JIRA)

AS5 installation writes into common/lib --------------------------------------- Key: JBESB-2895 URL: https://jira.jboss.org/jira/browse/JBESB-2895 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.6 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 The following are written into common/lib rather than the server lib. commons-httpclient-3.0.1.jar h2-1.0.68.jar jboss-identity-bindings-1.0.0.beta3.pre.jar jboss-identity-bindings-jboss-1.0.0.beta3.pre.jar jboss-identity-fed-api-1.0.0.beta3.pre.jar jboss-identity-fed-core-1.0.0.beta3.pre.jar jboss-identity-fed-model-1.0.0.beta3.pre.jar jboss-identity-web-1.0.0.beta3.pre.jar jboss-identity-xmlsec-model-1.0.0.beta3.pre.jar xmlsec-1.4.3.jar Also, moving httpclient has broken the jBPM quickstarts. -- 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

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2785) Add synchronous service invocation action

by Kevin Conner (JIRA)

Add synchronous service invocation action ----------------------------------------- Key: JBESB-2785 URL: https://jira.jboss.org/jira/browse/JBESB-2785 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.6 Reporter: Kevin Conner Fix For: 4.7 Add an action to invoke an ESB service synchronously. It should be made clear in the documentation that this can only be used when there is no active transaction and that asynchronous invocations are to be preferred for reasons of performance/scaling. -- 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

16 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-2894) Remove slf4j installation for as5

by Kevin Conner (JIRA)

Remove slf4j installation for as5 --------------------------------- Key: JBESB-2894 URL: https://jira.jboss.org/jira/browse/JBESB-2894 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Build and Release Affects Versions: 4.6 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.7 These jars are already in the as5 server -- 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

16 years, 6 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues October 2009