[
https://jira.jboss.org/jira/browse/JBAS-6758?page=com.atlassian.jira.plug...
]
Ian Springer commented on JBAS-6758:
------------------------------------
Looks like when writing the xml file out, it needs to either:
1) if there's any slashes in the JNID name, just use the portion after the rightmost
slash as the filename root, e.g. deploy/ejb_Deployment_whitebox-tx.rar-ds.xml. This seems
less than ideal because you could have multiple JNDI names that map to the same filename.
or
2) replace the slash in the JNDI name (and other invalid filename characters) with valid
filename characters, e.g.: deploy/eis_ejb_Deployment_whitebox-tx.rar-ds.xml
or
3) whenever slashes are encountered, translate them into separate path components, i.e.
create a dir named deploy/eis/, then write a file named
ejb_Deployment_whitebox-tx.rar-ds.xml into that dir.
AS 5 Plugin: Entering Global JNDI name for new ConnectionFactory
results in FileNotFoundException
--------------------------------------------------------------------------------------------------
Key: JBAS-6758
URL:
https://jira.jboss.org/jira/browse/JBAS-6758
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Shelly McGowan
Assignee: Emanuel Muckenhuber
Fix For: JBossAS-5.1.0.CR1
When entering a Global JNDI name using
eis/ejb_Deployment, an attempt to create the new resource results in the following
Exception. Using ejb_Deployment only is successful.
Failed to add Resource (see app server log for additional details):
java.lang.RuntimeException:Failed to process template. ->
java.lang.RuntimeException:java.io.FileNotFoundException:
/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/all/deploy/eis/ejb_Deployment-ds.xml
(No such file or directory) ->
java.io.FileNotFoundException:/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/all/deploy/eis/ejb_Deployment-ds.xml
(No such file or directory)
Caused by: java.lang.RuntimeException: java.io.FileNotFoundException:
/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/all/deploy/eis/ejb_Deployment_whitebox-tx.rar-ds.xml
(No such file or directory)
at
org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.transferDeployment(StreamingDeploymentTarget.java:287)
at
org.jboss.profileservice.management.upload.remoting.StreamingDeploymentTarget.distribute(StreamingDeploymentTarget.java:107)
at
org.jboss.profileservice.management.upload.DeploymentProgressImpl.distribute(DeploymentProgressImpl.java:177)
at
org.jboss.profileservice.management.upload.DeploymentProgressImpl.run(DeploymentProgressImpl.java:82)
at
org.jboss.profileservice.management.AbstractTemplateCreator.distribute(AbstractTemplateCreator.java:158)
at
org.jboss.profileservice.management.AbstractTemplateCreator.applyTemplate(AbstractTemplateCreator.java:99)
at
org.jboss.profileservice.management.ManagementViewImpl.applyTemplate(ManagementViewImpl.java:1005)
<snip>
Caused by: java.io.FileNotFoundException:
/TEST/Branch_5_x/build/output/jboss-5.1.0.CR1/server/all/deploy/eis/ejb_Deployment_whitebox-tx.rar-ds.xml
(No such file or directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
at
org.jboss.system.server.profileservice.repository.BasicDeploymentRepository.addDeploymentContent(BasicDeploymentRepository.java:147)
--
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