[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections

[Brian Fitzpatrick (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-9771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12631907#comment-12631907 ] 

Brian Fitzpatrick commented on JBIDE-9771:
------------------------------------------

Yes, there are ripples there. I've asked Nick to comment on the particulars, but I'm betting it's all related. 

> JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
> ----------------------------------------------------------------------------------
>
>                 Key: JBIDE-9771
>                 URL: https://issues.jboss.org/browse/JBIDE-9771
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: esb
>    Affects Versions: 3.2.2.M1
>            Reporter: Len DiMaggio
>            Assignee: Viacheslav Kabanovich
>            Priority: Blocker
>             Fix For: 3.2.2.M2, 3.3.0.M4
>
>         Attachments: no_bpel_action_jbide-9771.jpg
>
>
> See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4 server is defined as the runtime - the BPELInvoke action is not included in the OOTB action list.
> I also tried explicitly adding the server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the runtime and the ESB project classpath. 
> Slava, can you look into this? If the file is on the classpath, I'm wondering why your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira