- This topic has 1 reply, 2 voices, and was last updated 17 years, 6 months ago by
.
-
Posts
-
JSPX, there is no dedicated jspx template in the new files list, xmlns definitions are marked as errors and not parsed, however if you take the same file under a xhtml definition it works, the xhtml editor however ignores the xmlns settings ones the file ends with jspx.
The html editor picks up css definitions in external files quite nicely and integrates it into the split preview html pane, the jsp editor however does not.
The component definition files in facelets for separate facelet components are not parsed by the taglib parser, hence self written components are not integrated into the code insight in the jsp/xhtml editors.
JSPX, there is no dedicated jspx template in the new files list, xmlns definitions are marked as errors and not parsed, however if you take the same file under a xhtml definition it works, the xhtml editor however ignores the xmlns settings ones the file ends with jspx.
Known issue, should be fixed in 6.0. Sorry about the wait.
The html editor picks up css definitions in external files quite nicely and integrates it into the split preview html pane, the jsp editor however does not.
It should, I’ll file this as a bug.
The component definition files in facelets for separate facelet components are not parsed by the taglib parser, hence self written components are not integrated into the code insight in the jsp/xhtml editors.
Known issue, we hope to get it fixed soon.
Thank you for keeping us honest werpu, any other issues you run into please report.
