Re: [uportal-dev] context file in uP3

[Eric Dalquist]

Did you try just making the change in uportal-war/src/main/webapp/META-INF/context.xml ?

-Eric


Tuyhang Ly wrote:

If I understand Tomcat config files you should be able to change path="/portal" to get the change you want. uPortal would still get deployed as uPortal.war but it would get mapped in Tomcat as /portal.

In uportal-ear/pom.xml:

<finalName>portal</finalName>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-ear-plugin</artifactId>
                <version>${maven-ear-plugin.version}</version>
                <configuration>
                    <modules>
                        <webModule>
                            <groupId>org.jasig.portal</groupId>
                            <artifactId>uportal-war</artifactId>
                            <bundleFileName>portal.war</bundleFileName>
                            <contextRoot>/portal</contextRoot>
                        </webModule>
                         ...

In uportal-war/pom.xml:

    <build>
        <finalName>portal</finalName>
        <filters>
            <filter>${basedir}/../build.properties</filter>
        </filters>



Eric Dalquist wrote:

Actually, I had to change both uportal-ear/pom.xml and uportal-war/pom.xml for both methods to work correctly. Maybe we should introduce a common variable for this one.

You should be able to change the context path in the context.xml file so it is /portal regardless of what the .WAR is named. I haven't completely tested this functionality out with the new build though so if that doesn't work for you we may have to look at other options. Part of the issue is there are two ways to deploy the uPortal WAR now. 'ant deploy-war' deploys the Maven generated WAR directly and 'ant deploy-ear' deploys the WAR from the packaged EAR. We have to make sure anything that changes the final name of the .war file is consistent for both methods.

-Eric

Tuyhang Ly wrote:

                <configuration>
                    <modules>
                        <webModule>
                            <groupId>org.jasig.portal</groupId>
                            <artifactId>uportal-war</artifactId>
                            <bundleFileName>uPortal.war</bundleFileName>
                            <contextRoot>/portal</contextRoot>
                        </webModule>


Tuy.

Eric Dalquist wrote:

Thanks Eric! If I wanted to change the context path from /uPortal to /portal, I only have to change uportal-ear/pom.xml as below: Is this correct?

As of Tomcat 5.5 (maybe 5.0 actually) Tomcat support specifying the context specific config file in $TOMCAT_HOME/webapps/uPortal/META-INF/context.xml The format of the file internally is the same but this reduces the information the uPortal deployer needs about the destination Tomcat instance.

-Eric

Tuyhang Ly wrote:

Hi,



Thanks,
Tuy.

I've updated my environment from up3 trunk and noticed that the context file uPortal.xml is no longer being deployed to $TOMCAT_HOME/conf/Catalina/localhost with either "ant deploy-ear" or "ant initportal". Am I missing something here?

--
You are currently subscribed to uportal-dev@lists.ja-sig.org as: [EMAIL 
PROTECTED]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

--
You are currently subscribed to uportal-dev@lists.ja-sig.org as: [EMAIL 
PROTECTED]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/uportal-dev

smime.p7s
Description: S/MIME Cryptographic Signature