[jboss-dev] VFS3 (in AS trunk) - Non .jar file handling

[Jaikiran Pai]

FYI - This behaviour seems to have introduced deployment failures 
https://issues.jboss.org/browse/JBAS-8725

-Jaikiran

On Wednesday 10 March 2010 03:58 PM, Jaikiran Pai wrote:
> I see a new behaviour with VFS3 in JBoss AS. Earlier in AS-5/6 (with
> VFS2) and AS-4 (without any VFS), to try out some quick fixes, i used to
> rename existing jar files to end with .bak name and replace them with
> the new patched jar file. So for example, if i had a fix in
> jboss-ejb3-core.jar, i would:
>
> 1) Rename the JBOSS_HOME/common/lib/jboss-ejb3-core.jar to
> JBOSS_HOME/common/lib/jboss-ejb3-core.jar.orig.bak
> 2) Place a patched jboss-ejb3-core.jar in JBOSS_HOME/common/lib
> 3) Restart the server
>
> The server would then pickup the new patched jar file and ignore the
> .bak file. After testing the fix, i would then revert back to the
> original jar file by renaming it back to its original name.
>
> However, with the recent upgrade to VFS3 in AS trunk, i notice that even
> the .bak is used for classloading (following is the output from
> -verbose:class JVM argument):
>
> [Loaded org.jboss.ejb3.EJBContainer from
> file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/common/lib/jboss-ejb3-core.jar.orig.bak/]
>
> Looks like VFS3 picks up this non .jar suffix file for classloading. Is
> this expected? Shouldn't it be looking for only .jar files (atleast in
> this context)?
>
>
>
> regards,
> -Jaikiran
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development