May 2008 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-1753) Update install/readme.txt

by Tom Cunningham (JIRA)

Update install/readme.txt ------------------------- Key: JBESB-1753 URL: http://jira.jboss.com/jira/browse/JBESB-1753 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.3 Update install/readme.txt to reflect that we are deploying in 4.2.2.GA now rather than 4.2.1.GA, remove instructions on patching 4.2.1GA with updated JBoss Remoting and Web Services JARs. -- 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, 11 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-1760) Error in jms_router queue deploy

by Tom Cunningham (JIRA)

Error in jms_router queue deploy -------------------------------- Key: JBESB-1760 URL: http://jira.jboss.com/jira/browse/JBESB-1760 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.3 Getting the following error deploying to jboss-4.2.2.GA + ESB and trying to run jms_router QS : 15:08:08,505 ERROR [STDERR] [Fatal Error] jbmq-queue-service.xml:17:5: Element type "mbean" must be followed by either attribute specifications, ">" or "/>". 15:08:08,507 ERROR [MainDeployer] Could not initialise deployment: file:/Users/tcunning/tools/jboss-4.2.2.GA/server/default/deploy/Quickstart_JMS_Router.esb org.jboss.deployment.DeploymentException: Element type "mbean" must be followed by either attribute specifications, ">" or "/>".; - nested throwable: (org.xml.sax.SAXParseException: Element type "mbean" must be followed by either attribute specifications, ">" or "/>".) at org.jboss.deployment.SARDeployer.init(SARDeployer.java:217) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:895) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) Caused by: org.xml.sax.SAXParseException: Element type "mbean" must be followed by either attribute specifications, ">" or "/>". at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.jboss.deployment.SARDeployer.parseDocument(SARDeployer.java:622) at org.jboss.deployment.SARDeployer.init(SARDeployer.java:181) ... 22 more 15:08:18,524 ERROR [STDERR] [Fatal Error] jbmq-queue-service.xml:17:5: Element type "mbean" must be followed by either attribute specifications, ">" or "/>". 15:08:18,525 ERROR [MainDeployer] Could not initialise deployment: file:/Users/tcunning/tools/jboss-4.2.2.GA/server/default/deploy/Quickstart_JMS_Router.esb org.jboss.deployment.DeploymentException: Element type "mbean" must be followed by either attribute specifications, ">" or "/>".; - nested throwable: (org.xml.sax.SAXParseException: Element type "mbean" must be followed by either attribute specifications, ">" or "/>".) at org.jboss.deployment.SARDeployer.init(SARDeployer.java:217) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:895) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) Caused by: org.xml.sax.SAXParseException: Element type "mbean" must be followed by either attribute specifications, ">" or "/>". at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.jboss.deployment.SARDeployer.parseDocument(SARDeployer.java:622) at org.jboss.deployment.SARDeployer.init(SARDeployer.java:181) ... 22 more -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1761) smooks_file_splitter errors

by Tom Cunningham (JIRA)

smooks_file_splitter errors --------------------------- Key: JBESB-1761 URL: http://jira.jboss.com/jira/browse/JBESB-1761 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Reporter: Tom Cunningham Assigned To: Tom Cunningham Fix For: 4.3 16:13:27,298 ERROR [MainDeployer] Could not initialise deployment: file:/Users/tcunning/tools/jboss-4.2.2.GA/server/default/deploy/Quickstart_smooks_file_splitter_router.esb org.jboss.deployment.DeploymentException: Element type "mbean" must be followed by either attribute specifications, ">" or "/>".; - nested throwable: (org.xml.sax.SAXParseException: Element type "mbean" must be followed by either attribute specifications, ">" or "/>".) at org.jboss.deployment.SARDeployer.init(SARDeployer.java:217) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872) at org.jboss.deployment.MainDeployer.init(MainDeployer.java:895) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) Caused by: org.xml.sax.SAXParseException: Element type "mbean" must be followed by either attribute specifications, ">" or "/>". at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at org.jboss.deployment.SARDeployer.parseDocument(SARDeployer.java:622) at org.jboss.deployment.SARDeployer.init(SARDeployer.java:181) ... 22 more -- 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, 11 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-1756) Update bpm_orchestration3 to remove the process signalling

by Kevin Conner (JIRA)

Update bpm_orchestration3 to remove the process signalling ---------------------------------------------------------- Key: JBESB-1756 URL: http://jira.jboss.com/jira/browse/JBESB-1756 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Kevin Conner Fix For: 4.3 bpm_orchestration3 uses the process signal command, which is no longer supported. Burr has provided an update which now uses the EPR and the jBPM callback service. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-1723) Wrong version identifier in MANIFEST.MF of jbossesb-rosetta.jar

by Martin Vecera (JIRA)

Wrong version identifier in MANIFEST.MF of jbossesb-rosetta.jar --------------------------------------------------------------- Key: JBESB-1723 URL: http://jira.jboss.com/jira/browse/JBESB-1723 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Build and Release, Rosetta Affects Versions: 4.2.1 CP2 Environment: Observed in embedded SOA-P 4.2.CP01 Reporter: Martin Vecera Fix For: 4.2.1 CP3 4.2.1 CP2 MANIFEST.MF reads: Name: JBoss ESB Specification-Title: jbossesb-server-4.2.1GA Specification-Version: 4.2.1GA Specification-Vendor: JBoss Implementation-Version: 4.2.1GA April 15 2008 I'd suppose to read "4.2.1CP2" and "4.2.1CP3" for future version. -- 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, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1706) Review documentation

by Kevin Conner (JIRA)

Review documentation -------------------- Key: JBESB-1706 URL: http://jira.jboss.com/jira/browse/JBESB-1706 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 Reporter: Kevin Conner Fix For: 4.3 Go through the documentation and review the contents. Check for consistent versioning information, updated actions, transports etc. -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (JBESB-1754) Review install/Deployment.txt

by Daniel Bevenius (JIRA)

Review install/Deployment.txt ----------------------------- Key: JBESB-1754 URL: http://jira.jboss.com/jira/browse/JBESB-1754 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Daniel Bevenius Assigned To: Daniel Bevenius -- 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, 11 months

3
5
0 / 0

[JBoss JIRA] Created: (JBESB-1751) StandAloneBootStrapper doesn't initialise the Registry instance in the RegistryFactory

by Tom Fennelly (JIRA)

StandAloneBootStrapper doesn't initialise the Registry instance in the RegistryFactory -------------------------------------------------------------------------------------- Key: JBESB-1751 URL: http://jira.jboss.com/jira/browse/JBESB-1751 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Registry and Repository, Rosetta Affects Versions: 4.2.1 TP-FP1 Reporter: Tom Fennelly Assigned To: Tom Fennelly 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

17 years, 11 months

2
12
0 / 0

[JBoss JIRA] Created: (JBESB-1720) Refresh Doc Indexes/TOCs before generating the PDFs

by Tom Fennelly (JIRA)

Refresh Doc Indexes/TOCs before generating the PDFs --------------------------------------------------- Key: JBESB-1720 URL: http://jira.jboss.com/jira/browse/JBESB-1720 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Documentation Reporter: Tom Fennelly 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

17 years, 11 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-1708) Update documentation PDFs

by Kevin Conner (JIRA)

Update documentation PDFs ------------------------- Key: JBESB-1708 URL: http://jira.jboss.com/jira/browse/JBESB-1708 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 Reporter: Kevin Conner 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

17 years, 11 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues May 2008