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

[Denny Xu]

John Graham wrote:
> I'd like to get some impressions about the usability of this wizard.
>
> First, however, a note: Denny is building this wizard within the
> structures defined by WTP, and so the options are somewhat constrained.
>
> The first wizard page (attachment: esb-wizard-1.jpg) asks for a "Target
> Runtime" and a "JBoss ESB Version." Unless we're expecting that multiple
> ESB instances (and versions) can run in one AS configuration, then
> ideally I think the ESB version should be determined automatically by
> the wizard, based on the target runtime.

I think the scenario might be that, before create a esb project, the 
user should know which version of esb
project he want to create, so the esb version should  the entry point of 
the work flow.
the relationship of  "Target Runtime" and "Jboss ESB Version"  has 
already been defined in JBoss AS runtime,  if you
select a specified ESB version and then only supported Target Runtimes 
will be displayed in the runtime list.
>  Also, it seems that we are hard
> coding the runtime values (4.2 and 4.3), whereas it would be better to
> determine the version based on the target runtime (for instance, I had
> JBoss ESB 4.4 installed, and it was confusing to have to select 4.3 for
> it.)
>   

The runtime version value is defined as ESB facet version and also has 
been associated with AS runtime type through  extension  points.


> The second wizard page (attachment: esb-wizard-2.jpg) configures the
> project structure and other meta-data (e.g. the facet). It asks for the
> "JBoss ESB Runtime," but that was provided on the first page. I don't
> see a use case where a different runtime value on the second page would
> make sense, so I suggest that the wizard should just take the value from
> the first page, and not show this detail on the second page.
>   
There are two runtime concepts in the wizard, Server Runtime and ESB 
Runtime,  Server Runtime is 
the runtime of the target jboss server , since wtp server adapter does 
not contain any esb runtime info,
 and we can not get any esb  runtime info  from the target runtime of 
the first page ,
so we have to define a ESB runtime to configure the classpath that a esb 
project need.

certainly, if the user select target server runtime  at the first page 
and the server has already get ESB runtime
installed with it, we can provide  options for the user to use the 
server provided ESB runtime and specify another
ESB runtime.
since the project wizard is for development, users might not specify a 
target runtime at first page, so I think at the first page
the ESB runtime field should make sense. The purpose of specifying ESB 
runtime is for configuring the classpath the project.

> Don't know if this is related to the appearance of the Rosetta jar in
> the project classpath or not: On my system (FC8), the drop down for
> "JBoss ESB Runtime" did not work (attachement: esb-wizard-2-err.jpg);
> instead a thin line appeared.
>   
the ESB runtime should be predefined at the preference page under JBoss 
Tools --> JBoss ESB Runtime, and you also can new a ESB runtime
at the second wizard page when creating the project, and the esb runtime 
version should match the JBoss ESB version selected at the first page.

Denny
> -- John
>
>
>
> On Tue, 2008-09-09 at 16:37 +0800, Denny Xu 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.
>>     
>>> 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?
>>     
>>> It does not appear that you can create an esb archive or deploy yet, so I did try that.
>>>   
>>>       
>> You can find the esb archive under jboss esb server deployment folder, 
>> such as: /home/fugang/jboss-all/jbossesb-server-4.3.GA/server/default/deploy
>> it's a *.esb folder contains all stuff that a esb need.
>>
>>
>> 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
>>     
>>
>> ------------------------------------------------------------------------
>>
>>
>> ------------------------------------------------------------------------
>>
>>
>> ------------------------------------------------------------------------
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Soa-tools-list mailing list
>> Soa-tools-list at redhat.com
>> https://www.redhat.com/mailman/listinfo/soa-tools-list