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, 10 Aug 2016 17:37:20 GMT

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

Sathwik Bantwal Premakumar edited comment on ODE-1060 at 8/10/16 5:36 PM:
--------------------------------------------------------------------------

Created a experimental git branch https://github.com/apache/ode/tree/ODE-1060 with couple
of initial commits.

# Tomee 1.7.4 (JEE 6 certified) or 7.0.1 (JEE 7 not yet certified)?
** Went ahead with Tomee 7.0.1 as it has good support to deploy a jar as a webapp (deployClasspathAsWebApp).
# Packaging of ODE web application within apache-ode-tomee-uber.jar? What options are available?
** The packaging will be a zip file which will contain tomee libraries and ode war. Tomee
will be started in embedded mode and will deploy the embedded ODE war. The datasource used
will be derby database. This kind of packaging helps in resolving library conflicts that may
arise in future. Hibernate is the preferred JPA for deployment for customers and default configured
is OpenJPA, It gives the flexibility to engage Hibernate at the Embedded Tomee or with in
the ODE war. This will also help in deploying customer specific implementation for custom
XPATH functions and ODE event listeners.
# apache-ode-tomee-uber.jar might have to be built without JaxRS,JaxWS,JSF dependencies of
Tomee?
** As indicated the packaging will be a zip archive and embedded tomee has JaxRS,CXF and JSF
excluded.
# 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?
**  This packaging structure should provide the flexibility to engage Hibernate at the Embedded
Tomee or with in the ODE war.
# Slf4j Logging configuration? Tomee uses SLF4J with jdk implementation and ODE uses Log4j2
implementation.
** Logging configurations is being provided at the embedded container level. 
# We need to externalize conf , embedded derby database and process deployment folders.
** A separate conf folder holding configurations for the embedded TOMEE is provided. Derby
database containing OpenJPA and HIbernate Schema are provided. Process deployment folder can
be externalized with the system property setting which is already available with ODE. Default
would be the usual WEB-INF/processes under the ODE web application.
# 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.
** The default is configured as External datasource pointing to embedded derbyjpa. This is
only for demo purposes and customers need to configure to other databases of their choice
for realtime usage by adding the relevant drivers jars to embeeded tomee and configuring the
datasources in tomee.xml.
# User should be able to change the axis2.xml, hence where do we place axis2.xml and Axis2
kernel to load it?
** There is no change in the location of the axis2.xml. It will remain within ODE web application.


was (Author: sathwik):
Created a experimental git branch https://github.com/apache/ode/tree/ODE-1060 with couple
of initial commits.

# Tomee 1.7.4 (JEE 6 certified) or 7.0.1 (JEE 7 not yet certified)?
** Went ahead with Tomee 7.0.1 as it has good support to deploy a jar as a webapp (deployClasspathAsWebApp).
# Packaging of ODE web application within apache-ode-tomee-uber.jar? What options are available?
** The packaging will be a zip file which will contain tomee libraries and ode war. Tomee
will be started in embedded mode and will deploy the embedded ODE war. The datasource used
will be derby database. This kind of packaging helps in resolving library conflicts that may
arise in future. Hibernate is the preferred JPA for deployment, It gives the flexibility to
engage Hibernate at the Embedded Tomee or with in the ODE war. This will also help in deploying
customer specific implementation for custom XPATH functions and ODE event listeners.
# apache-ode-tomee-uber.jar might have to be built without JaxRS,JaxWS,JSF dependencies of
Tomee?
** As indicated the packaging will be a zip archive and embedded tomee has JaxRS,CXF and JSF
excluded.
# 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?
**  This packaging structure should provide the flexibility to engage Hibernate at the Embedded
Tomee or with in the ODE war.
# Slf4j Logging configuration? Tomee uses SLF4J with jdk implementation and ODE uses Log4j2
implementation.
** Logging configurations is being provided at the embedded container level. 
# We need to externalize conf , embedded derby database and process deployment folders.
** A separate conf folder holding configurations for the embedded TOMEE is provided. Derby
database containing OpenJPA and HIbernate Schema are provided. Process deployment folder can
be externalized with the system property setting which is already available with ODE. Default
would be the usual WEB-INF/processes under the ODE web application.
# 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.
** The default is configured as External datasource pointing to embedded derbyjpa. This is
only for demo purposes and customers need to configure to other databases of their choice
for realtime usage by adding the relevant drivers jars to embeeded tomee and configuring the
datasources in tomee.xml.
# User should be able to change the axis2.xml, hence where do we place axis2.xml and Axis2
kernel to load it?
** There is no change in the location of the axis2.xml. It will remain within ODE web application.

> 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