Release notes for GlassFish ESB Release Candidate 1

JBI Runtime / Admin tools:

• Issue 411 Application verifier does not behave consistently when "startOnVerify" is true. If "startOnVerify" is true, the verify command should always start up the component if necessary before performing verification, and then return the component to its original state. Currently the component is started after the verification, causing different results when the same verify command is repeated; the first one fails, the second one succeeds.
  • Workaround: Either repeat the verify command or start the required components before running the first verify command.
    
    
• Issue 512 If the key store and/or trust store password in a configuration have empty values, they appear pre-populated with data because they show up as "******". A null value should not be displayed as an obfuscated string, it should be displayed as an empty string.
  • Workaround: If the password is actually null the obfuscated string can be safely ignored.
    
    
• Issue 884 Components should be configurable when in the stopped state. Currently the runtime does not allow a component to be configured unless it is in the started state.
  • Workaround: Start the component before attempting to configure it.
    
    
• Issue 885 Web console should allow configuration of stopped components. Currently the admin console does not allow a component to be configured unless it is in the started state.
  • Workaround: Start the component before attempting to configure it.
    
    

This page (revision-3) was last changed on 25-Nov-08 21:11 PM, -0800 by MarkWhite.
This page was created on 14-Nov-08 15:12 PM, -0800 by FrankKieviet.

More info...