ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sathwik Bantwal Premakumar (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (ODE-1060) ODE Standalone Server on TomEE
Date Wed, 13 Jul 2016 11:42:20 GMT

    [ https://issues.apache.org/jira/browse/ODE-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15374858#comment-15374858
] 

Sathwik Bantwal Premakumar edited comment on ODE-1060 at 7/13/16 11:41 AM:
---------------------------------------------------------------------------

Some thoughts on the packaging,

apache-ode-tomee.tar.gz

apache-ode-tomee
    * bin
        ** startup.sh (need this to indicate the location of conf, database and processes
as system properties)
    * conf
        ** ode-axis2.properties
        ** tomee.xml (To enable TM and Datasource)
    * database
        ** derbyjpa
        ** derbyhib
    * lib
        ** apache-ode-tomee-uber.jar
    * processes

# Tomee 1.7.4 (JEE 6 certified) or 7.0.1 (JEE 7 not yet certified)?
# Packaging of ODE web application within apache-ode-tomee-uber.jar? What options are available?
# apache-ode-tomee-uber.jar might have to be built without JaxRS,JaxWS,JSF?
# Uber jar will have OpenJPA dependencies included, For hibernate usage where do we store
and load Hibernate dependencies since the application is started from the uber jar?
# Slf4j Logging configuration? Tomee uses SLF4J with jdk implementation and ODE uses Log4j2
implementation.
# We need to externalize conf , embedded derby database and process deployment folders.
# Embedded database configuration is no more valid in this server configuration, as we will
have the datasource defined in the tomee.xml pointing to the database folder (Openjpa=derbyjpa,
Hibernate=derbyhib). TM and DS will be looked up from JNDI.
# User should be able to change the axis2.xml, hence where do we place axis2.xml and Axis2
kernel to load it?



was (Author: sathwik):
Some thoughts on the packaging,

apache-ode-tomee.tar.gz

apache-ode-tomee
    -bin
        -startup.sh (need this to indicate the location of conf, database and processes as
system properties)
    -conf
        -ode-axis2.properties
        -tomee.xml (To enable TM and Datasource)
    -database
        -derbyjpa
        -derbyhib
    -lib
        -apache-ode-tomee-uber.jar
    -processes

1) Tomee 1.7.4 (JEE 6 certified) or 7.0.1 (JEE 7 not yet certified)?
1) Packaging of ODE web application within apache-ode-tomee-uber.jar? What options are available?
2) apache-ode-tomee-uber.jar might have to be built without JaxRS,JaxWS,JSF?
3) Uber jar will have OpenJPA dependencies included, For hibernate usage where do we store
and load Hibernate dependencies since the application is started from the uber jar?
4) Slf4j Logging configuration? Tomee uses SLF4J with jdk implementation and ODE uses Log4j2
implementation.

5) We need to externalize conf , embedded derby database and process deployment folders.
6) Embedded database configuration is no more valid in this server configuration, as we will
have the datasource defined in the tomee.xml pointing to the database folder (Openjpa=derbyjpa,
Hibernate=derbyhib). TM and DS will be looked up from JNDI.
7) User should be able to change the axis2.xml, hence where do we place axis2.xml and Axis2
kernel to load it?


> ODE Standalone Server on TomEE
> ------------------------------
>
>                 Key: ODE-1060
>                 URL: https://issues.apache.org/jira/browse/ODE-1060
>             Project: ODE
>          Issue Type: New Feature
>          Components: Build System, Deployment
>            Reporter: Sathwik Bantwal Premakumar
>            Assignee: Sathwik Bantwal Premakumar
>             Fix For: 1.3.7
>
>
> This is to integrate ODE's axis2 based distribution as a standalone fatjar bundled with
TomEE.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message