<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>It's Only Software &#187; How to Diagnose the Awful Websphere Portal EJPPG0003E Error &#8211; It&#8217;s Only Software</title>
	<atom:link href="http://www.mularien.com/blog/category/jsf/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mularien.com/blog</link>
	<description>Notes by Peter Mularien on Hibernate, Spring, CSS, Java, etc.</description>
	<lastBuildDate>Tue, 01 Mar 2011 11:26:31 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>How to Diagnose the Awful Websphere Portal EJPPG0003E Error</title>
		<link>http://www.mularien.com/blog/2008/05/06/how-to-diagnose-the-awful-websphere-portal-ejppg0003e-error/</link>
		<comments>http://www.mularien.com/blog/2008/05/06/how-to-diagnose-the-awful-websphere-portal-ejppg0003e-error/#comments</comments>
		<pubDate>Wed, 07 May 2008 02:09:28 +0000</pubDate>
		<dc:creator>pmularien</dc:creator>
				<category><![CDATA[development]]></category>
		<category><![CDATA[java]]></category>
		<category><![CDATA[jsf]]></category>
		<category><![CDATA[portlet]]></category>
		<category><![CDATA[websphere]]></category>

		<guid isPermaLink="false">http://www.mularien.com/blog/2008/05/06/how-to-diagnose-the-awful-websphere-portal-ejppg0003e-error/</guid>
		<description><![CDATA[If you have done Websphere Portal 5.1 development, you have probably seen this error (among many others) at some point in your development lifecycle: EJPPG0003E: ServletContext lookup for /.MyPortalApp returned the portal context. It has to be a different one. Let me tell you that this error can be caused by about a hundred different [...]]]></description>
		<wfw:commentRss>http://www.mularien.com/blog/2008/05/06/how-to-diagnose-the-awful-websphere-portal-ejppg0003e-error/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Tomcat 6.0.14 + JSTL 1.2_07 RI = *Boom* NullPointerException</title>
		<link>http://www.mularien.com/blog/2008/02/05/tomcat-6014-jstl-12_07-ri-boom-nullpointerexception/</link>
		<comments>http://www.mularien.com/blog/2008/02/05/tomcat-6014-jstl-12_07-ri-boom-nullpointerexception/#comments</comments>
		<pubDate>Wed, 06 Feb 2008 01:39:26 +0000</pubDate>
		<dc:creator>pmularien</dc:creator>
				<category><![CDATA[development]]></category>
		<category><![CDATA[eclipse]]></category>
		<category><![CDATA[java]]></category>
		<category><![CDATA[jsf]]></category>
		<category><![CDATA[jstl]]></category>
		<category><![CDATA[tomcat]]></category>

		<guid isPermaLink="false">http://www.mularien.com/blog/2008/02/05/tomcat-6014-jstl-12_07-ri-boom-nullpointerexception/</guid>
		<description><![CDATA[I guess I&#8217;ve had a busy / buggy weekend noodling around with stuff. I ran into a [known] bug in the latest JSTL/JSF 1.2 Reference Implementation on Tomcat 6.0.14. I was playing around with Spring MVC 2.5.1, and even the simplest JSP page gave me this: java.lang.NullPointerException com.sun.faces.application.WebappLifecycleListener.syncSessionScopedBeans&#40;WebappLifecycleListener.java:312&#41; com.sun.faces.application.WebappLifecycleListener.requestDestroyed&#40;WebappLifecycleListener.java:87&#41; com.sun.faces.config.ConfigureListener.requestDestroyed&#40;ConfigureListener.java:240&#41; &#91;snip&#93; This is interesting, because [...]]]></description>
		<wfw:commentRss>http://www.mularien.com/blog/2008/02/05/tomcat-6014-jstl-12_07-ri-boom-nullpointerexception/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic page generated in 0.586 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2012-02-04 14:45:18 -->

