I've also noticed another difference between the 1.0 and 1.1 deployment plans.

Concerning the following xml:

  <security-realm-name>geronimo-properties-realm</security-realm-name>
  <security>
    <default-principal>
<principal name="anonymous" class="org.apache.geronimo.security.realm.providers.GeronimoUserPrincipal"/>
    </default-principal>
    <role-mappings>
      <role role-name="tomcat">
<principal name="admin" class="org.apache.geronimo.security.realm.providers.GeronimoGroupPrincipal"/>
      </role>
    </role-mappings>
  </security>


IIRC, for *G1.0*, certain applications required this xml in order to deploy/start properly on Jetty. It was *not* required for Tomcat.

For *G1.1*, it seems that these security settings are required for both Jetty and Tomcat. The point is that Jetty applications will migrate fine though Tomcat applications may now require these few additional lines of xml.

Perhaps the Upgrade tool should account for this case..

Thanks
-Dave-


David Jencks wrote:
Thanks for trying it out. I changed how it starts quite a bit today -- I hope it hasn't become too slow.

I also think I fixed the schema issue Dave Colasurdo found.

thanks
david jencks

On May 14, 2006, at 3:57 PM, Chris Cardona wrote:

Hi David J.,

This is very helpful! So far it worked for the simple
ejb, war, ear that I've tested. I'll let you know if I
ran into problems deploying other modules.

Dave Colasurdo,

FYI, I tried upgrading my geronimo-web.xml and it was
converted from:

<web-app xmlns="http://geronimo.apache.org/xml/ns/web";
...

To:

<web-app
xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-1.1";
...

Maybe the upgrade tool is not expecting:

<web-app
xmlns="http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.0";
...

Not sure if this is a bug or that's the expected
behavior.

Chris

--- Dave Colasurdo <[EMAIL PROTECTED]> wrote:

Thanks David!  It seems to run fine on the simple
plans that I have
tried though I do have a few quick comments and
observations..

1) Should the version in the schema name be updated
(from 1.0 -> 1.1)
for both jetty and tomcat plans? For example, the
following line is
unchanged when the tool is run..
   <web-app

xmlns="http://geronimo.apache.org/xml/ns/j2ee/web/tomcat-1.0";>

2) When using a unicode file as input (on windows
platform) the output
file isn't created in unicode format.

3) On windows platform, it seems that CR (x'0D') is
inserted on the end
of every line..  This appears as a musical note in
my editor :)

-Dave-


David Jencks wrote:
I put the upgrade jar at



http://people.apache.org/~djencks/geronimo-upgrade-1.1-SNAPSHOT.jar

It would be very helpful to find out to what
extent this works in real
life.

It's supposed to include all the classes it needs
(that's why its so big)

usage:

java -jar geronimo-upgrade-1.1-SNAPSHOT.jar <path
to source plan> [<path
to target plan>]

if you leave out the target, you'll get output in
the same directory as
the source.

thanks
david jencks






__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com



Reply via email to