[jbosstools-dev] Re: [Fwd: [Soa-tools-list] a rough esb project wizard is ready]

[Denny Xu]

there are some predefined ESBs in ESB runtime, such spring.esb, 
jrules.esb and jbpm.esb etc,  so
the user develops one kind of esb, the classpath should contains  jars 
from the corresponding esb folder

here is a piece of xml to show what should be included, it comes from  
jbossesb-server-4.3.GA/samples/quickstarts/conf/base-build.xml:
<path id="deployment-classpath">
            <fileset 
dir="${org.jboss.esb.server.server}/deploy/jbossesb.sar/lib" 
includes="*.jar"/>
            <!-- jbossesb config -->
            <fileset 
dir="${org.jboss.esb.server.server}/deploy/jbossesb.esb" includes="*.jar"/>
            <pathelement 
location="${org.jboss.esb.server.server}/deploy/jbossesb.esb"/>
            <!-- jbpm config -->
            <fileset 
dir="${org.jboss.esb.server.server}/deploy/jbpm.esb" includes="*.jar"/>
            <pathelement 
location="${org.jboss.esb.server.server}/deploy/jbpm.esb"/>
            <pathelement 
location="${org.jboss.esb.server.server}/lib/cglib.jar"/>
            <pathelement 
location="${org.jboss.esb.server.server}/lib/dom4j.jar"/>
            <!-- smooks config -->
            <fileset 
dir="${org.jboss.esb.server.server}/deploy/smooks.esb" includes="*.jar"/>
            <pathelement 
location="${org.jboss.esb.server.server}/deploy/smooks.esb"/>
            <!-- jbrules config -->
            <fileset 
dir="${org.jboss.esb.server.server}/deploy/jbrules.esb" includes="*.jar"/>
            <pathelement 
location="${org.jboss.esb.server.server}/deploy/jbrules.esb"/>
            <!-- spring config -->
            <fileset 
dir="${org.jboss.esb.server.server}/deploy/spring.esb" includes="*.jar"/>
            <pathelement 
location="${org.jboss.esb.server.server}/deploy/spring.esb"/>
            <!-- soap config -->
            <fileset 
dir="${org.jboss.esb.server.server}/deploy/soap.esb" includes="*.jar"/>
            <pathelement 
location="${org.jboss.esb.server.server}/deploy/soap.esb"/>
            <fileset dir="${org.jboss.esb.server.server}/lib" 
includes="activation.jar, mail.jar, jboss-ejb3x.jar"/>
            <!-- general libs -->
            <pathelement 
location="${org.jboss.esb.server.home}/lib/commons-logging.jar"/>
            <pathelement 
location="${org.jboss.esb.server.home}/lib/commons-codec.jar"/>
            <pathelement 
location="${org.jboss.esb.server.home}/lib/jboss-system.jar"/>
            <pathelement 
location="${org.jboss.esb.server.home}/lib/jboss-xml-binding.jar"/>
            <pathelement 
location="${org.jboss.esb.server.server}/lib/jbossts-common.jar"/>
        </path>

Denny

Max Rydahl Andersen wrote:
> ah yes, I forgot that ESB "leaks" those jars to deployed projects.
>
> What we need to do is that the ESB facet asks the server for those 
> jars and then we pick them up.
>
> We need to know which jars exactly should we add to the clients 
> classpath ?
>
> Specific jars from .esb or just deploy/**.esb/*.jar ?
>
> /max
>
>
>> most of the ESB specific jars are in the deploy directory.
>>
>> Max Rydahl Andersen wrote:
>>>>>> Hi Jeff
>>>>>> I include some mail-lists,  someone in the list may be interested 
>>>>>> in it too.
>>>>>
>>>>>>> 1) The project wizard did not add jbossesb-rossetta.jar to the 
>>>>>>> classpath, I had to do this myself.
>>>>>
>>>>>> Did you specify a esb runtime when creating the project? I tested 
>>>>>> it and the jar is included in the classpath under "JBoss ESB 
>>>>>> Runtime" container.
>>>>>
>>>>> Isn't that jar supposed to be picked up by JBoss AS classpath 
>>>>> container ?
>>>>>
>>>>> When we deploy to SOA-P there is no additional runtimes needed.
>>>> If I understand jeff's concern correctly the problem is that the 
>>>> runtime is fine but the compiler in Eclipse needs the jar in its 
>>>> "build path".
>>>
>>> Yes I know. And my point is that all other services provide by AS 
>>> normally
>>> is to be found in the AS classpath.
>>>
>>> If it is not in there where is it ?
>>>
>>> -max
>>>
>>>>>>> 2) Providers shows up below services in the xml source, and the 
>>>>>>> providers element is red x and red underline with the message: 
>>>>>>> invalid content was found, no child elements expected.
>>>>>>> 3) Filter would not always show up right away when creating a 
>>>>>>> JMS Provider Bus (thought we were going to name these 
>>>>>>> channels?). If I moved the "bus" up or down, or otherwise then 
>>>>>>> it showed up.
>>>>>>> 4) Should id be busid in the name (it is in the xml)?
>>>>>>> 5) Under providers, JMS Provider, name should be selectable from 
>>>>>>> a list, e.g., JBossMQ?
>>>>>>>
>>>>>> about 2, 3, 4 and 5, it seems that it's something related to 
>>>>>> jboss-esb.xml editor, right?  Max , do you have any comments?
>>>>>
>>>>> Yes - Jeff should report these in jira with screenshots and info 
>>>>> so they can get fixed.
>>>>>
>>>>> Denny - about the download build page please create jira with it 
>>>>> so we won't forgot
>>>>> to get the smooks plugin available for standalone download. (even 
>>>>> thouhgh for it to work
>>>>> you need AS etc. too)
>>>>>
>>>>> /max
>>>>>
>>>>>>
>>>>>> Denny
>>>>>>
>>>>>>> Jeff
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ----- Original Message -----
>>>>>>> From: "Denny Xu" <dxu at redhat.com>
>>>>>>> To: "Jeffrey Delong" <jdelong at redhat.com>
>>>>>>> Sent: Sunday, September 7, 2008 8:55:59 PM GMT -07:00 US/Canada 
>>>>>>> Mountain
>>>>>>> Subject: Re: Fwd: [Fwd: [Soa-tools-list] a rough esb project 
>>>>>>> wizard is ready]
>>>>>>>
>>>>>>> Hi Jeff
>>>>>>>
>>>>>>> Jeffrey Delong wrote:
>>>>>>>
>>>>>>>> Hi Danny,
>>>>>>>>
>>>>>>>> Is this plugin compatible with Eclipse 3.4 (Ganymede) or 3.3 
>>>>>>>> (Europa)?
>>>>>>>>
>>>>>>> Eclipse 3.4 is fine
>>>>>>>
>>>>>>>> Where specifically can I access the plugin? I would like to 
>>>>>>>> test it out? Is there a list of required dependencies?
>>>>>>>>
>>>>>>> the plugin has been added to nightly build,  so you can get it 
>>>>>>> from jboss tools nightly build: 
>>>>>>> http://download.jboss.org/jbosstools/builds/nightly/,  it 
>>>>>>> requires WTP 3.0.
>>>>>>>
>>>>>>> thanks very much to test it, if you have any suggestion and 
>>>>>>> requirement and any problem,  please fell free to let me know.
>>>>>>>
>>>>>>> Thanks
>>>>>>> Denny
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Soa-tools-list mailing list
>>>>>> Soa-tools-list at redhat.com
>>>>>> https://www.redhat.com/mailman/listinfo/soa-tools-list
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>
>
>