January 2013 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3880) Changes to jUDDI initialisation code to allow use of spaces within directories

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3880?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3880: ------------------------------------------------ kconner(a)redhat.com made a comment on [bug 880892|https://bugzilla.redhat.com/show_bug.cgi?id=880892] The patch addresses the jUDDI specific startup issue and not the WS problems. In order to workaround the JBossWS issue you must add the following to the startup 'add -Dorg.jboss.net.protocol.file.useURI=false' There is more information on the WS/EAP issue in JBPAPP-10417 > Changes to jUDDI initialisation code to allow use of spaces within directories > ------------------------------------------------------------------------------ > > Key: JBESB-3880 > URL: https://issues.jboss.org/browse/JBESB-3880 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Registry and Repository > Affects Versions: 4.11 CP2 > Reporter: Kevin Conner > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > Attachments: juddi.patch > > > The jUDDI code requires a correctly encoded URI to be passed but we are not escaping them correctly. The attached changes need to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3880) Changes to jUDDI initialisation code to allow use of spaces within directories

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3880?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3880: ------------------------------------------------ Jiri Pechanec <jpechane(a)redhat.com> changed the Status of [bug 880892|https://bugzilla.redhat.com/show_bug.cgi?id=880892] from VERIFIED to MODIFIED > Changes to jUDDI initialisation code to allow use of spaces within directories > ------------------------------------------------------------------------------ > > Key: JBESB-3880 > URL: https://issues.jboss.org/browse/JBESB-3880 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Registry and Repository > Affects Versions: 4.11 CP2 > Reporter: Kevin Conner > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > Attachments: juddi.patch > > > The jUDDI code requires a correctly encoded URI to be passed but we are not escaping them correctly. The attached changes need to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3880) Changes to jUDDI initialisation code to allow use of spaces within directories

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3880?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3880: ------------------------------------------------ Jiri Pechanec <jpechane(a)redhat.com> made a comment on [bug 880892|https://bugzilla.redhat.com/show_bug.cgi?id=880892] The issue is still present. When starting the server with JBossWS native then an exception is thrown 09:09:52,061 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/home/jpechane/releases/531%20ER3/jboss-as/server/default/deploy/juddiv3.war/ state=PreReal mode=Manual requiredState=Real org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/home/jpechane/releases/531%20ER3/jboss-as/server/default/deploy/juddiv3.war/ at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:185) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543) at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) at org.jboss.Main.boot(Main.java:229) at org.jboss.Main$1.call(Main.java:561) at org.jboss.Main$1.call(Main.java:557) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.lang.Thread.run(Thread.java:722) Caused by: org.jboss.ws.metadata.wsdl.WSDLException: Cannot parse wsdlLocation: file:/home/jpechane/releases/531 ER3/jboss-as/server/default/tmp/jbossws/UDDICustodyTransferService_8a4a9304b23e9f42efd6518f596af799.wsdl at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.getDocument(WSDLDefinitionsFactory.java:191) at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:109) at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:293) at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:176) at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:52) at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:62) at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.start(UnifiedMetaDataDeploymentAspect.java:64) at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:129) at org.jboss.wsf.container.jboss50.deployer.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:76) at org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:60) at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:55) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) ... 32 more Caused by: java.io.IOException at org.jboss.net.protocol.file.FileURLConnection.<init>(FileURLConnection.java:102) at org.jboss.net.protocol.file.Handler.openConnection(Handler.java:40) at java.net.URL.openConnection(URL.java:969) at java.net.URL.openStream(URL.java:1035) at org.jboss.ws.core.utils.ResourceURL.openStream(ResourceURL.java:55) at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.getDocument(WSDLDefinitionsFactory.java:167) ... 43 more Caused by: java.net.URISyntaxException: Illegal character in path at index 32: file:/home/jpechane/releases/531 ER3/jboss-as/server/default/tmp/jbossws/UDDICustodyTransferService_8a4a9304b23e9f42efd6518f596af799.wsdl at java.net.URI$Parser.fail(URI.java:2829) at java.net.URI$Parser.checkChars(URI.java:3002) at java.net.URI$Parser.parseHierarchical(URI.java:3086) at java.net.URI$Parser.parse(URI.java:3034) at java.net.URI.<init>(URI.java:595) at java.net.URL.toURI(URL.java:936) at org.jboss.net.protocol.file.FileURLConnection.<init>(FileURLConnection.java:85) ... 48 more > Changes to jUDDI initialisation code to allow use of spaces within directories > ------------------------------------------------------------------------------ > > Key: JBESB-3880 > URL: https://issues.jboss.org/browse/JBESB-3880 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Registry and Repository > Affects Versions: 4.11 CP2 > Reporter: Kevin Conner > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > Attachments: juddi.patch > > > The jUDDI code requires a correctly encoded URI to be passed but we are not escaping them correctly. The attached changes need to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3880) Changes to jUDDI initialisation code to allow use of spaces within directories

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3880?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3880: ------------------------------------------------ Jiri Pechanec <jpechane(a)redhat.com> changed the Status of [bug 880892|https://bugzilla.redhat.com/show_bug.cgi?id=880892] from ON_QA to VERIFIED > Changes to jUDDI initialisation code to allow use of spaces within directories > ------------------------------------------------------------------------------ > > Key: JBESB-3880 > URL: https://issues.jboss.org/browse/JBESB-3880 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Registry and Repository > Affects Versions: 4.11 CP2 > Reporter: Kevin Conner > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > Attachments: juddi.patch > > > The jUDDI code requires a correctly encoded URI to be passed but we are not escaping them correctly. The attached changes need to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3880) Changes to jUDDI initialisation code to allow use of spaces within directories

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3880?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3880: ------------------------------------------------ Jiri Pechanec <jpechane(a)redhat.com> made a comment on [bug 880892|https://bugzilla.redhat.com/show_bug.cgi?id=880892] Verified in ER3 > Changes to jUDDI initialisation code to allow use of spaces within directories > ------------------------------------------------------------------------------ > > Key: JBESB-3880 > URL: https://issues.jboss.org/browse/JBESB-3880 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Registry and Repository > Affects Versions: 4.11 CP2 > Reporter: Kevin Conner > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > Attachments: juddi.patch > > > The jUDDI code requires a correctly encoded URI to be passed but we are not escaping them correctly. The attached changes need to be made. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3893) PropertySubstituter not expanding properties in notifications

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3893?page=com.atlassian.jira.plugin... ] Tom Cunningham resolved JBESB-3893. ----------------------------------- Resolution: Done > PropertySubstituter not expanding properties in notifications > ------------------------------------------------------------- > > Key: JBESB-3893 > URL: https://issues.jboss.org/browse/JBESB-3893 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.11 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > > In ESB notifications, you're supposed to be able to use property names which will get expanded at runtime to the values of those properties, but this isn't working correctly and the property names are used literally. > The following variations were tested: > <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}.xml" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID.txt" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID" append="false"/> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3893) PropertySubstituter not expanding properties in notifications

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3893?page=com.atlassian.jira.plugin... ] Tom Cunningham closed JBESB-3893. --------------------------------- > PropertySubstituter not expanding properties in notifications > ------------------------------------------------------------- > > Key: JBESB-3893 > URL: https://issues.jboss.org/browse/JBESB-3893 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.11 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > > In ESB notifications, you're supposed to be able to use property names which will get expanded at runtime to the values of those properties, but this isn't working correctly and the property names are used literally. > The following variations were tested: > <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}.xml" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID.txt" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID" append="false"/> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3893) PropertySubstituter not expanding properties in notifications

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3893: ------------------------------------- Summary: PropertySubstituter not expanding properties in notifications Key: JBESB-3893 URL: https://issues.jboss.org/browse/JBESB-3893 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.11 Reporter: Tom Cunningham Assignee: Tom Cunningham In ESB notifications, you're supposed to be able to use property names which will get expanded at runtime to the values of those properties, but this isn't working correctly and the property names are used literally. The following variations were tested: <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}.xml" append="false"/> <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}" append="false"/> <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID.txt" append="false"/> <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID" append="false"/> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3893) PropertySubstituter not expanding properties in notifications

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3893?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated JBESB-3893: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=883518 > PropertySubstituter not expanding properties in notifications > ------------------------------------------------------------- > > Key: JBESB-3893 > URL: https://issues.jboss.org/browse/JBESB-3893 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.11 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > > In ESB notifications, you're supposed to be able to use property names which will get expanded at runtime to the values of those properties, but this isn't working correctly and the property names are used literally. > The following variations were tested: > <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}.xml" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID.txt" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID" append="false"/> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3893) PropertySubstituter not expanding properties in notifications

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3893?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3893: ---------------------------------- Fix Version/s: 4.11 CP2 > PropertySubstituter not expanding properties in notifications > ------------------------------------------------------------- > > Key: JBESB-3893 > URL: https://issues.jboss.org/browse/JBESB-3893 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Rosetta > Affects Versions: 4.11 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > > In ESB notifications, you're supposed to be able to use property names which will get expanded at runtime to the values of those properties, but this isn't working correctly and the property names are used literally. > The following variations were tested: > <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}.xml" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/{header.call.MessageID}" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID.txt" append="false"/> > <file URI="/Users/dboeren/data/ftpinterface/header.call.MessageID" append="false"/> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues January 2013