DFS. Build multiple service modules into one ear-file

How to?
I've read DFS Development Guide and there is chapter with packageService task description how to build multiple modules with dfs-services into one ear-file.

But when I use one destination folder of such tasks as generateArtifacts, buildService my destination files are being overwritten (not appended).

Can someone describe the process?

I need diffirent module names because URLs to services are hardcoded in client.

Find more posts tagged with

Comments

lastnitescurry

please give examples of these different urls.... at worst what you want will not be possible... at best you will have to customise the DFS build scripts

zapirium

For example:

/context/module1/Service1
/context/module2/Service2

Real paths:
/services/syncdictionary/DictionaryService

/services/getsettings/SettingsService

What customizing do you mean?

Now I have my custom build.xml for each service module. It produces "syncdictionary.ear" and "getsettings.ear" files.
This ears have duplicate ucf.war inside and duplicate libraries(jars) from sdk.
I can achieve the result by modifiing *.ear/META-INF/application.xml, adding sections by hand:

...

<web>

<web-uri>services-syncdictionary.war</web-uri>

<context-root>/services/syncdictionary</context-root>

</web>

</module>

<web>

<web-uri>services-getsettings.war</web-uri>

<context-root>/services/getsettings</context-root>

</web>

</module>

...

and copiing second war file inside united ear.

I would like to make this process more automatic using DFS Built Tools with ant targets.