[ http://jira.jboss.com/jira/browse/JBAS-422?page=history ]
     
Adrian Brock closed JBAS-422:
-----------------------------

    Resolution: Out of Date

> ejb-link doesn't work with exploded EJB .jar files
> --------------------------------------------------
>
>          Key: JBAS-422
>          URL: http://jira.jboss.com/jira/browse/JBAS-422
>      Project: JBoss Application Server
>         Type: Feature Request
>     Reporter: SourceForge User
>     Assignee: Scott M Stark

>
>
> SourceForge Submitter: vancan13 .
> (see [ jboss-Bugs-650929 ] ejb-link doesn't work in
> deployment)
> There is a bug when ejbjar is not a jar but a directory
> (when .ear file contains exploded EJB .jar files).
> An additional '/' must be added to the ejbjar URL.
> You can add in the method "resolveRelativeLink" of
> "EjbUtil.java" the following code:
>       DeploymentInfo targetInfo = null;
>       try
>       {
>          targetInfo = (DeploymentInfo)server.invoke(
>             MainDeployerMBean.OBJECT_NAME,
>             "getDeployment",
>             new Object[] {target},
>             new String[] {URL.class.getName()}
>             );
> ==>>
>          // if null, try with an extra '/'
>          // (happen when ejbjar is a directory)
>          if( targetInfo == null )
>          {
>            // add a '/' at the end and retry
>            target = new URL( ourPath + '/' );
>            targetInfo = (DeploymentInfo)server.invoke(
>               MainDeployerMBean.OBJECT_NAME,
>               "getDeployment",
>               new Object[] {target},
>               new String[] {URL.class.getName()}
>               );
>          }
> <<==
>       }
>       catch( Exception e )
>       {
>          log.error( "Got Exception when looking for
> DeploymentInfo: " + e );
>          return null;
>       }
> ==>>>>>>>>>>>>>>
> >Comment By: Christian Riege (lqd)
> personally i think this is out of the scope of the specs as
> the specs don't mention exploded modules inside of an .ear
> file (or any exploded content at all). however i can see
> your use-case for this.
> could you please re-file this as a separate "Feature
> Request" here on sourceforge and i'll integrate it (yeah,
> sounds like bureaucracy but i want to keep track of it
> separately from this bug).
> thanks in advance,
>   christian

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to