August 2010 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-3432) Quickstart webservie_producer deployment.xml file contains an invalid newline character

by Tom Fennelly (JIRA)

Quickstart webservie_producer deployment.xml file contains an invalid newline character ---------------------------------------------------------------------------------------- Key: JBESB-3432 URL: https://jira.jboss.org/browse/JBESB-3432 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3431) Quickstart webservie_mtom deployment.xml file contains an invalid newline character

by Tom Fennelly (JIRA)

Quickstart webservie_mtom deployment.xml file contains an invalid newline character ------------------------------------------------------------------------------------ Key: JBESB-3431 URL: https://jira.jboss.org/browse/JBESB-3431 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.9 Causes the following exception... DEPLOYMENTS IN ERROR: Deployment "vfszip:/Users/tfennelly/packs/jboss-5.1.0.GA/server/default/deploy/Quickstart_Security_Cert.esb/" is in error due to the following reason(s): javax.management.MalformedObjectNameException: Newline in quoted value at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993) at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939) at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:369) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:637) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3430) Change manager name in esb.juddi.client.xml to 'uddi-portlet-manager'

by Kevin Conner (JIRA)

Change manager name in esb.juddi.client.xml to 'uddi-portlet-manager' --------------------------------------------------------------------- Key: JBESB-3430 URL: https://jira.jboss.org/browse/JBESB-3430 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.8 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.9 If this is not done then the uddi-console cannot retrieve the correct manager. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-3409) Document MRG as a provider in docbook docs

by Tom Cunningham (JIRA)

Document MRG as a provider in docbook docs ------------------------------------------ Key: JBESB-3409 URL: https://jira.jboss.org/browse/JBESB-3409 Project: JBoss ESB Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Documentation Reporter: Tom Cunningham Assignee: Tom Cunningham Fix For: 4.9 Merge MRG-as-provider changes to docbook docs: [tcunning@localhost docs]$ svn log AdministrationGuide.odt | more ------------------------------------------------------------------------ r34149 | tcunning | 2010-07-23 16:02:46 -0400 (Fri, 23 Jul 2010) | 3 lines JBESB-3370 Document use of MRG as JMS provider. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3412) All webservice_proxy_* quickstarts are broken

by David Ward (JIRA)

All webservice_proxy_* quickstarts are broken --------------------------------------------- Key: JBESB-3412 URL: https://jira.jboss.org/browse/JBESB-3412 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples, Web Services Environment: JDK 1.5 + AS 4.2.3 and JDK 1.6 + AS 5.1.0 Reporter: David Ward Priority: Blocker Fix For: 4.9 Each of the webservice_proxy_* quickstarts are broken in some way. webservice_proxy_basic, webservice_proxy_security and webservice_proxy_versioning all have problem with their WSDL contracts being empty from the http//localhost:8080/contract/ web application. Light debugging showed that the reason for this is that ContractProviderLifecycleResource, while having it's map being propertly populated with the appropriate lifecycle resource (deployment) ID + ContractProvider instance at deployment, is returning null when the HttpGatewayServlet attempts to get at it's appropriate ContractProvider. The reason is that during the thread of execution behind the HttpGatewayServlet, when calling ContractProviderLifecycleResource.buildKey(svc_cat, svc_name), LifecycleResourceManager.getSingleton().getIdentity() is returning DEFAULT-ID (or whatever it's called) instead of the actual deployment ID. This *USED* to work, so I don't know what changed environment-wise. webservice_proxy_routed doesn't provide a contract (no HTTP endpoints), so it's N/A to that quickstart. webservice_proxy_routed doesn't provide a contract either (no HTTP endpoints), however it has a different problem. It appears the work done in JBESB-3372 ("Move SOAP services away from JBossWS-Native implementation") has a bug when using JBossWS-Native. I thought the purpose was that both the Native and CXF stacks should work. If only the CXF stack should work, we shouldn't release ESB .org with Native. Anyway, after lightly looking at the code changes, it appears that there is a problem with the mappings being done. Specifically the same QName for Operation/Binding is being reused everywhere, even if there is more than one. When you run the quickstart with "ant saygoodbye", it work. When you run the quickstart with "ant sayhello" it breaks. This is because the goodbye QName is what was used. For example, "{http://webservice_proxy_routed/goodbye}GoodbyeBinding" and "{http://webservice_proxy_routed/goodbye}sayGoodbye". This is fine for "ant rungoodbye", but when you run "ant runhello" you get, "ERROR [SOAPFaultHelperJAXWS] SOAP request exception org.jboss.ws.core.CommonSOAPFaultException: Endpoint {http://webservice_proxy_routed/goodbye}GoodbyePort does not contain operation meta data for: {http://webservice_proxy_routed/hello}sayHello". So, obviously the mapping work done during initialization is busted in that it won't support more than one. In fact, looking at the deployment INFO being logged again, you will see the set of "[SOAPProxy] mapped abc [...] to xyz [...]" mappings twice, but both sets for GOODBYE. Nothing for HELLO. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
16
0 / 0

[JBoss JIRA] Created: (JBESB-3424) Typos in the Programmers Guide, Transport Specific Type Implementations section

by Jehudi Castro (JIRA)

Typos in the Programmers Guide, Transport Specific Type Implementations section ------------------------------------------------------------------------------- Key: JBESB-3424 URL: https://jira.jboss.org/browse/JBESB-3424 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.8 Reporter: Jehudi Castro On the page 81, the second transport specific implementation listed is SQL but the tag <ftp-bus> is used. Same with the fifth one, the transport specific implementation is File System but the tag <sql-bus> is used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBESB-2971) Document there are no guarantees that the format on contents of EPR will remain the same

by Taro Yasuma (JIRA)

Document there are no guarantees that the format on contents of EPR will remain the same ---------------------------------------------------------------------------------------- Key: JBESB-2971 URL: https://jira.jboss.org/jira/browse/JBESB-2971 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.4 CP3 Reporter: Taro Yasuma See SOA-1589. -- 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

15 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (JBESB-3427) ReturnJMSMessage class (simple_cbr quickstart) not closing JMS session and connection before exiting.

by Tom Fennelly (JIRA)

ReturnJMSMessage class (simple_cbr quickstart) not closing JMS session and connection before exiting. ----------------------------------------------------------------------------------------------------- Key: JBESB-3427 URL: https://jira.jboss.org/browse/JBESB-3427 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3429) ReturnJMSMessage class (transform_XML2POJO quickstart) not closing JMS session and connection before exiting.

by Tom Fennelly (JIRA)

ReturnJMSMessage class (transform_XML2POJO quickstart) not closing JMS session and connection before exiting. ------------------------------------------------------------------------------------------------------------- Key: JBESB-3429 URL: https://jira.jboss.org/browse/JBESB-3429 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.9 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-3426) Quickstart security_cert deployment.xml file contains an invalid newline character

by Tom Fennelly (JIRA)

Quickstart security_cert deployment.xml file contains an invalid newline character ----------------------------------------------------------------------------------- Key: JBESB-3426 URL: https://jira.jboss.org/browse/JBESB-3426 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Examples Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.9 Causes the following exception... DEPLOYMENTS IN ERROR: Deployment "vfszip:/Users/tfennelly/packs/jboss-5.1.0.GA/server/default/deploy/Quickstart_Security_Cert.esb/" is in error due to the following reason(s): javax.management.MalformedObjectNameException: Newline in quoted value at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993) at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939) at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:369) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:637) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 9 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 August 2010