I would rather not have knowledge of 3rd party app server deployment
descriptors in the core JBoss code as it would only complicate understanding
of how the jboss.xml and standardjboss.xml descriptor are used. Its a fine
idea but it could be implemented via a utility that transformed the app server
specific jar into a jar with a jboss.xml descriptor.
----- Original Message -----
From: "Rob Castaneda" <[EMAIL PROTECTED]>
To: "Jboss-Dev" <[EMAIL PROTECTED]>
Sent: Sunday, April 01, 2001 6:14 PM
Subject: [JBoss-dev] Support for WebLogic and other vendor jars
> Hi,
>
> During another long boring flight, I made some changes to the
> XMLFileLoader and metadata classes to support weblogic jar files. The idea
> is to have jboss be able to run WebLogic ejb-jars untouched. So far I have
> the following in mind:
>
> Load jar file
> Load Default values from standardjboss.xml
> ++ Override standard defaults with weblogic-ejb-jar IF it exists
> Load jboss.xml, overriding all.
>
>
> This is one option, although could be confusing if the user has some
> properties set in jboss.xml and some in weblogic-ejb-jar.xml , the other
> option is to have WebLogic Compatibility flag somewhere so that jboss can be
> put into this mode explicitly. If so can someone suggest the best place to
> put it?
>
> Supporting this is good in 2 ways: It helps those developing on JBoss deploy
> on WLS, and those deploying on WLS move to JBoss... win win.
>
> thoughts anyone? If this works well the next step would be to refactor the
> loader to make it easier to "plug in" support for other vendor jar files.
>
>
> regards,
>
> -Rob
>
> --
> Robert Castaneda
> [EMAIL PROTECTED]
> http://www.customware.com/jboss
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
