Hi Jim, I think how to fix the deployment problems might be described in one of the two features I actually documented.
http://cwiki.apache.org/GMOxDOC21/configuring-run-as-and-default-subjects-and-principal-role-mapping.html I'm attaching an updated plan with what look like plausible changes. I haven't been able to figure out what you are trying to deploy with this plan from the 4.4.1 downloads, so I'll wait for more input from you. I think the Roller plugin provides a good model for what you might end up with in terms of a reproducible plugin/server build environment. svn co https://svn.apache.org/repos/asf/geronimo/plugins/roller/trunk This shows how to construct switchable database plugins (derby and mysql) and constructs roller plugins for jetty and tomcat, and shows how to assemble servers around these plugins. The archetypes I've started should help a lot with setting up projects like this. thanks david jencks ----- Original Message ---- From: Jim Foster <[EMAIL PROTECTED]> To: user@geronimo.apache.org Sent: Thursday, February 21, 2008 4:16:58 PM Subject: Re: Geronimo v2.1 Plan Creator => Deploy Liferay 4.4.1 djencks wrote: > > Jim, > > Is liferay 4.4.1 available on a maven repo? If not where can I find it? > Is liferay normally built with maven? I snagged the plan off an earlier > mail... > > By far the easiest way to create a g 2.1 plugin is with maven. I'm > starting a maven archetype to make it easy to set up a maven project to > generate a plugin. This seems like a good test case. > > thanks > david jencks > > Hi David, I think this is an excellent suggestion! When one thinks of application server usage, a Portal environment is usually hovering near the top of use-case scenarios, followed closely by CMS, so if we were to take Liferay as a first use-case and make it a model, we would be solving many problems at once: your archetype development, a use-case model suitable for public consumption, and solving my particular development situation. I need to step away right now, but I will follow-up again to this thread and provide you with all the information you require so that we can work together on getting this accomplished. Thanks! Jim -- View this message in context: http://www.nabble.com/Re%3A-Geronimo-v2.1-Plan-Creator-%3D%3E-Deploy-Liferay-4.4.1-tp15623755s134p15624334.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
<?xml version="1.0"?> <web-app xmlns="http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1";> <environment> <moduleId> <groupId>liferay</groupId> <artifactId>liferay-portal-tomcat</artifactId> <version>4.4.1</version> <type>car</type> </moduleId> <dependencies> <dependency> <groupId>org.apache.geronimo.configs</groupId> <artifactId>j2ee-security</artifactId> <type>car</type> </dependency> <dependency> <groupId>org.apache.geronimo.configs</groupId> <artifactId>j2ee-server</artifactId> <type>car</type> </dependency> <dependency> <groupId>org.apache.geronimo.configs</groupId> <artifactId>javamail</artifactId> <type>car</type> </dependency> <dependency> <groupId>org.apache.geronimo.configs</groupId> <artifactId>sharedlib</artifactId> <type>car</type> </dependency> <dependency> <groupId>org.apache.geronimo.modules</groupId> <artifactId>geronimo-mail</artifactId> <type>jar</type> <import>classes</import> </dependency> <dependency> <groupId>liferay</groupId> <artifactId>liferay-pool</artifactId> <type>car</type> </dependency> <!--<dependency> <groupId>liferay</groupId> <artifactId>portal-kernel</artifactId> <type>jar</type> <import>classes</import> </dependency> <dependency> <groupId>liferay</groupId> <artifactId>portal-service</artifactId> <type>jar</type> <import>classes</import> </dependency> <dependency> <groupId>portlet-api</groupId> <artifactId>portlet-api</artifactId> <type>jar</type> <import>classes</import> </dependency>--> </dependencies> <inverse-classloading /> </environment> <context-root>/</context-root> <security-realm-name>PortalRealm</security-realm-name> <security use-context-handler="false" xmlns="http://geronimo.apache.org/xml/ns/security-2.0";> <default-subject> <realm>PortalRealm</realm> <id>default</id> </default-subject> <role-mappings> <role role-name="users"> <principal class="com.liferay.portal.security.jaas.PortalRole" name="users" /> </role> </role-mappings> </security> <!-- if you name the pool jdbc/LiferayPool you can omit this mapping --> <resource-ref> <ref-name>jdbc/LiferayPool</ref-name> <resource-link>LiferayPool</resource-link> </resource-ref> <!-- unless you have specific mail configuration I'd suggest you use the built in mail/MailSession in the javamail plugin so you can omit this mapping --> <resource-ref> <ref-name>mail/MailSession</ref-name> <resource-link>LiferayMailSession</resource-link> </resource-ref> <gbean name="CredentialStore" class="org.apache.geronimo.security.credentialstore.SimpleCredentialStoreImpl"> <xml-attribute name="credentialStore"> <credential-store xmlns="http://geronimo.apache.org/xml/ns/credentialstore-1.0";> <realm name="PortalRealm"> <subject> <id>default</id> <!-- you will have so set up the backing store appropriately --> <credential> <type>org.apache.geronimo.security.credentialstore.NameCallbackHandler</type> <value>anonymous</value> </credential> <credential> <type>org.apache.geronimo.security.credentialstore.PasswordCallbackHandler</type> <value>anonymous</value> </credential> </subject> </realm> </credential-store> </xml-attribute> </gbean> <gbean name="LiferayMailSession" class="org.apache.geronimo.mail.MailGBean"> <attribute name="transportProtocol">smtp</attribute> <attribute name="host">localhost</attribute> </gbean> <gbean name="PortalRealm" class="org.apache.geronimo.security.realm.GenericSecurityRealm"> <attribute name="realmName">PortalRealm</attribute> <reference name="ServerInfo"> <name>ServerInfo</name> </reference> <!--<reference name="LoginService"> <name>JaasLoginService</name> </reference>--> <xml-reference name="LoginModuleConfiguration"> <log:login-config xmlns:log="http://geronimo.apache.org/xml/ns/loginconfig-2.0";> <log:login-module control-flag="REQUIRED" wrap-principals="false"> <log:login-domain-name>PortalRealm</log:login-domain-name> <log:login-module-class>com.liferay.portal.security.jaas.ext.tomcat.PortalLoginModule</log:login-module-class> </log:login-module> </log:login-config> </xml-reference> </gbean> </web-app>
