Re: [VOTE] jUDDI v3.3.9

[Kurt Stam]

+1 from me! —Kurt

On Aug 15, 2020, at 15:48, Steve Viens  wrote:


+1 from me!

Steve Viens
svi...@gmail.com
603-828-2397


On Sat, Aug 15, 2020 at 9:39 AM Alex O'Ree  wrote:

> Dear jUDDI enthusiasts,
>
> The new release is here! This release resolves 11 JIRAs, 3 enhancements
> and the rest bugs. I did update the release notes in the distro, however I
> had incorrectly labeled some of the JIRA as being fixed in the previous
> version so it's missing a few issues. It's corrected in JIRA now
>
> The release distribution is temporarily available here
> https://www.dropbox.com/sh/k2ojoye8y2916bf/AACRJoqqI5X4zlTKBlhASjCma?dl=0
>
> The release artifacts are staged in nexus:
> https://repository.apache.org/content/repositories/orgapachejuddi-1019
>
> and we have a tag at:
>
> https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=refs/tags/juddi-3.3.9
>
> Please give it a spin and cast your vote. This vote will be open for
> the next 72 hours per the release policy, which is:
> - the vote will be closed as soon as 6 hours have past and  >7 +1
> votes are received with no -1 vote being cast, or
>  - if after 12h >5 +1 votes have been cast with no -1 vote, or
>  - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing
> that
>  - after 72h provided at least 3 +1 votes have been cast and there is
> a majority of +1 votes from the cast votes.
>
> +1 for me
>
> Bug
>
>- [JUDDI-1004 ] -
>JUDDI-3.3.7 With SQL Server Database Gives Primary Key Violation For Table
>j3_category_bag
>- [JUDDI-1006 ] -
>Saving an Access Point Type
>- [JUDDI-1008 ] -
>find_business returns an error when querying a tModel when using the v2
>Inquire API
>- [JUDDI-1009 ] -
>Browse Businesses using juddiv2 page navigation issue
>- [JUDDI-1010 ] -
>save_business does not properly save the accessPoint URLType when using the
>v2 Publish API
>- [JUDDI-1011 ] - MS
>SQL Server table - length of field too large
>- [JUDDI-1013 ] -
>GUI adding records
>- [JUDDI-1015 ] -
>Oracle database start up issue due to max string length
>
> Improvement
>
>- [JUDDI-1012 ] - MS
>SQL Server Sequence table change
>- [JUDDI-1014 ] -
>Binding Editor – tModel Instance Information
>- [JUDDI-1016 ] -
>Add DDL generators for all available hibernate supported dialetcs
>
>

Re: [VOTE] jUDDI v3.3.9

[Steve Viens]

+1 from me!

Steve Viens
svi...@gmail.com
603-828-2397


On Sat, Aug 15, 2020 at 9:39 AM Alex O'Ree  wrote:

> Dear jUDDI enthusiasts,
>
> The new release is here! This release resolves 11 JIRAs, 3 enhancements
> and the rest bugs. I did update the release notes in the distro, however I
> had incorrectly labeled some of the JIRA as being fixed in the previous
> version so it's missing a few issues. It's corrected in JIRA now
>
> The release distribution is temporarily available here
> https://www.dropbox.com/sh/k2ojoye8y2916bf/AACRJoqqI5X4zlTKBlhASjCma?dl=0
>
> The release artifacts are staged in nexus:
> https://repository.apache.org/content/repositories/orgapachejuddi-1019
>
> and we have a tag at:
>
> https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=refs/tags/juddi-3.3.9
>
> Please give it a spin and cast your vote. This vote will be open for
> the next 72 hours per the release policy, which is:
> - the vote will be closed as soon as 6 hours have past and  >7 +1
> votes are received with no -1 vote being cast, or
>  - if after 12h >5 +1 votes have been cast with no -1 vote, or
>  - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing
> that
>  - after 72h provided at least 3 +1 votes have been cast and there is
> a majority of +1 votes from the cast votes.
>
> +1 for me
>
> Bug
>
>- [JUDDI-1004 ] -
>JUDDI-3.3.7 With SQL Server Database Gives Primary Key Violation For Table
>j3_category_bag
>- [JUDDI-1006 ] -
>Saving an Access Point Type
>- [JUDDI-1008 ] -
>find_business returns an error when querying a tModel when using the v2
>Inquire API
>- [JUDDI-1009 ] -
>Browse Businesses using juddiv2 page navigation issue
>- [JUDDI-1010 ] -
>save_business does not properly save the accessPoint URLType when using the
>v2 Publish API
>- [JUDDI-1011 ] - MS
>SQL Server table - length of field too large
>- [JUDDI-1013 ] -
>GUI adding records
>- [JUDDI-1015 ] -
>Oracle database start up issue due to max string length
>
> Improvement
>
>- [JUDDI-1012 ] - MS
>SQL Server Sequence table change
>- [JUDDI-1014 ] -
>Binding Editor – tModel Instance Information
>- [JUDDI-1016 ] -
>Add DDL generators for all available hibernate supported dialetcs
>
>

[VOTE] jUDDI v3.3.9

[Alex O'Ree]

Dear jUDDI enthusiasts,

The new release is here! This release resolves 11 JIRAs, 3 enhancements and
the rest bugs. I did update the release notes in the distro, however I had
incorrectly labeled some of the JIRA as being fixed in the previous version
so it's missing a few issues. It's corrected in JIRA now

The release distribution is temporarily available here
https://www.dropbox.com/sh/k2ojoye8y2916bf/AACRJoqqI5X4zlTKBlhASjCma?dl=0

The release artifacts are staged in nexus:
https://repository.apache.org/content/repositories/orgapachejuddi-1019

and we have a tag at:
https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=refs/tags/juddi-3.3.9

Please give it a spin and cast your vote. This vote will be open for
the next 72 hours per the release policy, which is:
- the vote will be closed as soon as 6 hours have past and  >7 +1
votes are received with no -1 vote being cast, or
 - if after 12h >5 +1 votes have been cast with no -1 vote, or
 - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing
that
 - after 72h provided at least 3 +1 votes have been cast and there is
a majority of +1 votes from the cast votes.

+1 for me

Bug

   - [JUDDI-1004 ] -
   JUDDI-3.3.7 With SQL Server Database Gives Primary Key Violation For Table
   j3_category_bag
   - [JUDDI-1006 ] -
   Saving an Access Point Type
   - [JUDDI-1008 ] -
   find_business returns an error when querying a tModel when using the v2
   Inquire API
   - [JUDDI-1009 ] -
   Browse Businesses using juddiv2 page navigation issue
   - [JUDDI-1010 ] -
   save_business does not properly save the accessPoint URLType when using the
   v2 Publish API
   - [JUDDI-1011 ] - MS
   SQL Server table - length of field too large
   - [JUDDI-1013 ] - GUI
   adding records
   - [JUDDI-1015 ] -
   Oracle database start up issue due to max string length

Improvement

   - [JUDDI-1012 ] - MS
   SQL Server Sequence table change
   - [JUDDI-1014 ] -
   Binding Editor – tModel Instance Information
   - [JUDDI-1016 ] - Add
   DDL generators for all available hibernate supported dialetcs

[jira] [Updated] (JUDDI-1013) GUI adding records

[Alex O'Ree (Jira)]

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

Alex O'Ree updated JUDDI-1013:
--
Fix Version/s: 3.3.9

> GUI adding records
> --
>
> Key: JUDDI-1013
> URL: https://issues.apache.org/jira/browse/JUDDI-1013
> Project: jUDDI
>  Issue Type: Bug
>  Components: juddi-gui
>Affects Versions: 3.3.7
>Reporter: Steve Luisser
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.9
>
>
> Create a business and save it.  Navigate to the Services to add a service.  
> You see the message “Please save the business first, then you can add 
> services.”  You need to open the business again before you can add a service. 
>  This behavior occurs at multiple levels as you go deeper into the business 
> definition.  It does not seem like the page is refreshing to know that the 
> data has been saved.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (JUDDI-1013) GUI adding records

[Alex O'Ree (Jira)]

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

Alex O'Ree updated JUDDI-1013:
--
Fix Version/s: (was: 3.3.8)

> GUI adding records
> --
>
> Key: JUDDI-1013
> URL: https://issues.apache.org/jira/browse/JUDDI-1013
> Project: jUDDI
>  Issue Type: Bug
>  Components: juddi-gui
>Affects Versions: 3.3.7
>Reporter: Steve Luisser
>Assignee: Alex O'Ree
>Priority: Major
>
> Create a business and save it.  Navigate to the Services to add a service.  
> You see the message “Please save the business first, then you can add 
> services.”  You need to open the business again before you can add a service. 
>  This behavior occurs at multiple levels as you go deeper into the business 
> definition.  It does not seem like the page is refreshing to know that the 
> data has been saved.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (JUDDI-1012) MS SQL Server Sequence table change

[Alex O'Ree (Jira)]

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

Alex O'Ree updated JUDDI-1012:
--
Fix Version/s: (was: 3.3.8)
   3.3.9

> MS SQL Server Sequence table change
> ---
>
> Key: JUDDI-1012
> URL: https://issues.apache.org/jira/browse/JUDDI-1012
> Project: jUDDI
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 3.3.7
>Reporter: Steve Luisser
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.9
>
>
> SQL Server 2012 is the oldest version that is supported by Microsoft.  This 
> and newer versions support sequences.
>  
> File mssql2000.ddl:
>  
> create table hibernate_sequence (next_val numeric(19,0));
> Multiple instances of insert into hibernate_sequence values ( 1 );
>  
> Suggestion to change this to:
> create sequence hibernate_sequence start with 1 increment by 1;
>  
> To remove the sequence use: DROP sequence hibernate_sequence;



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (JUDDI-1009) Browse Businesses using juddiv2 page navigation issue

[Alex O'Ree (Jira)]

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

Alex O'Ree updated JUDDI-1009:
--
Fix Version/s: (was: 3.3.8)
   3.3.9

> Browse Businesses using juddiv2 page navigation issue
> -
>
> Key: JUDDI-1009
> URL: https://issues.apache.org/jira/browse/JUDDI-1009
> Project: jUDDI
>  Issue Type: Bug
>  Components: juddi-gui
>Affects Versions: 3.3.7
>Reporter: Steve Luisser
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.9
>
> Attachments: Business List v2.png
>
>
> Browse Businesses using the default (v3) works properly.  Total records shows 
> 473 businesses.  Paging through the records with the right arrow button 
> properly moves you to the next set of 20 businesses.  
>  
> Select juddiv2 as the active configuration.  Browse Businesses.  Total 
> records shows 20 businesses.  Paging trough the records lets you go 1 page 
> forward showing an offset of 20.  The records displayed are the same 20 on 
> the first page with offset 0.
>  
> This issue is present for Services and tModels.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (JUDDI-1008) find_business returns an error when querying a tModel when using the v2 Inquire API

[Alex O'Ree (Jira)]

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

Alex O'Ree updated JUDDI-1008:
--
Fix Version/s: (was: 3.3.8)
   3.3.9

> find_business returns an error when querying a tModel when using the v2 
> Inquire API
> ---
>
> Key: JUDDI-1008
> URL: https://issues.apache.org/jira/browse/JUDDI-1008
> Project: jUDDI
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.7
>Reporter: Steve Luisser
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.9
>
>
> The v2 Inquire API find_business returns an error when querying for a tModel. 
>  The v3 call gives a valid response.
> V2 Request
> 
> http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>   
>     
>   
>      keyName="DUNS" keyValue="12-345-6781" />
>   
>     
>   
> 
>  
> V2 Response
> http://schemas.xmlsoap.org/soap/envelope/";>
>   
>     
>   soap:Server
>   At least one search criterion must be supplied. Try using 
> '%' as a wild card with the a 'approximateMatch' find qualifer for 
> everything
>   
>      operator="uddi:juddi.apache.org:node1" truncated="false">
>   
>     A serious technical error has 
> occurred while processing the request.
>   
>     
>   
>     
>   
> 
>  
> V3 Request
> 
> http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>   
>     
>   
>      keyName="DUNS" keyValue="12-345-6781" />
>   
>     
>   
> 
>  
> V3 Response
> http://schemas.xmlsoap.org/soap/envelope/";>
>   
>      xmlns:ns10="urn:uddi-org:vs_v3" xmlns:ns9="urn:uddi-org:repl_v3" 
> xmlns:ns8="urn:uddi-org:policy_v3" xmlns:ns7="urn:uddi-org:custody_v3" 
> xmlns:ns6="urn:uddi-org:subr_v3" xmlns:ns5="urn:uddi-org:sub_v3" 
> xmlns:ns4="urn:uddi-org:vscache_v3" 
> xmlns:ns3="http://www.w3.org/2000/09/xmldsig#"; 
> xmlns:ns2="urn:uddi-org:api_v3" truncated="false">
>   
>     1
>     1
>     1
>   
>   
>      businessKey="uddi:juddi.apache.org:0a528283-47f9-4bf8-b29c-1c1e0338fe28">
>   Test Provider
>   
>      serviceKey="uddi:juddi.apache.org:249f327a-68bd-4cd7-b358-c0347369e573" 
> businessKey="uddi:juddi.apache.org:0a528283-47f9-4bf8-b29c-1c1e0338fe28">
>   Test Service
>     
>   
>     
>   
>     
>   
> 
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (JUDDI-1010) save_business does not properly save the accessPoint URLType when using the v2 Publish API

[Alex O'Ree (Jira)]

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

Alex O'Ree updated JUDDI-1010:
--
Fix Version/s: (was: 3.3.8)
   3.3.9

> save_business does not properly save the accessPoint URLType when using the 
> v2 Publish API
> --
>
> Key: JUDDI-1010
> URL: https://issues.apache.org/jira/browse/JUDDI-1010
> Project: jUDDI
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.3.7
>Reporter: Steve Luisser
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.9
>
>
> The v2 Publish API – save_business does not save the values passed in for the 
> accessPoint URLType in the database, endpoint is always put in the DB.  The 
> response from the v2 call includes the proper values for the accessPoint 
> URLType.  The v3 call saves the accessPoint URLType properly.  Note the value 
> for the authtoken was changed in the example XML.
>  
> V2 Request
> 
> http://schemas.xmlsoap.org/soap/envelope/"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
>   
>     
>   authtoken:ZZZ
>   
>     Test Provider
>     
>   
>     Test Service
>     
>   
>      URLType="http">http://somedomain.com/testservice.svc
>     
>    tModelKey="uuid:ee846ebf-ef30-4e73-8558-0eba166d002a" />
>     
>   
>   
>      URLType="mailto">mailto:t...@domain.com
>     
>    tModelKey="uuid:f05b5947-8831-4c6a-9aa3-009ce5e6a707" />
>     
>   
>     
>   
>     
>     
>    tModelKey="uuid:578a72bd-8f35-4099-b559-8b4997389bc5" keyName="DUNS" 
> keyValue="12-345-6781" />
>     
>   
>     
>   
> 
>  
> V2 Response
> http://schemas.xmlsoap.org/soap/envelope/";>
>   
>      operator="uddi:juddi.apache.org:node1" truncated="false">
>    operator="uddi:juddi.apache.org:node1">
>     Test Provider
>     
>    serviceKey="uddi:juddi.apache.org:99a4c6f6-c7f9-4536-a810-73c60f605a97">
>     Test Service
>     
>    bindingKey="uddi:juddi.apache.org:2c3da830-751a-4304-8da4-006dd0d0007e">
>      URLType="http">http://somedomain.com/testservice.svc
>     
>    tModelKey="uuid:ee846ebf-ef30-4e73-8558-0eba166d002a"/>
>     
>   
>    bindingKey="uddi:juddi.apache.org:c859a269-fefb-4f32-9047-e3de41b36900">
>      URLType="mailto">mailto:t...@domain.com
>     
>    tModelKey="uuid:f05b5947-8831-4c6a-9aa3-009ce5e6a707"/>
>     
>   
>     
>   
>     
>     
>    tModelKey="uuid:578a72bd-8f35-4099-b559-8b4997389bc5" keyName="DUNS" 
> keyValue="12-345-6781"/>
>     
>   
>     
>   
> 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (JUDDI-1004) JUDDI-3.3.7 With SQL Server Database Gives Primary Key Violation For Table j3_category_bag

[Alex O'Ree (Jira)]

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

Alex O'Ree updated JUDDI-1004:
--
Fix Version/s: (was: 3.3.8)
   3.3.9

> JUDDI-3.3.7 With SQL Server Database Gives Primary Key Violation For Table 
> j3_category_bag 
> ---
>
> Key: JUDDI-1004
> URL: https://issues.apache.org/jira/browse/JUDDI-1004
> Project: jUDDI
>  Issue Type: Bug
>  Components: core, juddi-tomcat
>Affects Versions: 3.3.7
>Reporter: Amol Bhonsle
>Priority: Major
>  Labels: jUDDI, juddi
> Fix For: 3.3.9
>
>
> Our application is based on JUDDI-3.3.7 When we try to publishService() we 
> get following Exception: 
>  
>  
> Caused by:  
> org.apache.openjpa.persistence.RollbackException: The transaction has been 
> rolled back.  See the nested exceptions for details on the errors that 
> occurred.
> FailedObject: 
> [org.apache.juddi.model.ServiceCategoryBag@2a6330e7|mailto:org.apache.juddi.model.ServiceCategoryBag@2a6330e7]
>     at 
> org.apache.openjpa.persistence.EntityManagerImpl.commit(EntityManagerImpl.java:594)
>     at 
> org.apache.juddi.api.impl.UDDIPublicationImpl.saveService(UDDIPublicationImpl.java:892)
>     at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>     at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>     at java.base/java.lang.reflect.Method.invoke(Method.java:566)
>     at 
> org.apache.cxf.service.invoker.AbstractInvoker.performInvocation(AbstractInvoker.java:179)
>     at 
> org.apache.cxf.jaxws.JAXWSMethodInvoker.performInvocation(JAXWSMethodInvoker.java:66)
>     at 
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker.java:96)
>     ... 42 more
> Caused by:  
> org.apache.openjpa.persistence.PersistenceException: The transaction has been 
> rolled back.  See the nested exceptions for details on the errors that 
> occurred.
> FailedObject: 
> [org.apache.juddi.model.ServiceCategoryBag@2a6330e7|mailto:org.apache.juddi.model.ServiceCategoryBag@2a6330e7]
>     at 
> org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2370)
>     at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2207)
>     at 
> org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:2105)
>     at 
> org.apache.openjpa.kernel.BrokerImpl.beforeCompletion(BrokerImpl.java:2023)
>     at 
> org.apache.openjpa.kernel.LocalManagedRuntime.commit(LocalManagedRuntime.java:81)
>     at org.apache.openjpa.kernel.BrokerImpl.commit(BrokerImpl.java:1528)
>     at 
> org.apache.openjpa.kernel.DelegatingBroker.commit(DelegatingBroker.java:933)
>     at 
> org.apache.openjpa.persistence.EntityManagerImpl.commit(EntityManagerImpl.java:570)
>     ... 50 more
> Caused by:  
> org.apache.openjpa.persistence.EntityExistsException: Violation of PRIMARY 
> KEY constraint 'PK__j3_categ__3213E83FD3C84046'. Cannot insert duplicate key 
> in object 'dbo.j3_category_bag'. The duplicate key value is (902). {prepstmnt 
> 1928491676 INSERT INTO j3_category_bag (id) VALUES (?)} [code=2627, 
> state=23000]
> FailedObject: 
> [org.apache.juddi.model.ServiceCategoryBag@2a6330e7|mailto:org.apache.juddi.model.ServiceCategoryBag@2a6330e7]
>     at 
> org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4959)
>     at 
> org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4934)
>     at 
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:134)
>     at 
> org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:76)
>     at 
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:144)
>     at 
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:100)
>     at 
> org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:88)
>     at 
> org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flushPrimaryRow(OperationOrderUpdateManager.java:203)
>     at 
> org.apache.openjpa.jdbc.kernel.OperationOrderUpdateManager.flush(OperationOrderUpdateManager.java:89)
>     at 
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:104)
>     at 
> org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:77)
>     at 
> org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:732)
> 

[jira] [Updated] (JUDDI-1014) Binding Editor – tModel Instance Information

[Alex O'Ree (Jira)]

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

Alex O'Ree updated JUDDI-1014:
--
Fix Version/s: (was: 3.3.8)
   3.3.9

> Binding Editor – tModel Instance Information
> 
>
> Key: JUDDI-1014
> URL: https://issues.apache.org/jira/browse/JUDDI-1014
> Project: jUDDI
>  Issue Type: Improvement
>  Components: juddi-gui
>Affects Versions: 3.3.7
>Reporter: Steve Luisser
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.9
>
> Attachments: tModel Instance Info.png
>
>
> It would be nice to display the tModel Name as you most likely will not know 
> what each tModel the GUID is for.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)