[dna-issues] [JBoss JIRA] Updated: (DNA-310) Create dna-web subproject, with primary artifact being WAR file

[Brian Carothers (JIRA)]

     [ https://jira.jboss.org/jira/browse/DNA-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Carothers updated DNA-310:
--------------------------------

    Attachment: DNA-310.patch


Attached a patch that creates a new web-based project in extensions/dna-web-jcr-rest that provides a basic, RESTEasy-based servlet (that doesn't do anything useful yet) and some extra configuration to support in-container deployment.

This is pretty vanilla stuff, but here are some potentially debatable organizational assumptions that I made in laying out this project:

1.  I assumed that it made sense to package and test the JCR REST interface differently than any other future web interface (or I would have called the subproject dna-web).  I came to this assumption after years of using OPL (other peoples' libraries) that required me to do a chicken dance to enable or disable the features that I wanted.  In this model, people deploy the WAR if the want REST and don't deploy it if they don't.  One alternative would be to have a single dna-web subproject and just keep adding things to it as we add web-based features.

2.  I assumed that our web-based POMs could use the integration-test phase of the Maven lifecycle for testing instead of the test phase.  The integration-test phase happens after the package phase, so my assumption is basically that unit testing our web-based stuff outside of a container is of minimal value.  An alternative approach would be to define a separate, parallel subproject that only contained integration tests.

I'm perfectly happy to change the code if either of these (or any other) assumptions don't make sense to other people.  None of the code contributed so far assumes the approval of the URI scheme posted on the board as an RFC for DNA-309.

I believe that this patch addresses not only DNA-310 (create a web subproject), but also DNA-311 (integrate with RESTEasy), and DNA-317 (integrate and test in-container).  There are still separate sub-tasks open for deciding on a URI scheme, implementing the URI scheme, and deploying DNA to a webapp.




> Create dna-web subproject, with primary artifact being WAR file
> ---------------------------------------------------------------
>
>                 Key: DNA-310
>                 URL: https://jira.jboss.org/jira/browse/DNA-310
>             Project: DNA
>          Issue Type: Sub-task
>          Components: Web Application
>    Affects Versions: 0.3
>            Reporter: Johnny Verhaeg
>             Fix For: 0.5
>
>         Attachments: DNA-310.patch
>
>
> DNA should be provided via a WAR file so that it can be deployed in and made available to applications such as JBoss Tools, Teiid Designer, etc., via a container such as JBoss AS/EASP.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira