[
https://issues.apache.org/jira/browse/JUDDI-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15085185#comment-15085185
]
Matthieu Ghilain commented on JUDDI-949:
----------------------------------------
I could try to provide one but I didn't not open a ticket for everything I have
done on JUDDI on my forked branch.
I am thinking about how I can provide you the changes I have performed on
JUDDI. Probably the easiest way would be for you to go through my changes and
to merge them with your current version. I didnt modify any feature of JUDDI
only added stuff to make it work with Oracle/Weblogic/Toplink.
I also created a specific module to run the tck as part of maven build.
> Make JUDDI compatible with WebLogic and Oracle database
> -------------------------------------------------------
>
> Key: JUDDI-949
> URL: https://issues.apache.org/jira/browse/JUDDI-949
> Project: jUDDI
> Issue Type: Improvement
> Components: juddi-tomcat
> Affects Versions: 3.3.2
> Reporter: Matthieu Ghilain
> Priority: Minor
>
> At the moment JUDDI is not compatible with Oracle database and WebLogic.
> The following things are probably necessary:
> - Creation of a weblogic.xml file
> - Creation of a specific orm.xml file to make it compatible with Oracle
> - Custom web.xml
> - *Adjustment to code (problem with JAXB)*
> - *Fix in some jsp*
> - Custom persistence.xml
> - Creation of a custom build profile in pom.xml
> The things in bold might have an impact on other deployment environment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
