Message-
From: Sachin Patel
[mailto:[EMAIL PROTECTED]
Sent: Thursday, March 09, 2006
7:02 PM
To: dev@geronimo.apache.org
Subject: Re: valid XML checking
I'm already doing this on importing applications.
Non-qualified plans can be imported, and I run the conversion to make it a
valid doc so
The code is correct as is. Even outside of tools applications are
deployed in two steps, a distribute phase and a start phase. The
only fix that that needs to be done is the conversion and beyond that
the use of an in-memory copy so that the qualified version is never
seen and only used
the deployment plan to bypass
the valid XML checking. The extra editing is are not needed if I
use the command line deployer or admin console.
The
problem is that the plugin checks the deployment plan very strictly. I have to use fully qualified elements, otherwise the
plans are not treated
the valid XML checking. The extra editing is are not needed if I use the command line deployer or admin console. The problem is that the plugin checks the deployment plan very strictly. I have to use fully qualified elements, otherwise the plans are not treated as valid xmls, and the model editor
ime trying to get the MDB sample (http://opensource2.atlassian.com/confluence/oss/display/GERONIMO/JBoss+to+Geronimo+-+EJB-MDB+Migration) deployed using the eclipse plugin. I was able to get it running eventually but I had to spend extra time in modifying the deployment plan to bypass the valid XM
+Migration) deployed using the eclipse plugin. I was able to get it running eventually but I had to spend extra time in modifying the deployment plan to bypass the valid XML checking. The extra editing is are not needed if I use the command line deployer or admin console. The problem is that
