Hi
I tried to run the struts-shale-usecases webapp from the nightly
build(16th), but I get a NullpointerException during startup.
I am running on Tomcat 5.0.30 and have tried both JDK 1.4.2_09 and
1.5.0_04.
javax.servlet.ServletException: Error at line 41 char 56: null
at
org.apache.shale.faces.ShaleApplicationFilter.init(ShaleApplicationFilte
r.java:334)
at
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFi
lterConfig.java:225)
...
----- Root Cause -----
java.lang.NullPointerException
at
org.apache.commons.digester.Digester.createSAXException(Digester.java:29
19)
at
org.apache.commons.digester.Digester.createSAXException(Digester.java:29
45)
at
org.apache.commons.digester.Digester.startElement(Digester.java:1364)
at
org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at
org.apache.xerces.impl.dtd.XMLDTDValidator.startElement(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(U
nknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDis
patcher.dispatch(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unkno
wn Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
Source)
at
org.apache.commons.digester.Digester.parse(Digester.java:1647)
at
org.apache.shale.dialog.config.ConfigurationParser.parse(ConfigurationPa
rser.java:160)
at
org.apache.shale.dialog.config.ConfigurationInit.execute(ConfigurationIn
it.java:101)
at
org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:166)
at
org.apache.shale.faces.ShaleApplicationFilter.init(ShaleApplicationFilte
r.java:331)
....
Anybody had the same problem ?
Hermod
-----Opprinnelig melding-----
Fra: Craig McClanahan [mailto:[EMAIL PROTECTED]
Sendt: 16. september 2005 08:59
Til: Struts Users Mailing List
Emne: Re: [Shale]managed beans in request vs. session scope and how to
clean up
On 9/15/05, Holshausen, Ron <[EMAIL PROTECTED]> wrote:
>
> Hi Geeta,
>
> Just to let you know that one of the changes that was made to the JSF
> spec was to integrate the JSTL and JSF, so you could use c:forEach
with
> JSF UI components. So using JSTL is still ok, I do. And I think it
will
> be around for a while.
Ron's comments with respect to JSF 1.2 and JSTL interoperability are
correct
... but they only address part of the overall issue. If all you care
about
is *rendering* output based on an iteration over a collection of model
tier
objects, the JSF 1.2 integration strategy will work fine. If, on the
other
hand, you want to have *input* fields inside your <c:forEach> tag,
you're
going to run into more problems. The right answer there is to use an
outer
"grouping" component (such as, but not limited to, <h:dataTable>) that
deals
with the iteration issues during the postback processing phases (Apply
Request Values through Process Validations) as well as during rendering.
Solutions based on JSTL *only* work during rendering, because the JSP
page
itself is *not* involved in actually performing a postback.
Or, if you want a shorter version of the answer, depending on
<c:forEach> is
still going to limit what you can actually do inside the iterations,
even in
a JSF 1.2 world. The right answer is smarter components that do
iterations
for you, not forcing the page developer to manually code iteration
loops.
Craig
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
This email with attachments is solely for the use of the individual or
entity to whom it is addressed. Please also be aware that the DnB NOR Group
cannot accept any payment orders or other legally binding correspondence with
customers as a part of an email.
This email message has been virus checked by the virus programs used
in the DnB NOR Group.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
