[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3733) JBoss ESB classpath container does not set source attachment location

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-3733:
--------------------------------------------

isn't this expected behavior ?

The IDE doesn't bundle each mutation of the ejb3 and jbossesb source code so how can we provide it out of the box without the src being available in i.e. a maven reposistory or similar ?

> JBoss ESB classpath container does not set source attachment location
> ---------------------------------------------------------------------
>
>                 Key: JBIDE-3733
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3733
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: esb
>    Affects Versions: 3.0.0.CR2
>            Reporter: John Graham
>            Assignee: Denny Xu
>            Priority: Critical
>             Fix For: 3.0.0.GA
>
>         Attachments: jboss-ejb3-src.zip, jbossesb-rosetta.zip
>
>
> *Fresh install of JBT 3.0 or JBDS 2.0*
> 1. Define a SOA-P 4.3 runtime environment and server connection
> 2. Create an ESB project, using the defined SOA-P 4.3 environment
> 3. In the ESB runtime classpath container, locate jbossesb-rosetta.jar
> 4. Right click on jbossesb-rosetta.jar and set the source code to point at the attached jar
> 5. Expand into a jbossesb-rosetta.jar package, and double click on a class
> 6. Notice that the Eclipse editor says that the source code can not be found
> 7. Open the JBoss AS classpath container
> 8. Locate jboss-ejb3.jar and attach the source zip provided here
> 9. Expand into a jboss-ejb3.jar package, and double click on a class
> 10. Notice that the source code for the class is found and displayed in an editor
> 11. Notice that the source code for jbossesb-rosetta.jar classes also are now found, and can be displayed in the editor
> The expected behavior would be finding the source code for jbossesb-rosetta.jar after setting only the source attachment for it in the JBoss ESB classpath container.

-- 
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