1 of 1 people found this helpful
Have you tried asking the same question on the Jetty forums? If a Jetty expert can point out something we need to change in our code we are more than willing to do so.
Thank you for the response.
I tried to debug the issue and the problem was inside CSSOMParser.parseStyleSheet function.
Although it parses valid and existing CSS resource the line below gives null.
Object o = handler.getRoot();
The difference between embedded Jetty(or maybe Jetty) and Tomcat is the following:
1) Jetty returns resource as FileInputStream.
2) Tomcat returns resource as ByteArrayInputStream.
I tried to upgrade to CSSParser 0.9.13(because currently used version 0.9.5 is way old) and it resolved one issue but
still CSSParser crashes internally.
Sounds like a bug. Can you file a jira with a simple (preferably maven-based) project we can use to reproduce?