Max Rydahl Andersen wrote:
I don't recall binary results being available in the
projects...this is only there when deploying, correct?
yes
> *4. Integrate with current ESB editor
> *For now, Jboss tools has a editor for jboss-esb.xml, we also can associate the
file with the editor
>
Not sure what this means ?
you know, JBoss tools has a ESB tree editor, I mean that when the
project is created and the user want to edit the jboss-esb.xml config
file, we can
open the file using the ESB editor .
> *5. Sample content(Template):*
> Provide a extension point for it. the extension has the following
> properties at least :
>
> * esb version: the templates will be filtered by the version of the esb facet
of the project.
>
> * description : when user select a template, on the wizard page, show
> the description to the user.
>
> * template: the template should be the main stuff of this extension
> point, we should determine the format of the template, since it may contain
some source
> code and other artifacts such as some ESB config files, so the template may be
an archive file such as a jar
> file or some other sort of it.
> * template install class: to handle some additional operations that template
providers want.
>
All sounds good - but I'm interested in getting the above issues done first so we get
something usable for deployment upfront.
John suggested to quickly develop a prototype of the wizard at first, I
think it may be worked out next week and then start to code base on it.
Denny