You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Ashley (JIRA)" <sc...@ws.apache.org> on 2011/06/20 14:05:47 UTC
[jira] [Created] (SCOUT-114) Table J3_TMODEL_INSTANCE_INFO - Column
INSTANCE_PARMS getting persisted with NULL in DB2
Table J3_TMODEL_INSTANCE_INFO - Column INSTANCE_PARMS getting persisted with NULL in DB2
----------------------------------------------------------------------------------------
Key: SCOUT-114
URL: https://issues.apache.org/jira/browse/SCOUT-114
Project: Scout
Issue Type: Bug
Components: Scout Implementation
Affects Versions: 1.2.2
Environment: Websphere App Server + DB2
Reporter: Ashley
Assignee: Kurt T Stam
Fix For: 1.2.3
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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SCOUT-114) Table J3_TMODEL_INSTANCE_INFO -
Column INSTANCE_PARMS getting persisted with NULL in DB2
Posted by "Ashley (JIRA)" <sc...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/SCOUT-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13052126#comment-13052126 ]
Ashley commented on SCOUT-114:
------------------------------
To be more precise Line 422 of ScoutUDDIV3Helper info.getInstanceDetails() results in a NULL, even though Line 424 idetails.getOverviewDoc() has content....
> Table J3_TMODEL_INSTANCE_INFO - Column INSTANCE_PARMS getting persisted with NULL in DB2
> ----------------------------------------------------------------------------------------
>
> Key: SCOUT-114
> URL: https://issues.apache.org/jira/browse/SCOUT-114
> Project: Scout
> Issue Type: Bug
> Components: Scout Implementation
> Affects Versions: 1.2.2
> Environment: Websphere App Server + DB2
> Reporter: Ashley
> Assignee: Kurt T Stam
> Labels: scout
> Fix For: 1.2.3
>
>
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SCOUT-114) Table J3_TMODEL_INSTANCE_INFO -
Column INSTANCE_PARMS getting persisted with NULL in DB2
Posted by "Tom Cunningham (Commented) (JIRA)" <sc...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/SCOUT-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190175#comment-13190175 ]
Tom Cunningham commented on SCOUT-114:
--------------------------------------
I'm putting in a change to getBindingTemplateFromJAXRSB that I think will fix this. According to the doc, TModelInstanceInfo.instanceDetails.instanceParams should be equivalent to SpecificationLink.getUsageParameters(). I don't see anywhere in scout where we map those two. This should allow you to setUsageParameters and get a value for INSTANCE_PARMS.
> Table J3_TMODEL_INSTANCE_INFO - Column INSTANCE_PARMS getting persisted with NULL in DB2
> ----------------------------------------------------------------------------------------
>
> Key: SCOUT-114
> URL: https://issues.apache.org/jira/browse/SCOUT-114
> Project: Scout
> Issue Type: Bug
> Components: Scout Implementation
> Affects Versions: 1.2.2
> Environment: Websphere App Server + DB2
> Reporter: Ashley
> Assignee: Kurt T Stam
> Labels: scout
> Fix For: 1.2.4
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (SCOUT-114) Table J3_TMODEL_INSTANCE_INFO - Column
INSTANCE_PARMS getting persisted with NULL in DB2
Posted by "Kurt T Stam (Closed) (JIRA)" <sc...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/SCOUT-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt T Stam closed SCOUT-114.
-----------------------------
> Table J3_TMODEL_INSTANCE_INFO - Column INSTANCE_PARMS getting persisted with NULL in DB2
> ----------------------------------------------------------------------------------------
>
> Key: SCOUT-114
> URL: https://issues.apache.org/jira/browse/SCOUT-114
> Project: Scout
> Issue Type: Bug
> Components: Scout Implementation
> Affects Versions: 1.2.2
> Environment: Websphere App Server + DB2
> Reporter: Ashley
> Assignee: Tom Cunningham
> Labels: scout
> Fix For: 1.2.4
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SCOUT-114) Table J3_TMODEL_INSTANCE_INFO -
Column INSTANCE_PARMS getting persisted with NULL in DB2
Posted by "Tom Cunningham (Resolved) (JIRA)" <sc...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/SCOUT-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Cunningham resolved SCOUT-114.
----------------------------------
Resolution: Fixed
Assignee: Tom Cunningham (was: Kurt T Stam)
> Table J3_TMODEL_INSTANCE_INFO - Column INSTANCE_PARMS getting persisted with NULL in DB2
> ----------------------------------------------------------------------------------------
>
> Key: SCOUT-114
> URL: https://issues.apache.org/jira/browse/SCOUT-114
> Project: Scout
> Issue Type: Bug
> Components: Scout Implementation
> Affects Versions: 1.2.2
> Environment: Websphere App Server + DB2
> Reporter: Ashley
> Assignee: Tom Cunningham
> Labels: scout
> Fix For: 1.2.4
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira