My thoughts (HTH):
guvnor-webapp-drools's web.xml should contain the context parameter (and
jars), since it's the "generic, portable war"
that runs on gwt hosted, tomcat, jetty, ...
Long term, we need an issue in resteasy or jboss AS that the existence
of context parameter shouldn't blow up AS.
Short term, in the jboss AS specific war assembly, we can exclude the
jars and hopefully remove the context parameter by maybe using some sort
of unpack option filtering:
If we can replace "resteasy.injector.factory" by
"disabled.resteasy.injector.factory" it' should be ok.
Problem is it it only filters build properties, so try asking on the
maven user list if this is somehow possible?
Alternatively, duplicating the web.xml for the jboss war is not
Op 21-06-12 00:04, Mikael Lönneberg schreef:
Thought I would get your input before I go any further on the task of
creating the separate builds for the different target platforms.
In switching to RESTeasy as the jax-rs framework this causes an issue
deploy to AS7 as RESTeasy is already bundled/provided in AS7. So for
all other platforms we need to include the resteasy-*.jar and for as7
they need to be removed. This is pretty straight forward.
However we also need to add or remove this section
to guvnor-webapp-drools web.xml depending on the target platform,
this is were it becomes a little tricky.
What version should be checked in? Running in hosted mode requires the
section to exist, running Arquillian integration-tests requires it to
be removed, since integration-tests are run on as7.
I'm leaning towards having the section included by default and remove
it in GuvnorIntegrationTest or having the build process filter and
create a new version per platform which can then be copied into the
WebArchive in GuvnorIntegrationTest.
What are your thoughts?
Mikael Lönneberg (gwendo)
rules-dev mailing list
With kind regards,
Geoffrey De Smet