[jira] [Commented] (TAP5-2351) Missing Bootstrap CSS Source Map
[ https://issues.apache.org/jira/browse/TAP5-2351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047547#comment-14047547 ] Thilo Tanner commented on TAP5-2351: I suggest to find a solution for TAP5-2185 first (keep this issue in mind). Rewriting the URL smells a little bit like a workaround. Let me know, if I can help with something. Missing Bootstrap CSS Source Map Key: TAP5-2351 URL: https://issues.apache.org/jira/browse/TAP5-2351 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.4 Reporter: Thilo Tanner Assignee: Jochen Kemnade Priority: Minor Labels: bootstrap The source map file (boostrap.css.map) for bootstrap.css is missing in the core stack. It could either be shipped with Tapestry or the reference at the end of bootstrap.css could be removed: /*# sourceMappingURL=bootstrap.css.map */ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TAP5-2351) Missing Bootstrap CSS Source Map
Thilo Tanner created TAP5-2351: -- Summary: Missing Bootstrap CSS Source Map Key: TAP5-2351 URL: https://issues.apache.org/jira/browse/TAP5-2351 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.4 Reporter: Thilo Tanner Priority: Minor The source map file (boostrap.css.map) for bootstrap.css is missing in the core stack. It could either be shipped with Tapestry or the reference at the end of bootstrap.css could be removed: /*# sourceMappingURL=bootstrap.css.map */ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (TAP5-2118) Bug in ComponentClassResolverImpl
Thilo Tanner created TAP5-2118: -- Summary: Bug in ComponentClassResolverImpl Key: TAP5-2118 URL: https://issues.apache.org/jira/browse/TAP5-2118 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.3.6 Reporter: Thilo Tanner There is a small bug in ComponentClassResolverImpl in the method toLogicalName. Consider the following page: pages.export.exports.ExportsIndex This page will be mapped to: export/exports/sIndex instead of export/exports It seems that stripTerm is invoked with export instead of exports. I can contribute a patch if you like. Please let me know. Thanks and kind regards, Thilo -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (TAP5-628) Parameter namespacePrefix was null when deploying in Glassfish
[ https://issues.apache.org/jira/browse/TAP5-628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12698733#action_12698733 ] Thilo Tanner commented on TAP5-628: --- Thanks a lot for your research! Btw. Tapestry is a great framework! Meanwhile we get Glassfish to work by copying the stax libs to the lib/ext directory. Reference: http://mail-archives.apache.org/mod_mbox/tapestry-users/200903.mbox/%3c1238516597597-2563985.p...@n2.nabble.com%3e Parameter namespacePrefix was null when deploying in Glassfish -- Key: TAP5-628 URL: https://issues.apache.org/jira/browse/TAP5-628 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.1.0.0, 5.1.0.1, 5.1.0.2 Environment: Ubuntu 8.10 / Mac OS X 10.5.6, Glassfish V2.1 and V3 / Jetty 6 Reporter: Thilo Tanner Assignee: Howard M. Lewis Ship Attachments: t5example.zip T5 throws java.lang.IllegalArgumentException: Parameter namespacePrefix was null when deploying application on Glassfish (v2.1 and v3). With Jetty everything works fine. It seems that Glassfish handles namespaces a bit different than other containers do. The error *only* occurs when a Doctype is set. It seems that the XML parser of glassfish sets the variable namespacePrefix in the method defineNamespace (class: org.apache.tapestry5.dom.Element) to null. When I change the value to (empty string) by hand (in the debugger), everything works fine. Would it be possible to change the behaviour that a null namespacePrefix will be accepted? When no Doctype is defined, the method defineNamespace is not called. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TAP5-628) Parameter namespacePrefix was null.
Parameter namespacePrefix was null. --- Key: TAP5-628 URL: https://issues.apache.org/jira/browse/TAP5-628 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.1.0.2, 5.1.0.1, 5.1.0.0 Reporter: Thilo Tanner T5 throws java.lang.IllegalArgumentException: Parameter namespacePrefix was null when deploying application on Glassfish (v2.1 and v3). With Jetty everything works fine. It seems that Glassfish handles namespaces a bit different than other container do. The error only occurs when a Doctype is set -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-628) Parameter namespacePrefix was null.
[ https://issues.apache.org/jira/browse/TAP5-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thilo Tanner updated TAP5-628: -- Attachment: t5example.zip A little test project which shows the error: There are two pages: Working and NotWorking. The error only occurs on the NotWorking page. Parameter namespacePrefix was null. --- Key: TAP5-628 URL: https://issues.apache.org/jira/browse/TAP5-628 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.1.0.0, 5.1.0.1, 5.1.0.2 Reporter: Thilo Tanner Attachments: t5example.zip T5 throws java.lang.IllegalArgumentException: Parameter namespacePrefix was null when deploying application on Glassfish (v2.1 and v3). With Jetty everything works fine. It seems that Glassfish handles namespaces a bit different than other container do. The error only occurs when a Doctype is set -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TAP5-628) Parameter namespacePrefix was null.
[ https://issues.apache.org/jira/browse/TAP5-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thilo Tanner updated TAP5-628: -- Description: T5 throws java.lang.IllegalArgumentException: Parameter namespacePrefix was null when deploying application on Glassfish (v2.1 and v3). With Jetty everything works fine. It seems that Glassfish handles namespaces a bit different than other containers do. The error *only* occurs when a Doctype is set. It seems that the XML parser of glassfish sets the variable namespacePrefix in the method defineNamespace (class: org.apache.tapestry5.dom.Element) to null. When I change the value to (empty string) by hand (in the debugger), everything works fine. Would it be possible to change the behaviour that a null namespacePrefix will be accepted? When no Doctype is defined, the method defineNamespace is not called. was: T5 throws java.lang.IllegalArgumentException: Parameter namespacePrefix was null when deploying application on Glassfish (v2.1 and v3). With Jetty everything works fine. It seems that Glassfish handles namespaces a bit different than other containers do. The error *only* occurs when a Doctype is set. It seems that the XML parser of glassfish sets the variable namespacePrefix in the method defineNamespace (class: org.apache.tapestry5.dom.Element) to null. When I change the value to (empty string) by hand, everything works fine. Would it be possible to change the behaviour that a null namespacePrefix will be accepted? When no Doctype is defined, the method defineNamespace is not called. Parameter namespacePrefix was null. --- Key: TAP5-628 URL: https://issues.apache.org/jira/browse/TAP5-628 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.1.0.0, 5.1.0.1, 5.1.0.2 Environment: Ubuntu 8.10 / Mac OS X 10.5.6, Glassfish V2.1 and V3 / Jetty 6 Reporter: Thilo Tanner Attachments: t5example.zip T5 throws java.lang.IllegalArgumentException: Parameter namespacePrefix was null when deploying application on Glassfish (v2.1 and v3). With Jetty everything works fine. It seems that Glassfish handles namespaces a bit different than other containers do. The error *only* occurs when a Doctype is set. It seems that the XML parser of glassfish sets the variable namespacePrefix in the method defineNamespace (class: org.apache.tapestry5.dom.Element) to null. When I change the value to (empty string) by hand (in the debugger), everything works fine. Would it be possible to change the behaviour that a null namespacePrefix will be accepted? When no Doctype is defined, the method defineNamespace is not called. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TAP5-551) Glassfish V2.1 is unable to load correct woodstox stax implemention
Glassfish V2.1 is unable to load correct woodstox stax implemention --- Key: TAP5-551 URL: https://issues.apache.org/jira/browse/TAP5-551 Project: Tapestry 5 Issue Type: Bug Components: tapestry-core Affects Versions: 5.1.0.0 Reporter: Thilo Tanner Glassfish throws the following error while loading a template file: [ERROR] InternalModule.TemplateParser Construction of service TemplateParser failed Error invoking constructor org.apache.tapestry5.internal.services.TemplateParserImpl(Map, boolean) (at TemplateParserImpl.java:50) via org.apache.tapestry5.internal.services.InternalModule.bind(ServiceBinder) (at InternalModule.java:65) (for service 'TemplateParser'): com.sun.xml.stream.ZephyrParserFactory cannot be cast to org.codehaus.stax2.XMLInputFactory2 ... Workaround: Add the system property below to Application Server JVM Settings JVM Options and restart Glassfish -Djavax.xml.stream.XMLInputFactory=com.ctc.wstx.stax.WstxInputFactory -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
