[
https://issues.jboss.org/browse/JBESB-3734?page=com.atlassian.jira.plugin...
]
Tom Cunningham commented on JBESB-3734:
---------------------------------------
Added options for farm and exploded. Tested farm option against SOA-P 5.2, seems to
work fine. The plugin had already been using profile service, so no changes needed
there.
tcunning@localhost:jonplugin]$ svn commit
Sending
jonplugin/as5/src/main/java/org/jbosson/plugins/jbossesb/ESB5Component.java
Sending jonplugin/as5/src/main/resources/META-INF/rhq-plugin.xml
Transmitting file data ..
Committed revision 38087.
SOA-P 5 ESB Deployment options prompts are asking for wrong
information
------------------------------------------------------------------------
Key: JBESB-3734
URL:
https://issues.jboss.org/browse/JBESB-3734
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Management
Affects Versions: 4.11
Reporter: Tom Cunningham
Fix For: 4.11 CP1
Steps to Reproduce: #. Start SOA5
#. From Admin Console (admin-console) expand and select localhost -> JBossAS
Servers - JBoss SOA-P 5 (default) -> JBoss ESB -> Deployments
#. Click 'Add a new resource' button
project_key: SOA
When deploying a new ESB using admin-console or JBoss Operations Network, the
ESB plug-in is asking for deployment options which are only valid for SOA 4.
For example, Deployment Location is asking for a path but in SOA 5
ProfileService is used to deploy managed components meaning that a destination
directory can not be selected but instead the user should be selecting whether
to deploy farmed or not.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira