[SCOUT-114] Table J3_TMODEL_INSTANCE_INFO - Column INSTANCE_PARMS getting persisted with NULL in DB2

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.2
• Fix Version/s: 1.2.4
• Component/s: Scout Implementation
• Labels: scout
• Environment: Websphere App Server + DB2
• Assignee: Thomas Cunningham
• Reporter: Ashley
• Created: 20/Jun/11 12:05
• Updated: 22/Jan/12 16:00
• Resolved: 20/Jan/12 22:42

Description

Hi,

Basically we are trying to persist WSDL info (like WSDL Location/Complex Types etc) into JUDDI.
Hence we call blm.saveServices(services).

1. Within this ...we create a Cocept (TModel), set a classification (eg. "uddi-org:types") to it.
2. create service and servicebinding.
3. create a SpecificationLink (TMODEL_INSTANCE_INFO pertains to SpecificationLink.)
4. Set a an External link to the SpecificationLink;
5. And finally associate the SpecificationLink to the service binding.

This causes an insertion of row in TMODEL_INSTANCE_INFO with the concept key and the service binding key with the Column INSTANCE_PARMS set to NULL.
Also a row in J3_OVERVIEW_DOC with ENTITY_KEY = (New Tmodel Key ) , OVERVIEW_URL = (location of my WSDL) and TMODEL_INSTANCE_INFO = (BLANK)

Now....on trying to find services (bqm.findServices)
I Iterate services, its bindings, and finally the spec links of the bindings.
Now This Spec Link fails to load due to the NULL field of INSTANCE_PARMS .
If I change the value of INSTANCE_PARMS to blank, the spec links load perfectly.

Can you initialize INSTANCE_PARMS to BLANK, instead of NULL? Also if thats not possible can you let me know to to set INSTANCE_PARMS to any value?
Have been unable to persist a value in INSTANCE_PARMS......Thank you.