Service Units and non-wsdl files
|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
 |
Service Units and non-wsdl files
by Marco-152
::
Rate this Message:
In the Service Unit / Service Assembly build process, the only files
that are included in the archives are the WSDL, the BPEL (for the BPEL SE Servuce Unit) and the jbi configuration files. It's possibile to include (in a binding component service unit) also files of different kind? Marco. |
|
|
Re: Service Units and non-wsdl files
by Tientien Li-2
::
Rate this Message:
Marco,
In NetBeans SOA tooling, each SE project implements its own SU packaging logic. If you have special artifacts needed to be packaged into a SE SU jar, you can contact the SE project team to extend its packaging logic. BC are packaged by CompApp. Currently, there is no plan to include files other than wsdl and xsd. If you have any special requirements for BC SU jars, please your use case or file a REF against the CompApp project. Also it is relatively easy to write a post processing script to adds your own artifacts to SU and/or SA generated by SOA tooling. Then you can deploy the modified SA using the JBI manager in NB or command line tools. HTH, -- Tientien Li Marco wrote: > In the Service Unit / Service Assembly build process, the only files > that are included in the archives are the WSDL, the BPEL (for the BPEL > SE Servuce Unit) and the jbi configuration files. > > It's possibile to include (in a binding component service unit) also > files of different kind? > > Marco. > > > -- Tientien Li Netbeans SOA Tools, http://enterprise.netbeans.org Open ESB Community, http://open-esb.org |
|
|
Re: Service Units and non-wsdl files
by Marco-152
::
Rate this Message:
Hi,
Thank for your answer. It's not clear for me how to write a post-processing script: do you mean an ant script? It's possible to hook this scripts to the CompApp build (for example installing it as netbeans module) to automaticaly "insert" it into the CompApp build just installing a nbm? Marco. On Tue, 2008-11-04 at 08:55 -0800, Tientien Li wrote: > Marco, > > In NetBeans SOA tooling, each SE project implements its own SU packaging > logic. If you have special artifacts needed to be packaged into a SE SU > jar, you can contact the SE project team to extend its packaging logic. > BC are packaged by CompApp. Currently, there is no plan to include files > other than wsdl and xsd. If you have any special requirements for BC SU > jars, please your use case or file a REF against the CompApp project. > > Also it is relatively easy to write a post processing script to adds > your own artifacts to SU and/or SA generated by SOA tooling. Then you > can deploy the modified SA using the JBI manager in NB or command line > tools. > > HTH, > > -- > Tientien Li > > Marco wrote: > > In the Service Unit / Service Assembly build process, the only files > > that are included in the archives are the WSDL, the BPEL (for the BPEL > > SE Servuce Unit) and the jbi configuration files. > > > > It's possibile to include (in a binding component service unit) also > > files of different kind? > > > > Marco. > > > > > > > > |
|
|
Re: Service Units and non-wsdl files
by Tientien Li-2
::
Rate this Message:
Marcok,
For the command line operation, anything that can process jar and zip files will work in this case. For NetBeans, you can manually modify the build script of a CompApp project, but I don't think there is any easy way to automatically attach additional ant tasks to a CompApp projects. HTH, -- Tientien Li Marco wrote: > Hi, > Thank for your answer. > It's not clear for me how to write a post-processing script: do you mean > an ant script? It's possible to hook this scripts to the CompApp build > (for example installing it as netbeans module) to automaticaly "insert" > it into the CompApp build just installing a nbm? > > Marco. > > > On Tue, 2008-11-04 at 08:55 -0800, Tientien Li wrote: > >> Marco, >> >> In NetBeans SOA tooling, each SE project implements its own SU packaging >> logic. If you have special artifacts needed to be packaged into a SE SU >> jar, you can contact the SE project team to extend its packaging logic. >> BC are packaged by CompApp. Currently, there is no plan to include files >> other than wsdl and xsd. If you have any special requirements for BC SU >> jars, please your use case or file a REF against the CompApp project. >> >> Also it is relatively easy to write a post processing script to adds >> your own artifacts to SU and/or SA generated by SOA tooling. Then you >> can deploy the modified SA using the JBI manager in NB or command line >> tools. >> >> HTH, >> >> -- >> Tientien Li >> >> Marco wrote: >> >>> In the Service Unit / Service Assembly build process, the only files >>> that are included in the archives are the WSDL, the BPEL (for the BPEL >>> SE Servuce Unit) and the jbi configuration files. >>> >>> It's possibile to include (in a binding component service unit) also >>> files of different kind? >>> >>> Marco. >>> >>> >>> >>> >> > > > -- Tientien Li Netbeans SOA Tools, http://enterprise.netbeans.org Open ESB Community, http://open-esb.org |
| Free embeddable forum powered by Nabble | Forum Help |
