Trying to summarize all steps thus far. Please let me know if I am
missing anything
1. in setDomainEnv.sh
JAVA_PROPERTIES="-Dplatform.home=${WL_HOME} -Dwls.home=${WLS_HOME}
-Dweblogic.home=${WLS_HOME}
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
"
export JAVA_PROPERTIES
2. remove xml-apis .jar from jetspeed/WEB-INF/lib
3. setting logging location in WEB-INF/classes/log4j.xml, otherwise it
goes to / for some reason
4. add weblogic.xml to WEB-INF of all deployed wars including
jetspeed, something like
<weblogic-web-app>
<reference-descriptor>
<resource-description>
<res-ref-name>jdbc/jetspeed</res-ref-name>
<!-- <jndi-name>JetspeedDB</jndi-name> -->
<jndi-name>jdbc/jetspeed</jndi-name>
</resource-description>
</reference-descriptor>
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
<show-archived-real-path-enabled>true</show-archived-real-path-enabled>
</container-descriptor>
</weblogic-web-app>
5. setup JNDI JDBC resource in weblogic (note: I never got this to
work, instead I changed the WEB-INF/assembly/boot/datasource.xml to
use a DBCP data source and commented out JNDI data source)
<bean id="JetspeedDS" class="org.apache.commons.dbcp.BasicDataSource"
destroy-method="close">
<!-- <meta key="j2:cat" value="jdbcDS" /> -->
<meta key="j2:cat" value="jndiDS" />
<meta key="j2:alias" value="JetspeedDS" />
6 . remove jetspeed-layouts from the local app area WEB-INF/apps/local.
The solution requires to no longer use jetspeed-layouts war
7. copy jetspeed-layouts(version).jar into jetspeed's WEB-INF/lib directory
8. replace all PSML entries in WEB-INF/pages from "jetspeed-layouts::"
to "jetspeed::" using sed or a global replace tool
(This part is a little fragile, since if you are naming your
jetspeed app something else, then you have to rename your layout
pages)
9. copy the jetspeed-layouts portlet.xml and jetspeed-portlet.xml from
the layout-portlets war into jetspeed/WEB-INF
10. add this servlet and servlet mapping the jetspeed's web.xml
<servlet>
<description>MVC Servlet for Jetspeed Portlet Applications</description>
<display-name>Jetspeed Container</display-name>
<servlet-name>JetspeedContainer</servlet-name>
<servlet-class>
org.apache.jetspeed.container.JetspeedContainerServlet</servlet-class>
<init-param>
<param-name>contextName</param-name>
<param-value>jetspeed</param-value>
</init-param>
<load-on-startup>100</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>JetspeedContainer</servlet-name>
<url-pattern>/container/*</url-pattern>
</servlet-mapping>
Will add this to docs once it settles down and the login problem is solved
On Tue, Feb 8, 2011 at 4:28 PM, David Taylor <[email protected]> wrote:
> Had some success. Note: I have only tested with an expanded jetspeed
> directory in the weblogic upload directory, and a non-expanded
> j2-admin in the upload directory (A min distribution, 2 war files)
>
> Try these steps:
>
> 0. shutdown weblogic
> 1. remove jetspeed-layouts from the local app area WEB-INF/apps/local.
> The solution requires to no longer use jetspeed-layouts war
> 2. copy jetspeed-layouts(version).jar into jetspeed's WEB-INF/lib directory
> 3. replace all PSML entries in WEB-INF/pages from "jetspeed-layouts::"
> to "jetspeed::" using sed or a global replace tool
> 4. copy the jetspeed-layouts portlet.xml and jetspeed-portlet.xml from
> the layout-portlets war into jetspeed/WEB-INF
> 5. add this servlet and servlet mapping the jetspeed's web.xml
>
> <servlet>
> <description>MVC Servlet for Jetspeed Portlet Applications</description>
> <display-name>Jetspeed Container</display-name>
> <servlet-name>JetspeedContainer</servlet-name>
> <servlet-class>
> org.apache.jetspeed.container.JetspeedContainerServlet</servlet-class>
> <init-param>
> <param-name>contextName</param-name>
> <param-value>jetspeed</param-value>
> </init-param>
> <load-on-startup>100</load-on-startup>
> </servlet>
>
> <servlet-mapping>
> <servlet-name>JetspeedContainer</servlet-name>
> <url-pattern>/container/*</url-pattern>
> </servlet-mapping>
>
> 6. restart Weblogic
>
> The NPE went away, and portlets are now rendering for the guest user.
> Note: I tested this approach on both Tomcat and Weblogic.
> I can login with Tomcat, but not Weblogic. Tried both active
> authentication and portal filter approaches, no luck
>
--
David
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
