Weblogs |
![](/images/tab_weblogs.gif) |
Hudson's growth chart
Seiji Sogabe, a Hudson committer, put together Hudson's growth chart. He put together a chart of the hudson.war size from 1.100 to 1.300. This is another way to see the progress in Hudson. Off the top of my head, a big jump in 1.160 or so is probably the native Maven2 support... —
Kohsuke Kawaguchi
Most session videos posted for M3DD
Sorry for the delay ... we finally got around to processing and posting most of the remaining session videos. To find the videos please check out the links on the Sessions tab (both for Technical Sessions and Lightning Talks). Note that... —
Terrence Barr
SwingX 1.0 in Sight
SwingX 1.0 is coming to fruition. We are making the final dispositions of what's in and what's out for the 1.0 release. If you have any comments regarding the decision to include or remove something from the 1.0 target list, please see my thread in the SwingLabs Forums... —
Karl Schaefer
Forums |
![](/images/tab_forums.gif) |
JAXB: Java code generation for Annotation tag elements
Hi, Can anyone help me with the following issue? I have defined TestObject object in WSDL schema definition. This object has defined annotations (documentation and appInfo) in its schema. I am trying to get the JAVA code generated for these defined annotations. I am also posting my sample TestObject and CustomAppInfo elements schema definition. We are using CXF's WsdlToJava for the code generation tool. Any suggestions would be greatly appreciated.
... —
glassfish croaks
I have three JBI service assemblies running in two Glassfish instances. Two service assemblies are running in one Glassfish node on Windows, the third service assembly is running in a Glassfish node on Linux. The first service assembly commands the second service assembly, receives a response, then the first service assembly commands the third service assembly and receives a response. Everything appears to have worked - but, in reality the Glassfish containing the third service assembly has died. The logs do not show anything... —
How does SynchronizationServlet work?
Here's what I noticed after a period of time using my Glassfish app cluster: - I have 2 servers, appserv01 and appserv02. - DAS running on appserv01 together with a node agent app01-agent. - Another node agent app02-agent running on appserv02. - I have a cluster my-app-cluster running with app01-instance and app02-instance on each server respectively. Typically, when I start up my cluster, the SynchronizationServlet will kick in and be done in about 10 seconds. Quick enough. Let's say I deploy an EAR file, say about 20MBs in size while the cluster is active. The deployment is successful and I can use the application immediately (as expected). However, if I were to stop and restart the cluster at this point of time (after deploying the EAR file)... —
![](/im/a.gif)