| Summary: | SOA-P server does not define TModel in SOA Software's registry if none exists | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 4 | Reporter: | Jiri Pechanec <jpechane> | ||||
| Component: | JBossESB | Assignee: | tcunning | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 4.3 IR4 | ||||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.3 CP01 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/SOA-818 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2009-03-19 19:45:19 UTC | Type: | Task | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Jiri Pechanec
2008-09-23 12:48:29 UTC
Link: Added: This issue is related to JBQA-1587 Link: Added: This issue is related to SOA-632 Attachment: Added: jbossesb-properties.xml The stacktrace would suggest that the database has not been initialised correctly, specifically that the classification scheme cannot be located.
From the scout code
public void setClassificationScheme(ClassificationScheme cscheme)
throws JAXRException
{
scheme = cscheme;
/*
* not 100% clear, but I *think* the JavaDoc indicates that if
* our internality dictates that of the scheme.
*/
103: ((ClassificationSchemeImpl) scheme).setExternal(isExternal());
}
So scheme must be null.
public Classification createClassification(ClassificationScheme scheme,
InternationalString name,
String value) throws JAXRException {
Classification cl = (Classification) this.createObject(LifeCycleManager.CLASSIFICATION);
198: cl.setClassificationScheme(scheme);
cl.setName(name);
cl.setValue(value);
((ClassificationImpl) cl).setExternal(true);
return cl;
}
public Classification createClassification(ClassificationScheme scheme,
String name, String value)
throws JAXRException {
210: return createClassification(scheme, this.createInternationalString(name), value);
}
So this value of scheme has come from the JAXRegistryImpl
ClassificationScheme cScheme = bqm.findClassificationSchemeByName(findQualifiers, "org.jboss.soa.esb.:category");
Collection<Classification> classifications = new ArrayList<Classification>();
425: Classification classification =
blm.createClassification(
cScheme,
"category", category );
So the scheme is obtained from scout/jUDDI and would appear to be null.
Does this classification exist in the jUDDI database? If not, why not?
The above questions are really targeted at the SOA Software configuration and not jUDDI. How is this classification created in the UDDI directory? Is the ESB supposed to create it at startup time? Do we need to setup categories, etc in SOA Software before starting up the ESB. Similar to how the jUDDI database is initialized? When running against jUDDI it is populated using the import.sql script under jbossesb.sar/juddi-sql. This would be executed, along with the creation script, if it is detected that the tables do not exist. Tom Cunningham says that SOA Software have similar scripts so I have asked him to check if they are initialising our data. Ideally we should be handling this but it doesn't look like we are at present. We need to do the following: In SOA Software's GUI, go to Configure -> tModel Add a new tModel with "org.jboss.soa.esb.:category" for both Name and Description. Do not add a Key, or either of the Overview Document fields. This gets us past the error above. dev76 (the machine that is being used for this test) still needs to be patched to SM 5.2 v1.1 for this to be a valid test - it contains fixes that we need. Tom, is there any way that this can be handled automatically? Link: Added: This issue depends JBESB-2072 Logged JBESB-2072 for Kevin's suggestion. dev76 is now working - Len installed the SM5.2 v1.1 patch. Add ClassificationScheme if none exists. Link: Added: This issue is duplicated by SOA-1070 Steps to verify: If you don't a TModel in SOA Software's registry, it'll create one for you automatically Re-set-up SOA Software, run through the SOA Software Integration guide and see if it works Verified with 4.3 CP01 CR4 |