July 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1673) SOA platform changed upload URL for jBPM

by Kevin Conner (JIRA)

SOA platform changed upload URL for jBPM ---------------------------------------- Key: JBESB-1673 URL: http://jira.jboss.com/jira/browse/JBESB-1673 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP2 Reporter: Kevin Conner Fix For: 4.2.1 CP3 The SOA platform has changed the URL used for uploading the process definitions for the 'production' server instance. The consequence of this is that the QSes cannot deploy their process definitions through the build.xml file. The mapping should read <servlet-mapping> <servlet-name>GDP Deployer Servlet</servlet-name> <url-pattern>/upload/*</url-pattern> </servlet-mapping> but now reads <servlet-mapping> <servlet-name>GDP Deployer Servlet</servlet-name> <url-pattern>/app/upload/*</url-pattern> </servlet-mapping> The ant task is still using http://localhost:8080/jbpm-console/upload -- 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, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBESB-1651) DBMessageStoreImpl explicitly setting the Transaction Isolation levels for message redelivery - breaking on Oracle

by Tom Fennelly (JIRA)

DBMessageStoreImpl explicitly setting the Transaction Isolation levels for message redelivery - breaking on Oracle ------------------------------------------------------------------------------------------------------------------ Key: JBESB-1651 URL: http://jira.jboss.com/jira/browse/JBESB-1651 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Message Store, Rosetta Affects Versions: 4.2.1 CP2, 4.2.1 CP1 Reporter: Tom Fennelly Fix For: 4.2.1 CP3 DBMessageStoreImpl.redeliver is explicitly setting the isolation level to TRANSACTION_READ_UNCOMMITTED. Oracle doesn't support or like this... http://www.oracle.com/technology/oramag/oracle/05-nov/o65asktom.html Should be configurable - or just come directly from the datasource config. -- 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, 4 months

5
10
0 / 0

[JBoss JIRA] Created: (JBESB-1664) Add an expected output portion to jms_transacted QS

by Tom Cunningham (JIRA)

Add an expected output portion to jms_transacted QS --------------------------------------------------- Key: JBESB-1664 URL: http://jira.jboss.com/jira/browse/JBESB-1664 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.2.1 CP3 Add an "expected output" portion to the jms_transacted QS. -- 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, 4 months

5
14
0 / 0

[JBoss JIRA] Created: (JBESB-1663) Lifecycle Unit Test does not work

by Mark Little (JIRA)

Lifecycle Unit Test does not work --------------------------------- Key: JBESB-1663 URL: http://jira.jboss.com/jira/browse/JBESB-1663 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2.1 CP2 Reporter: Mark Little Assigned To: Kevin Conner Priority: Minor Fix For: 4.3 // assertEquals(LifecycleResourceManager.DEFAULT_IDENTITY, first.getDestroyId()) ; -- 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, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1639) jms_secured quickstart does not work in the SOA platform

by Kevin Conner (JIRA)

jms_secured quickstart does not work in the SOA platform -------------------------------------------------------- Key: JBESB-1639 URL: http://jira.jboss.com/jira/browse/JBESB-1639 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 CP2 Reporter: Kevin Conner Fix For: 4.2.1 CP3 This quickstart attempts to modify the messaging security policy by updating the property files under conf, but the SOA platform defines a messaging policy to retrieve this information from a database. The required credentials are therefore not found when running the quickstart. -- 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, 4 months

3
5
0 / 0

[JBoss JIRA] Commented: (JBESB-1633) MBeanServerLocator.locate always returns the first item in the map instead of a lookup

by Darrin Mison (JIRA)

[ https://jira.jboss.org/jira/browse/JBESB-1633?page=com.atlassian.jira.plu... ] Darrin Mison commented on JBESB-1633: ------------------------------------- Proposed SOA 4.2 TP02 Release Note: MBeanServerLocator.locate now performs a correct MBean lookup by name > MBeanServerLocator.locate always returns the first item in the map instead of a lookup > -------------------------------------------------------------------------------------- > > Key: JBESB-1633 > URL: https://jira.jboss.org/jira/browse/JBESB-1633 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: 4.2.1, 4.2.1 CP1 > Reporter: Narayanan Raghavan > Assignee: Kevin Conner > Fix For: 4.3, 4.2.1 CP3 > > > The MBeanServerLocator.locate() method always returns the first item in the map and does not look-up the MBean by name. This always fails while looking up any MBean unless it happens to be the first one in the map. > Affected archive/ file: > soap.esb > services/soap/src/main/java/org/jboss/soa/esb/actions/soap/SoapUIInvoker.java > The constructor in SoapUIInvoker.java looks up the MBeanSever via the locate method which does not return the jboss.esb:service=SoapUIClientService MBean > mbeanServer = MBeanServerLocator.locate(); > The locateJboss function iterates through the map to find the relevant MBean. The above code should be changed to use > MBeanServerLocator.locateJboss(); > Thanks! -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-1636) MBean dependencies specify the datasource but not the initialiser

by Kevin Conner (JIRA)

MBean dependencies specify the datasource but not the initialiser ----------------------------------------------------------------- Key: JBESB-1636 URL: http://jira.jboss.com/jira/browse/JBESB-1636 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Configuration Affects Versions: 4.2.1, 4.2.1 CP2 Reporter: Kevin Conner Fix For: 4.2.1 CP3, 4.3 The result of this dependency is that there is a race between the user of the datasource and the configuration of the tables. -- 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, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-1635) The JbpmService MBean is missing a dependency

by Kevin Conner (JIRA)

The JbpmService MBean is missing a dependency --------------------------------------------- Key: JBESB-1635 URL: http://jira.jboss.com/jira/browse/JBESB-1635 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.2.1, 4.2.1 CP2 Reporter: Kevin Conner Fix For: 4.2.1 CP3, 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, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (JBESB-1627) Support authentication on outgoing JMS (i.e. JMSRouter)

by David Smiley (JIRA)

Support authentication on outgoing JMS (i.e. JMSRouter) ------------------------------------------------------- Key: JBESB-1627 URL: http://jira.jboss.com/jira/browse/JBESB-1627 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David Smiley JMSRouter doesn't support authenticating to JMS, and it should. This should be easy to add. Note: related to JBESB-1404 -- 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, 4 months

5
8
0 / 0

[JBoss JIRA] Created: (JBESB-1595) Remove JNDI default configuration from quickstart jboss-esb.xml files

by Kevin Conner (JIRA)

Remove JNDI default configuration from quickstart jboss-esb.xml files --------------------------------------------------------------------- Key: JBESB-1595 URL: http://jira.jboss.com/jira/browse/JBESB-1595 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.2.1 CP1 Reporter: Kevin Conner Fix For: 4.2.1 CP2 Specifying the default JNDI configuration in the quickstart jboss-esb.xml files is unnecessary and prevents deployment if the server has been bound with a different configuration. We should remove these configurations from the quickstarts and update the readme files. -- 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, 4 months

4
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues July 2008