This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 164422 - java.io.IOException when opening Facelets 2.0 XHTML file
Summary: java.io.IOException when opening Facelets 2.0 XHTML file
Status: RESOLVED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: JSF (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@javaee
URL: http://statistics.netbeans.org/analyt...
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-04 22:40 UTC by ievans
Modified: 2010-12-21 09:21 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ievans 2009-05-04 22:40:32 UTC
A java.io.IOException is thrown when opening an XHTML file that uses the Facelets 2.0 taglib, picked up up from the
glassfishv3/glassfish/modules/jsf-impl.jar file.

See exception report 25198.

This is a blocking bug for the First Cup tutorial included with the Java EE 6 SDK.
Comment 1 ievans 2009-05-04 22:45:21 UTC
To reproduce using First Cup:

1. Check out the example source code as described here:
https://firstcup.dev.java.net/source/browse/firstcup/

2. Add GlassFish v3 as a server instance.

3. Open firstcup/example/firstcup/web/resources/components/inputDate.xhtml.

Comment 2 Petr Jiricka 2009-05-05 11:38:33 UTC
I can not reproduce this exact exception. Is it really exception report 25198? That one has JasperReports code in the
stack trace, so it looks unrelated. Can you please attach the exact exception you are getting?

I am getting a different exception when I opened the project and go to project properties - I reported this as a
separate issue 164463.
Comment 3 Marek Fukala 2009-05-05 13:41:16 UTC
>I can not reproduce this exact exception. Is it really exception report 25198? 
I think so, at least the last duplicate is the same as what you reported in issue 164463. Looks like the exception
reporter matches the issue due to the stactraces similarity incorrectly. I would recommend to close this issue and track
it in the new one.
Comment 4 Petr Jiricka 2009-07-24 17:40:03 UTC
I believe this is fixed in the current NB 6.8 builds.