[jbosstools-issues] [JBoss JIRA] Reopened: (JBIDE-5636) Java class in ESB project does not get compiled and deployed in ESB archive

[Rob Stryker (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBIDE-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Stryker reopened JBIDE-5636:
--------------------------------



I'll re-open just because I can't see how my patch actually fixed it and since I should ask some more questions.

To elaborate on what the problem I observed when testing was:
   The creation of the ESB project properly added what was called an output container reference. The problem was the JBTVirtualComponent was not returning this reference. So the "Module Assembly" property page was not showing this output container reference. 

Now in my local environment history, I show the following line of code which was the reason it wasn't being included:
  							if (referencedIVirtualComponent != null && referencedIVirtualComponent.exists()
									 && vReference.getDependencyType() == IVirtualReference.DEPENDENCY_TYPE_USES ) {

(Output container is a consumed reference, not a used reference).  However SVN doesn't show this line in any of the previous versions. But I remember being pretty damn sure that my environment was up to date and not modified, so now I'm scratching my head. 

Now dynamic web projects do not use this output container thing. it's a custom construct of JBT projects, not WTP projects. So that makes me wonder why your web project isn't exposing this resource properly. And I've *definitely* not been able to replicate that one. 

> Java class in ESB project does not get compiled and deployed in ESB archive
> ---------------------------------------------------------------------------
>
>                 Key: JBIDE-5636
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5636
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: esb
>         Environment: JBDS 3.0 CR1
>            Reporter: Aaron Pestel
>            Assignee: Rob Stryker
>            Priority: Blocker
>             Fix For: 3.1.0.CR2
>
>         Attachments: LabWebService.zip
>
>
> 1.)  Create an ESB project
> 2.)  Add a Java Action to the "src" directory
> 3.)  Add a Generic Action to the esb.xml and point it at the Java class just created
> 4.)  Add project to SOA-P 5 server
> 5.)  Notice ClassNotFound exception in server console
> If you look in the server deploy directory, their is no .class file for the .java file created in step #2

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira