[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5546) ESB examples packaged with JBDS 3.0 fail with SOA-P 5.0

[Martin Malina (JIRA)]

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

Martin Malina commented on JBIDE-5546:
--------------------------------------

The Project Examples were supposed to work out of the box with soa-p 4.3, but that isn't always true either.
>From my email:

We did some experimenting with Dominik and found out that it stands and falls on the name of the runtime. It only works out of the box if you install SOA-P 4.3 via the installer AND the install dir is jboss-soa-p.4.3.0 so it suggests this as the runtime name (but you still have to fix the JRE problem). If you have soa in a different dir and you don't change the runtime name to jboss-soa-p.4.3.0 then it doesn't work and you have to follow the same 12 steps Brian described for SOA-P 5.0. On the other hand, if you install SOA-P 5.0 runtime and name it as jboss-soa-p.4.3.0 Runtime, then it works out of the box as well.


> ESB examples packaged with JBDS 3.0 fail with SOA-P 5.0
> -------------------------------------------------------
>
>                 Key: JBIDE-5546
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5546
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: esb
>    Affects Versions: 3.1.0.M4
>         Environment: JBossTools-Update-3.1.0.v200912141523M-H176-RC1.zip
> or
> jbdevstudio-macosx-carbon-3.0.0.v200912182118M-H46-CR1.jar
> SOA-P 5.0 ER5
>            Reporter: Martin Malina
>         Attachments: client_part.jpg, server_part.jpg
>
>
> Currently the SOA-P quickstarts store the jboss-esb.xml in the root dir of each quickstart under jboss-as/samples/quickstarts. When you run a quickstart using the supplied ant script, jboss-esb.xml is first moved to META-INF which is the required location for it.
> If you only try to import such a project to JBoss Tools/JBDS it won't work since it won't look for the jboss-esb.xml in the root dir.
> This is not exactly a problem of JBoss Tools as such, but I'm reporting it here for a reference.

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