sagt einem JDiskReport (z.B. per Java Webstart) recht schön zum Durchklicken:
Artikel getaggt mit Java
It’s either trivial or harder than it looks – (at least) four stalled projects named apns4j:
- http://sourceforge.net/projects/apns4j/ (zero files in svn)
- https://apns4j.dev.java.net/source/browse/apns4j/ (zero *.java in svn, same ownername as above)
- http://code.google.com/p/apns4j/ (zero files in svn, same ownername as above)
- http://github.com/netmask/apns4j (three commits)
I didn’t look closer – maybe the last was gifted with a mature birth. The first three look like the project got stuck in choosing it’s hoster.
Google App Engine + XSLT
Okt 2
Google App Engine (java) doesn’t do XSLT transformations out of the box. Using a Transformer like
TransformerFactory.newInstance().newTransformer(new StreamSource(...)).transform(...);
yields a
Nested in javax.servlet.ServletException: java.lang.NoClassDefFoundError: com.sun.org.apache.xalan.internal.xsltc.runtime.BasisLibrary is a restricted class. Please see the Google App Engine developer's guide for more details.:
java.lang.NoClassDefFoundError: com.sun.org.apache.xalan.internal.xsltc.runtime.BasisLibrary is a restricted class. Please see the Google App Engine developer's guide for more details.
These google groups posts http://code.google.com/p/googleappengine/issues/detail?id=1452 and http://groups.google.com/group/google-appengine-java/browse_thread/thread/9c9fb88e1b175395 lead into the right direction but didn’t completely solve my problem. I added xalan.jar and serializer.jar from xalan-2.7.1 to war/WEB_INF/lib as suggested, but didn’t change the TransformerFactory setup.
This got me the WARNING log entries Failed calling setMethod method and Failed calling setIndent method.
This cyrillc blog-post lead me to removing all <xsl:output/> statements from the transformation and voilá – the trafo ran fine!
The whole procedure in short:
- add
xalan.jarandserializer.jartowar/WEB_INF/lib, - remove
<xsl:output/>from the stylesheet.
Got this mail from Sun recently:
– snip — snip — snip — snip — snip — snip — snip — snip –
Dear Java community,
You are receiving this email because you have either voted for or added a watch to one of our most wanted features in Java SE: 64-bit Java Plug-In (Bug ID: 4802695).
This is a one-time email notification, and we usually do not contact voters and watchers about bug fixes in early access releases; however, given the popularity of this feature, we have decided to spread this news: 64-bit Java Plug-In will be available in Java SE 6 Update 12.
Although 6u12 has not officially released yet, you can download the early access version and try it yourself. Send us your feedback at http://bugreport.sun.com or post your comments at 6uN Early Access Forum.
Thank you,
Java Developer Support Team
Sun Microsystems
– snip — snip — snip — snip — snip — snip — snip — snip –
The IT industry really isn’t always very fast-moving.