Petals ESB 3.0.5 has just been released.
As a maintenance release, there was some bug fixes, mostly for View and EIP.
But most important, we migrated to JDK 6, which is available for download.

Changes :
- Migrating to JDK 1.6
Petals ESB 3.0.5 is now supported on JVM 1.6
JVM 1.5 is no longer supported.
However, you can still use 1.5 Bytecode in JVM 1.6
  - 24 Bug fixes :

• [Router] the order of elected endpoints is not taken account with sendSync method
• [Easywsdl] Unable to read wsdl with imports
• [JMX RMI Connector] Client RMI connections hang when remote server network interface are unreachable
• [WebConsole] unable to show a large payload
• [Ant] petals-configure-service-assembly task is unable to update properties when a '.' is in the su name
• [Registry] Automatic synchronization seems to be broken
• [Registry] Master looses remotes endpoints when synchronizing manually the registry
• [Topology] The topology synchro period is 30s even if it is defined in the server.properties file
• Kernel] User configuration causes an infinite loop and Stack overflow...
• Launcher] Petals do not restart after a crash
• [CDK] unable to destroy a registration
• [CDK] RuntimeConfigurationNotifier.setAttributes() do not notify in the component
• [EIP SE] unable to set an error on Bridge
• [EIP SE] error on a endpoint definition
• [EIP SE] manage the MEP desynchronously with the configuration
• [EIP SE] unable to manage fault or error : bug on Routing Slip so
• [BC SOAP] unable to subscribe on cdk topic
• [SOAP BC] In the provide mode, the SOAP component throws an error when the SOAP request contains attachment
• [SOAP BC] In the consume mode, the JBI fault in not wrapped in to the SOAP fault
• [KPI SE] unable to reinstall the component
• [KPI SE] unable to restart the component
• [SE-KPI] Unable to use the default configuration
• [SOAP BC] In the provide mode, the NMR attachments are not copied into the SOAP request