asbachb commented on PR #6096: URL: https://github.com/apache/netbeans/pull/6096#issuecomment-1621245374
> Ah, so you have finally figured out what this stuff does. Too bad it's not possible to load new schemas from newer Mojarra as it requires JDK 11. Maybe they could be added locally to existing jars (just the schemas)? That would be a possibility. Another thing is that the module currently use some classes from the implementation itself. e.g. the schema is created based on a `SchemaFactory` provided by the JSF Implementation. I guess I'll abandon this PR for now as I'm currently experimenting with another solution: I try to get the JSF implementation of the JSF version which is currently used via maven. So for example if you use Jakarta EE 10 the module checks your local repository and if the JSF Reference Implementation is not present it will be downloaded from Maven Central. The module would still use the classes from the bundled JSF Implementation, but it would fetch the actual taglib descriptions from JSF reference implementation suited for the project. That basically already works. Currently the question is how to handle the legacy namespaces. Per spec they're still valid. The problem is that these namespaces - at least I'm not aware of - could not be retrieved from the JSF reference implementation jar. So the module would need to define them manually and this needs a some more refactoring to do it properly. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
