[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2750) loadImplicit error messages
by toni (JIRA)
loadImplicit error messages
---------------------------
Key: JBSEAM-2750
URL: http://jira.jboss.com/jira/browse/JBSEAM-2750
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.1.GA
Environment: JBoss 4.2.2 GA, Linux Sarge, Sun JDK 1.5_14
Reporter: toni
Every few minutes the following log entries show up in the log file of my application:
2008-03-17 23:59:41,251 ERROR [STDERR] Mar 17, 2008 11:59:41 PM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/jboss-4.2.2.GA/server/default/deploy/calc.ear/calc.war/WEB-INF/lib/jboss-seam-ui.jar!/META-INF/s.taglib.xml
2008-03-17 23:59:41,275 ERROR [STDERR] Mar 17, 2008 11:59:41 PM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/jboss-4.2.2.GA/server/default/deploy/calc.ear/calc.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-core.taglib.xml
2008-03-17 23:59:41,280 ERROR [STDERR] Mar 17, 2008 11:59:41 PM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/jboss-4.2.2.GA/server/default/deploy/calc.ear/calc.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-html.taglib.xml
2008-03-17 23:59:41,285 ERROR [STDERR] Mar 17, 2008 11:59:41 PM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/jboss-4.2.2.GA/server/default/deploy/calc.ear/calc.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jsf-ui.taglib.xml
2008-03-17 23:59:41,290 ERROR [STDERR] Mar 17, 2008 11:59:41 PM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/jboss-4.2.2.GA/server/default/deploy/calc.ear/calc.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-core.taglib.xml
2008-03-17 23:59:41,302 ERROR [STDERR] Mar 17, 2008 11:59:41 PM com.sun.facelets.compiler.TagLibraryConfig loadImplicit
INFO: Added Library from: jar:file:/opt/jboss-4.2.2.GA/server/default/deploy/calc.ear/calc.war/WEB-INF/lib/jsf-facelets.jar!/META-INF/jstl-fn.taglib.xml
For me this is a rather a serious problem even so it's only cosmetic, because our application logfile reports important errors, which get lost in the huge amount of these loadImplicit messages. As an application developer you really want to be able read your application log file, which those messages make it kind of hard.
I have read that this is actually a facelets problem, however it would be great if you could provide a workaround/patch for it, because it's highly annoying. This seems to be the origin of the problem:
https://facelets.dev.java.net/issues/show_bug.cgi?id=298
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2749) fragment attribute in pages.xml
by Martin Sznapka (JIRA)
fragment attribute in pages.xml
-------------------------------
Key: JBSEAM-2749
URL: http://jira.jboss.com/jira/browse/JBSEAM-2749
Project: JBoss Seam
Issue Type: Feature Request
Affects Versions: 2.1.0.A1
Reporter: Martin Sznapka
Priority: Minor
What about to have fragment identifier in pages.xml, I can imagine something like smart help page which gives you the right chapter according to page where you are:
<page view-id="/*">
<rule if-outcome="help">
<redirect view-id="/help.xhtml"/>
</rule>
</page>
<page view-id="/applicationOne/*">
<rule if-outcome="help">
<redirect view-id="/help.xhtml" fragment="chapOne"/>
</rule>
</page>
<page view-id="/applicationTwo/*">
<rule if-outcome="help">
<redirect view-id="/help.xhtml" fragment="chapTwo"/>
</rule>
</page>
So the result link in the second application will be like:
/myApp/help.xhtml#chapTwo
It will be much easier than dynamically generate s:link's fragment attribute for each xhtml page.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years