Hide Forgot
Date of First Response: 2010-02-22 09:17:41 Workaround: Workaround Exists Workaround Description: Just copy the XML files to "juddi_custom_install_data" dir and restart the server so jUDDI can pickup the new tModels. project_key: SOA This issue may be seen when using jUDDI sample tModels (marketing_tModels.xml and sales_tModel.xml). This issue depends on https://issues.apache.org/jira/browse/JUDDI-366.
Workaround Description: Added: Just copy the XML files to "juddi_custom_install_data" dir. Workaround: Added: [Workaround Exists]
Workaround Description: Removed: Just copy the XML files to "juddi_custom_install_data" dir. Added: Just copy the XML files to "juddi_custom_install_data" dir and restart the server so jUDDI can pickup the new tModels.
Talked to Marek - this is working according to the UDDI v3 spec (section 8.2.2.1). We've agreed to close the corresponding JUDDI bug related to this issue (JUDDI-366: https://issues.apache.org/jira/browse/JUDDI-366). This one can be closed too.