Closed Tomas-Kraus closed 13 years ago
@glassfishrobot Commented Reported by bvingerh
@glassfishrobot Commented oleksiys said: 1.1.x branch
Project: fi Repository: svn Revision: 910 Author: oleksiys Date: 2011-08-08 09:15:52 UTC Link:
"Missing ResourceBundle.properties"
1.2.x branch Project: fi Repository: svn Revision: 908 Author: oleksiys Date: 2011-08-08 09:15:08 UTC Link:
"Missing ResourceBundle.properties"
@glassfishrobot Commented oleksiys said: FYI, the issue is fixed on trunk and 1.1.x branch. We'll make a release once issue #45 is fixed.
@glassfishrobot Commented oleksiys said: FYI:
1.2.11 have been released http://blogs.oracle.com/oleksiys/entry/fastinfoset_1_1_9_and
@glassfishrobot Commented This issue was imported from java.net JIRA FI-44
@glassfishrobot Commented Marked as fixed on Monday, August 8th 2011, 2:25:09 am
We just moved from FI 1.2.5 to 1.2.10 and our test frameworks fail with MissingResourceExceptions in the CommonResourceBundle constructors.
Stacktrace: java.util.MissingResourceException: Can't find bundle for base name com.sun.xml.fastinfoset.resources.ResourceBundle, locale en_US at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.j ava:1427) at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1250) at java.util.ResourceBundle.getBundle(ResourceBundle.java:705) at com.sun.xml.fastinfoset.CommonResourceBundle.(CommonResourceBundl
e.java:34)
at
com.sun.xml.fastinfoset.CommonResourceBundle.getInstance(CommonResource
Bundle.java:45)
at
com.sun.xml.fastinfoset.sax.SAXDocumentParser.setFeature(SAXDocumentPar
ser.java:209)
at net.sf.saxon.event.Sender.sendSAXSource(Sender.java:329)
...
In this case Saxon tries to set the 'http://xml.org/sax/features/validation' feature to false. As this feature is not supported by FI, an (expected) exception is attempted to be thrown. However the exception message is not found.
It seems that com.sun.xml.fastinfoset.resources.ResourceBundle.properties file (containing all exception messages) has been removed from the binary distribution of FI. I assume this change was not performed intentionally, but rather accidentally (maybe in the move to Maven?).
We consider this a critical bug as both we and other third-party libraries we use rely on proper exception handling for detecting anomalies and FI is at this moment unable to generate expectable exceptions, instead throwing the same RuntimeException in every case.
As a fix to this problem does not involve actual coding work, but only a repackaging, would it be possible to publish a stable release version very soon?
Affected Versions
[1.2.10]