You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@juddi.apache.org by "Jeff Faath (JIRA)" <ju...@ws.apache.org> on 2009/05/20 00:03:45 UTC

[jira] Resolved: (JUDDI-232) root_BusinessEntity.xml should not be in WAR

     [ https://issues.apache.org/jira/browse/JUDDI-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Faath resolved JUDDI-232.
------------------------------

    Resolution: Fixed

This should be done.  The install process will be triggered internally...pretty much the first time a method is called.  The process will first look for the files in "juddi_custom_install_data" (in the classpath) and if not found, then use the standard "juddi_install_data" package.  The install process can no longer be triggered manually.

> root_BusinessEntity.xml should not be in WAR
> --------------------------------------------
>
>                 Key: JUDDI-232
>                 URL: https://issues.apache.org/jira/browse/JUDDI-232
>             Project: jUDDI
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.0alpha
>            Reporter: Tom Cunningham
>            Assignee: Jeff Faath
>             Fix For: 3.0beta
>
>
> Currently, both juddi-axis and juddi-cxf have a copy of root_BusinessEntity.xml.      We should make sure that it is in the JAR and loaded from the JAR rather than keeping copies of this in both WAR setups.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.