>
> I agree with both of you that it should NOT be part of the core code,
> thats why I suggested to refactor that section to support various different
> types via a plugin, once it was working.
>
I must have missed that.
> An external utility is an extra step that a developer needs to go through to
> write beans, and results in two xml files..... It is much nicer just to have
> one, this follows the "drop it in and run it" philosophy of JBoss.
I agree that a utility is an extra step, but I think it would be a price
that a developer would be willing to pay in order to deploy on another
server.
I just saw a comment posted by a WL user that he doubted whether _any_ tool
would be able to convert the WL-specific ejb-jar descriptor.
You must think it can be done.
> I was thinking along the lines of having this behavior configurable in an
> MBean, and off by default. If it was on then the server would also read in
> the weblogic-ejb-jar.xml
If you think it can be done and eliminate the need for a utility in the
process, I guess it sounds good to me.
Anything that allows JBoss to deploy WL apps sounds good to me.
Scott?
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
