[
http://jira.amdatu.org/jira/browse/AMDATU-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivo Ladage - van Doorn resolved AMDATU-258.
-------------------------------------------
Resolution: Fixed
WAR deployment works now (assuming context path is /, other context paths are
covered by issue AMDATU-323). To test, read this WIKI page;
http://www.amdatu.org/confluence/display/Amdatu/WAR+deployment
> Support for WAR deployment
> --------------------------
>
> Key: AMDATU-258
> URL: http://jira.amdatu.org/jira/browse/AMDATU-258
> Project: Amdatu
> Issue Type: New Feature
> Components: Amdatu Web, Build & Release management
> Affects Versions: 0.2.0
> Reporter: Bram de Kruijff
> Assignee: Ivo Ladage - van Doorn
> Fix For: 0.2.0
>
>
> A common real world requirement in real life projects is that an application
> can be deployed on top of an existing enterprise infrastructure. Put simply,
> it must be deployable as a WAR/EAR. I would like us to support this type of
> distribution which would roughly require:
> 1) Create a host WAR with a proxy servlet that delegates to our embedded HTTP
> service
> 2) Integrate a bridge implementation within Amdatu that recieves te requests
> from the proxy
> 3) Deal with configuration specifics (work directory etc)
> 4) Create an assembly for the deployment type
> Most is provided by the Felix Http Service implementation we are using
> allready (see http://felix.apache.org/site/apache-felix-http-service.html).
> Finally note that this scopes to the deployment issue, NOT actually
> integrating bridging with application server provided services and
> management. The latter should be considered an entirely seperate issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
