[
https://jira.jboss.org/browse/JBIDE-7500?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-7500:
------------------------------------------
Obviously this is a very strange state for a user to put the new action class in, but I
can see it happening by accident fairly regularly. So I think this is a good compromise -
going for the "intent" of what we think the user was after. I'm good with
the fixes and explanation.
ESB Editor 1.3 generates incomplete template when creating
New->Custom Action.
------------------------------------------------------------------------------
Key: JBIDE-7500
URL:
https://jira.jboss.org/browse/JBIDE-7500
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.0.Beta1
Environment: JBDS 4 Beta 1. RHEL 6, x86_64. Sun 1.6 JDK 64-bit.
Reporter: Ken Johnson
Assignee: Viacheslav Kabanovich
Fix For: 3.2.0.Beta2
Using the ESB Editor: after creating a new Service, I create a new custom action by
right-selecting the Action folder under the newly created service and choose New->
Custom Action...
I enter MyAction for both Name and Class and click OK.
Click the Class link under the Action section in the editor panel to bring up New ESB
Action dialog.
Enter Package name as org.jboss.foo
Browse for Superclass and choose AbstractActionPipelineProcessor
Everything else left as default.
Click Finish.
The following is generated for the constructor:
public MyAction() {
// TODO Auto-generated constructor stub
}
This is an invalid constructor at deployment time. The correct constructor should accept
ConfigTree, a local variable should be generated for the config info and
org.jboss.soa.esb.helpers.ConfigTree should be added to the imports. It appears prior
versions of the tooling worked this way.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira