building flex enterprise applications

[Dimitri Alexeev]

Hi,

there is a nice configuration description on the the project site, to
set up a Flex 2 project as a dependency of a web application project.
( http://www.israfil.net/projects/mojo/maven-flex2-plugin/usage.html
)

But there is still one problem with deployment in case we need Data
Services:
The services-config.xml is needed by both <swf> and <war> projects.

And while maven-flex2-plugin is unable to lookup for services-
config.xml in <war> project during the <swf> build process, we are
forced to create and maintain another copy of services-config.xml
inside of <swf> project...

I am curious if there is a workaround to avoid redundant copy of
services-config.xml in both projects?


best regards
Dimitri

[Sudhan]

Hi Dimitri,

I will also be interested to know that the services-config.xml
contains ${context.root} and it also needs to be passed along with
this config file. Is there a way to pass the context.root as a
parameter.

thanks,

Sudhan

On Jan 16, 5:43 am, Dimitri Alexeev <dimitri.alex...@googlemail.com>
wrote:

[Christian Edward Gruber]

I was thinking of adding another maven packaging type for flex-
services-config, such that you'd create a separate maven project with
a simple pom
<project>
...
<groupId>my.group</groupId>
<artifactId>myproject-flex-services-config</artifactId>
<version>1.2.something.or.other</version>
<packaging>flex-services-xml</packaging>
</project>

Then have that as a dependency in the swc or pom projects. If the
plugin detects a dependency of that type, it'll pull in that services
config. This way several key files can be shared around.

The problem with a solution like this is that it's very friendly to
the way maven thinks of projects - 1 artifact per project, and is hard
to organize in terms that something such as flex-builder would be
comfortable with. That's not a big deal if you let local developers
keep a local copy for flex builder's purpose, but you have a
"canonical" build that's done by maven (in a continous build system or
release process).

Thoughts? Anyone have a better solution in mind? Or another way to
make this approach play friendly with FB? It's trivial to make it
work with an ant or script based approach, but FB makes assumptions
the command-line compilers don't automatically make.

Christian.