[jbossts-issues] [JBoss JIRA] (JBTM-2236) Remove / from ConfigurationInfo

[Mark Little (JIRA)]

    [ https://issues.jboss.org/browse/JBTM-2236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992372#comment-12992372 ] 

Mark Little commented on JBTM-2236:
-----------------------------------

Stick with removing the /

Then after basePath is first created, try this:

if (basePath.endsWith("/"))
    basePath = basePath.substring(0, basePath.length()-1);

> Remove / from ConfigurationInfo
> -------------------------------
>
>                 Key: JBTM-2236
>                 URL: https://issues.jboss.org/browse/JBTM-2236
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Common
>    Affects Versions: 5.0.2
>            Reporter: Mark Little
>            Assignee: Tom Jenkinson
>
> I've been working on compiling Java using the Avian project (http://oss.readytalk.com/avian/) and have eventually had success in running some of our hammer tests. However, there was a blocker which was to do with the way in which we locate the property file within the jar using the manifest. We can argue as to whether the issue resides within Avian or the way in which we do things, but the solution was to simply remove the / from:
> int suffixLength = ("/"+ConfigurationInfo.class.getCanonicalName()+".class").length();
> Rebuilding and rerunning the tests made everything work.
> I don't want to check in this change until I am sure that it is right, so would appreciate someone looking at it and at least running all of the QE tests to be sure nothing else breaks.
> I've included a reference to the Avian forum article where I discussed this with their team.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)