DFS Generation - Why it includes ucf.war?

Hello everybody

we are developing DFS Services with Composer and DFS framework Ant tasks.

When we generate a custom service, the EAR file always includes a 'ucf.war' automatically. It implies that every custom service that we implement contains this war (almost 30Mb !!!).

Why does it include it every time?

Is there any way to configure the Ant tasks to not include it?

Thank you!!

Find more posts tagged with

Comments

Francois Dauberlieu

can't remember when, can't remember where but I seem to remember reading somewhere, sometimes that this way, you're sure you always have the right version of the UCF, the one corresponding to your version of DFS when developing/packaging your services

Then again, I could be (an probably am) completely out of my mind

rpdiaz

Then , is it normal to include always a ucf.war in every package of services that we develop???

Thank you

Francois Dauberlieu

I guess yes, provided you need the UCF in your application. If I remember, in the DFS examples, there are some with and some without DFS. I never looked if they include this war file though

zhou_simonq

UCF is used to transfer content in a distributed environment and working with ACS/BOCS. If you include ucf.war in your custom services, you can specify UCF as transfer mode, as well as MTOM, BASE64. For more information, you can read DFS dev guide.

rpdiaz

Yes,

but I'm refering to the Ant Tasks. If I implement a DFS custom service, when it is packaged it always includes ucf.war, even if I do not use it in my service...

Thank you

zhou_simonq

It's included only for possible usage so that you can gain better performance in a distributed environment. In case you don't need UCF, you can remove it manually, I think.

- simon