Hide Forgot
Date of First Response: 2007-11-27 13:22:30 project_key: SOA Currently the ESB bits (jbossesb.sar, jbossesb.esb, etc) are deployed into the production & all configurations but not the "default" configuration. Default is the typical configuration for someone starting off their development process.
I believe this has already been discussed by the platform team. In any case it is an issue for them and not the ESB team. Assigning to Trevor to handle.
There is no 'default' configuration in EAP. We are not going to add a 'default' to EAP.
There is definitely a "default' configuration in the EAP. It's included in the jboss-as/server directory.
Link: Added: This issue is duplicated by SOA-139
Yes, but then they have CORBA that is supported in EAP all and production profiles, but not default. So how is this any more confusing?
Link: Added: This issue related SOA-487
Verified in 4.3 IR5 - default config contains ESB