[jira] [Commented] (JUDDI-1020) Use an alternate documentation mechanism than the jboss docbook plugin
[ https://issues.apache.org/jira/browse/JUDDI-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609238#comment-17609238 ] ASF subversion and git services commented on JUDDI-1020: Commit 76d055283912aaad65dd1d1bac4ebc5d9f6c18e7 in juddi's branch refs/heads/feature/JUDDI-978 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=76d055283 ] JUDDI-1020 resolves all known formating and packaging issues with maven pdf plugin switch (from docbook) > Use an alternate documentation mechanism than the jboss docbook plugin > -- > > Key: JUDDI-1020 > URL: https://issues.apache.org/jira/browse/JUDDI-1020 > Project: jUDDI > Issue Type: Improvement > Components: build >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Attachments: juddi-client-guide.pdf, juddi-server-guide.pdf > > > long story short, maven frequently has issues resolving either xlts or the > docbook plugins. I think it's an issue on the jboss maven repo either > blocking too many concurrent requests or some kind of quote or bandwidth cap, > etc. Maybe we can use the maven site plugin + pdf plugins to get a near > equivalent setup or maybe there are some other alternatives out there -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JUDDI-1022) Address codeql warnings
[ https://issues.apache.org/jira/browse/JUDDI-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609164#comment-17609164 ] ASF subversion and git services commented on JUDDI-1022: Commit dd57b3707e79e8fc729346d160fd4d82c076 in juddi's branch refs/heads/feature/JUDDI-978 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=dd57b ] JUDDI-1022 deprecating DES based code > Address codeql warnings > --- > > Key: JUDDI-1022 > URL: https://issues.apache.org/jira/browse/JUDDI-1022 > Project: jUDDI > Issue Type: Improvement >Reporter: Alex O'Ree >Priority: Major > > i finally got codeql up and running at github. it found a few things that > should be addressed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JUDDI-978) Build instability with Replication tests
[ https://issues.apache.org/jira/browse/JUDDI-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609165#comment-17609165 ] ASF subversion and git services commented on JUDDI-978: --- Commit d31740d51f06344c76f44211ec5b63655316953b in juddi's branch refs/heads/feature/JUDDI-978 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=d31740d51 ] Merge branch 'master' into feature/JUDDI-978 > Build instability with Replication tests > > > Key: JUDDI-978 > URL: https://issues.apache.org/jira/browse/JUDDI-978 > Project: jUDDI > Issue Type: Bug > Components: core, uddi-tck >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.5 > > > There were some changes made between 3.3.3 and 3.3.4 which continue until > this day that may cause test instability of juddi. From what i can, the > product itself isn't affected by this, however the fact that they are failing > bother me -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JUDDI-1022) Address codeql warnings
[ https://issues.apache.org/jira/browse/JUDDI-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609163#comment-17609163 ] ASF subversion and git services commented on JUDDI-1022: Commit 3e543287542e96c24d1d6aa4839790eb43de299c in juddi's branch refs/heads/feature/JUDDI-978 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=3e5432875 ] JUDDI-1022 deprecating DES based code > Address codeql warnings > --- > > Key: JUDDI-1022 > URL: https://issues.apache.org/jira/browse/JUDDI-1022 > Project: jUDDI > Issue Type: Improvement >Reporter: Alex O'Ree >Priority: Major > > i finally got codeql up and running at github. it found a few things that > should be addressed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JUDDI-1024) Hibernate build is no longer working on CI
[ https://issues.apache.org/jira/browse/JUDDI-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17609074#comment-17609074 ] ASF subversion and git services commented on JUDDI-1024: Commit c091e365ed247db91478ebeabf40bc1f3e0f03eb in juddi's branch refs/heads/bug/JUDDI-1024 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=c091e365e ] JUDDI-1024 a possible solution, by removing hibernate support > Hibernate build is no longer working on CI > -- > > Key: JUDDI-1024 > URL: https://issues.apache.org/jira/browse/JUDDI-1024 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Kurt T Stam >Priority: Major > Attachments: juddi.log, localhost.2022-05-30.log > > > in an attempt to juddi building on github actions and get all the fancy code > scanning, dependabot stuff running, i ran into an issue with the hibernate > setup. With OpenJPA, everything is fine, however on hibernate, once the > tomcat/juddi war starts up, it throws an > java.lang.ArrayIndexOutOfBoundsException without any real context as to > what's going. > Full log output is available here: > [https://github.com/apache/juddi/runs/6479545287?check_suite_focus=true#step:6:27488] > I am unable to reproduce locally. Off of master, the command the CI job is > using is > " mvn -B install -Pgithubactiondist -Phibernate" on JDK8 > > I'll attach the logs from my system shortly -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (JUDDI-1022) Address codeql warnings
[ https://issues.apache.org/jira/browse/JUDDI-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537302#comment-17537302 ] ASF subversion and git services commented on JUDDI-1022: Commit dd57b3707e79e8fc729346d160fd4d82c076 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=dd57b ] JUDDI-1022 deprecating DES based code > Address codeql warnings > --- > > Key: JUDDI-1022 > URL: https://issues.apache.org/jira/browse/JUDDI-1022 > Project: jUDDI > Issue Type: Improvement >Reporter: Alex O'Ree >Priority: Major > > i finally got codeql up and running at github. it found a few things that > should be addressed. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (JUDDI-1022) Address codeql warnings
[ https://issues.apache.org/jira/browse/JUDDI-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537296#comment-17537296 ] ASF subversion and git services commented on JUDDI-1022: Commit 3e543287542e96c24d1d6aa4839790eb43de299c in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=3e5432875 ] JUDDI-1022 deprecating DES based code > Address codeql warnings > --- > > Key: JUDDI-1022 > URL: https://issues.apache.org/jira/browse/JUDDI-1022 > Project: jUDDI > Issue Type: Improvement >Reporter: Alex O'Ree >Priority: Major > > i finally got codeql up and running at github. it found a few things that > should be addressed. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (JUDDI-978) Build instability with Replication tests
[ https://issues.apache.org/jira/browse/JUDDI-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537295#comment-17537295 ] ASF subversion and git services commented on JUDDI-978: --- Commit eab4a7e307b904ff13b465b07162769028cc813c in juddi's branch refs/heads/test/testmerge from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=eab4a7e30 ] Merge branch 'feature/JUDDI-978' into test/testmerge resolves all ci/testing isssues > Build instability with Replication tests > > > Key: JUDDI-978 > URL: https://issues.apache.org/jira/browse/JUDDI-978 > Project: jUDDI > Issue Type: Bug > Components: core, uddi-tck >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.5 > > > There were some changes made between 3.3.3 and 3.3.4 which continue until > this day that may cause test instability of juddi. From what i can, the > product itself isn't affected by this, however the fact that they are failing > bother me -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (JUDDI-978) Build instability with Replication tests
[ https://issues.apache.org/jira/browse/JUDDI-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537214#comment-17537214 ] ASF subversion and git services commented on JUDDI-978: --- Commit b5d853881d2133a10bb140b5d7d9174d97ca5bc6 in juddi's branch refs/heads/feature/JUDDI-978 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=b5d853881 ] Merge branch 'master' into feature/JUDDI-978 > Build instability with Replication tests > > > Key: JUDDI-978 > URL: https://issues.apache.org/jira/browse/JUDDI-978 > Project: jUDDI > Issue Type: Bug > Components: core, uddi-tck >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.5 > > > There were some changes made between 3.3.3 and 3.3.4 which continue until > this day that may cause test instability of juddi. From what i can, the > product itself isn't affected by this, however the fact that they are failing > bother me -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (JUDDI-1020) Use an alternate documentation mechanism than the jboss docbook plugin
[ https://issues.apache.org/jira/browse/JUDDI-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537219#comment-17537219 ] ASF subversion and git services commented on JUDDI-1020: Commit fde14da9bde8d85aa59b1a0deb2cfc1114289ab2 in juddi's branch refs/heads/feature/JUDDI-978 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=fde14da9b ] [JUDDI-978] [JUDDI-1020] > Use an alternate documentation mechanism than the jboss docbook plugin > -- > > Key: JUDDI-1020 > URL: https://issues.apache.org/jira/browse/JUDDI-1020 > Project: jUDDI > Issue Type: Improvement > Components: build >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Attachments: juddi-client-guide.pdf, juddi-server-guide.pdf > > > long story short, maven frequently has issues resolving either xlts or the > docbook plugins. I think it's an issue on the jboss maven repo either > blocking too many concurrent requests or some kind of quote or bandwidth cap, > etc. Maybe we can use the maven site plugin + pdf plugins to get a near > equivalent setup or maybe there are some other alternatives out there -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (JUDDI-978) Build instability with Replication tests
[ https://issues.apache.org/jira/browse/JUDDI-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537217#comment-17537217 ] ASF subversion and git services commented on JUDDI-978: --- Commit fde14da9bde8d85aa59b1a0deb2cfc1114289ab2 in juddi's branch refs/heads/feature/JUDDI-978 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=fde14da9b ] [JUDDI-978] [JUDDI-1020] > Build instability with Replication tests > > > Key: JUDDI-978 > URL: https://issues.apache.org/jira/browse/JUDDI-978 > Project: jUDDI > Issue Type: Bug > Components: core, uddi-tck >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.5 > > > There were some changes made between 3.3.3 and 3.3.4 which continue until > this day that may cause test instability of juddi. From what i can, the > product itself isn't affected by this, however the fact that they are failing > bother me -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (JUDDI-978) Build instability with Replication tests
[ https://issues.apache.org/jira/browse/JUDDI-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537210#comment-17537210 ] ASF subversion and git services commented on JUDDI-978: --- Commit 25a86acaed152606a730444f57845a7afe5379dc in juddi's branch refs/heads/feature/JUDDI-978 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=25a86acae ] Merge branch 'master' into feature/JUDDI-978 # Conflicts: # docs/asciidoc/ClientGuide/pom.xml # docs/asciidoc/Guide/pom.xml # docs/asciidoc/pom.xml # pom.xml > Build instability with Replication tests > > > Key: JUDDI-978 > URL: https://issues.apache.org/jira/browse/JUDDI-978 > Project: jUDDI > Issue Type: Bug > Components: core, uddi-tck >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.5 > > > There were some changes made between 3.3.3 and 3.3.4 which continue until > this day that may cause test instability of juddi. From what i can, the > product itself isn't affected by this, however the fact that they are failing > bother me -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (JUDDI-978) Build instability with Replication tests
[ https://issues.apache.org/jira/browse/JUDDI-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537209#comment-17537209 ] ASF subversion and git services commented on JUDDI-978: --- Commit 47accac9ad450f77294bef3b25f3543bc3f7f6d2 in juddi's branch refs/heads/feature/JUDDI-978 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=47accac9a ] JUDDI-978 resolves merge issues > Build instability with Replication tests > > > Key: JUDDI-978 > URL: https://issues.apache.org/jira/browse/JUDDI-978 > Project: jUDDI > Issue Type: Bug > Components: core, uddi-tck >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.5 > > > There were some changes made between 3.3.3 and 3.3.4 which continue until > this day that may cause test instability of juddi. From what i can, the > product itself isn't affected by this, however the fact that they are failing > bother me -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (JUDDI-978) Build instability with Replication tests
[ https://issues.apache.org/jira/browse/JUDDI-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537211#comment-17537211 ] ASF subversion and git services commented on JUDDI-978: --- Commit 1ae04582fdaac4ef11351e5e01aa2d1dd03d6814 in juddi's branch refs/heads/feature/JUDDI-978 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=1ae04582f ] JUDDI-978 adds maven site (html) and pdf plugin generation to the build > Build instability with Replication tests > > > Key: JUDDI-978 > URL: https://issues.apache.org/jira/browse/JUDDI-978 > Project: jUDDI > Issue Type: Bug > Components: core, uddi-tck >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.5 > > > There were some changes made between 3.3.3 and 3.3.4 which continue until > this day that may cause test instability of juddi. From what i can, the > product itself isn't affected by this, however the fact that they are failing > bother me -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (JUDDI-978) Build instability with Replication tests
[ https://issues.apache.org/jira/browse/JUDDI-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537212#comment-17537212 ] ASF subversion and git services commented on JUDDI-978: --- Commit 578ecfdbb697f99164dcd2ff09b85320439ccaa7 in juddi's branch refs/heads/feature/JUDDI-978 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=578ecfdbb ] Merge branch 'master' into feature/JUDDI-978 > Build instability with Replication tests > > > Key: JUDDI-978 > URL: https://issues.apache.org/jira/browse/JUDDI-978 > Project: jUDDI > Issue Type: Bug > Components: core, uddi-tck >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.5 > > > There were some changes made between 3.3.3 and 3.3.4 which continue until > this day that may cause test instability of juddi. From what i can, the > product itself isn't affected by this, however the fact that they are failing > bother me -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (JUDDI-1022) Address codeql warnings
[ https://issues.apache.org/jira/browse/JUDDI-1022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17537122#comment-17537122 ] ASF subversion and git services commented on JUDDI-1022: Commit b1a72d2f64fa772102a3db6b91c54489f64d7128 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=b1a72d2f6 ] NOJIRA removing old travis config, minor pom cleanup JUDDI-1022 deprecating DES based code > Address codeql warnings > --- > > Key: JUDDI-1022 > URL: https://issues.apache.org/jira/browse/JUDDI-1022 > Project: jUDDI > Issue Type: Improvement >Reporter: Alex O'Ree >Priority: Major > > i finally got codeql up and running at github. it found a few things that > should be addressed. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (JUDDI-1021) Remove the digital signature applet
[ https://issues.apache.org/jira/browse/JUDDI-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17523429#comment-17523429 ] ASF subversion and git services commented on JUDDI-1021: Commit 36c51732ff7162b47f426a7e5e084bc76047e8a0 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=36c51732f ] JUDDI-1021 remove the digital signature applet > Remove the digital signature applet > --- > > Key: JUDDI-1021 > URL: https://issues.apache.org/jira/browse/JUDDI-1021 > Project: jUDDI > Issue Type: Improvement >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > > looks like this was removed in jdk8 at some point (it is no longer available > in 1.8.302 on ubuntu, plugin.jar is missing entirely even with icedtea > installed). It's currently deprecated and marked for removal in jdk17. See > also JUDDI-990 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (JUDDI-1016) Add DDL generators for all available hibernate supported dialetcs
[ https://issues.apache.org/jira/browse/JUDDI-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176725#comment-17176725 ] ASF subversion and git services commented on JUDDI-1016: Commit 9627e3c76d1a5354063a6d5c83dea8edac744c11 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=9627e3c ] JUDDI-1016 produces DDL for all known supported hbernate dialetcs, resolves relative path class path issues > Add DDL generators for all available hibernate supported dialetcs > - > > Key: JUDDI-1016 > URL: https://issues.apache.org/jira/browse/JUDDI-1016 > Project: jUDDI > Issue Type: Improvement >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.9 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-1016) Add DDL generators for all available hibernate supported dialetcs
[ https://issues.apache.org/jira/browse/JUDDI-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176709#comment-17176709 ] ASF subversion and git services commented on JUDDI-1016: Commit 40b402dab998c8176ecadb3f2da7e16b012c7a80 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=40b402d ] JUDDI-1016 produces DDL for all known supported hbernate dialetcs > Add DDL generators for all available hibernate supported dialetcs > - > > Key: JUDDI-1016 > URL: https://issues.apache.org/jira/browse/JUDDI-1016 > Project: jUDDI > Issue Type: Improvement >Reporter: Alex O'Ree >Priority: Major > Fix For: 3.3.9 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-1015) Oracle database start up issue due to max string length
[
https://issues.apache.org/jira/browse/JUDDI-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176687#comment-17176687
]
ASF subversion and git services commented on JUDDI-1015:
Commit 4d7bc5a3bf37e7d5341286432c129f8fb1a4b203 in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=4d7bc5a ]
JUDDI-1015 reduces sql identifiers for better support for both mssql and for
oracledb.
JUDDI-1101 related. also resolves sql query issues for discoery url due to
varchar to clob change
> Oracle database start up issue due to max string length
> ---
>
> Key: JUDDI-1015
> URL: https://issues.apache.org/jira/browse/JUDDI-1015
> Project: jUDDI
> Issue Type: Bug
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.9
>
>
> from the juddi mailing list
>
> {color:#172b4d}Oracle Version of Juddi Due to string limit for a column
> CREATE TABLE j3_binding_template (entity_key VARCHAR2(255) NOT NULL,
> access_point_type VARCHAR2(255), access_point_url VARCHAR2(4096),
> hosting_redirector VARCHAR2(255), service_key VARCHAR2(255) NOT NULL, PRIMARY
> KEY (entity_key)) {color}*Oracle max varchar limit: 4000*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-1015) Oracle database start up issue due to max string length
[
https://issues.apache.org/jira/browse/JUDDI-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176686#comment-17176686
]
ASF subversion and git services commented on JUDDI-1015:
Commit 7a26bedd92cff633d641118d19b5237ac8474105 in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=7a26bed ]
Merge branch 'master' into bug/JUDDI-1015
> Oracle database start up issue due to max string length
> ---
>
> Key: JUDDI-1015
> URL: https://issues.apache.org/jira/browse/JUDDI-1015
> Project: jUDDI
> Issue Type: Bug
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.9
>
>
> from the juddi mailing list
>
> {color:#172b4d}Oracle Version of Juddi Due to string limit for a column
> CREATE TABLE j3_binding_template (entity_key VARCHAR2(255) NOT NULL,
> access_point_type VARCHAR2(255), access_point_url VARCHAR2(4096),
> hosting_redirector VARCHAR2(255), service_key VARCHAR2(255) NOT NULL, PRIMARY
> KEY (entity_key)) {color}*Oracle max varchar limit: 4000*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-1015) Oracle database start up issue due to max string length
[
https://issues.apache.org/jira/browse/JUDDI-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176683#comment-17176683
]
ASF subversion and git services commented on JUDDI-1015:
Commit c6e69a48bfe61dde00a8ff8873bb8f946e06e4ea in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=c6e69a4 ]
JUDDI-1015 adds oracle and mssql drivers to the mix along with an example for
oracle db
> Oracle database start up issue due to max string length
> ---
>
> Key: JUDDI-1015
> URL: https://issues.apache.org/jira/browse/JUDDI-1015
> Project: jUDDI
> Issue Type: Bug
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.9
>
>
> from the juddi mailing list
>
> {color:#172b4d}Oracle Version of Juddi Due to string limit for a column
> CREATE TABLE j3_binding_template (entity_key VARCHAR2(255) NOT NULL,
> access_point_type VARCHAR2(255), access_point_url VARCHAR2(4096),
> hosting_redirector VARCHAR2(255), service_key VARCHAR2(255) NOT NULL, PRIMARY
> KEY (entity_key)) {color}*Oracle max varchar limit: 4000*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-1015) Oracle database start up issue due to max string length
[
https://issues.apache.org/jira/browse/JUDDI-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176685#comment-17176685
]
ASF subversion and git services commented on JUDDI-1015:
Commit 93f2d3693cff16e52129171368d36b2580fc in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=93f2d36 ]
Merge branch 'master' into bug/JUDDI-1015
> Oracle database start up issue due to max string length
> ---
>
> Key: JUDDI-1015
> URL: https://issues.apache.org/jira/browse/JUDDI-1015
> Project: jUDDI
> Issue Type: Bug
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.9
>
>
> from the juddi mailing list
>
> {color:#172b4d}Oracle Version of Juddi Due to string limit for a column
> CREATE TABLE j3_binding_template (entity_key VARCHAR2(255) NOT NULL,
> access_point_type VARCHAR2(255), access_point_url VARCHAR2(4096),
> hosting_redirector VARCHAR2(255), service_key VARCHAR2(255) NOT NULL, PRIMARY
> KEY (entity_key)) {color}*Oracle max varchar limit: 4000*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-1015) Oracle database start up issue due to max string length
[
https://issues.apache.org/jira/browse/JUDDI-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176682#comment-17176682
]
ASF subversion and git services commented on JUDDI-1015:
Commit 7d562f926b974d46b5e0f9e76d774a10ff9dc889 in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=7d562f9 ]
JUDDI-1015 incomplete fix for certain columns being too long on specific
database vendors (oracle in this case). this has some test failures and query
issues due to the column type changes.
> Oracle database start up issue due to max string length
> ---
>
> Key: JUDDI-1015
> URL: https://issues.apache.org/jira/browse/JUDDI-1015
> Project: jUDDI
> Issue Type: Bug
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.9
>
>
> from the juddi mailing list
>
> {color:#172b4d}Oracle Version of Juddi Due to string limit for a column
> CREATE TABLE j3_binding_template (entity_key VARCHAR2(255) NOT NULL,
> access_point_type VARCHAR2(255), access_point_url VARCHAR2(4096),
> hosting_redirector VARCHAR2(255), service_key VARCHAR2(255) NOT NULL, PRIMARY
> KEY (entity_key)) {color}*Oracle max varchar limit: 4000*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-1014) Binding Editor – tModel Instance Information
[ https://issues.apache.org/jira/browse/JUDDI-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176672#comment-17176672 ] ASF subversion and git services commented on JUDDI-1014: Commit 1c7db5d2e0f9863614bd16e5ff4f627c63426a18 in juddi's branch refs/heads/bug/JUDDI-1015 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=1c7db5d ] JUDDI-1014 adds a field to display the display name of tmodels when adding tmodel instance info, tmodel instance params > 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.8 > > 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)
[jira] [Commented] (JUDDI-1015) Oracle database start up issue due to max string length
[
https://issues.apache.org/jira/browse/JUDDI-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176674#comment-17176674
]
ASF subversion and git services commented on JUDDI-1015:
Commit 4d7bc5a3bf37e7d5341286432c129f8fb1a4b203 in juddi's branch
refs/heads/bug/JUDDI-1015 from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=4d7bc5a ]
JUDDI-1015 reduces sql identifiers for better support for both mssql and for
oracledb.
JUDDI-1101 related. also resolves sql query issues for discoery url due to
varchar to clob change
> Oracle database start up issue due to max string length
> ---
>
> Key: JUDDI-1015
> URL: https://issues.apache.org/jira/browse/JUDDI-1015
> Project: jUDDI
> Issue Type: Bug
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.8
>
>
> from the juddi mailing list
>
> {color:#172b4d}Oracle Version of Juddi Due to string limit for a column
> CREATE TABLE j3_binding_template (entity_key VARCHAR2(255) NOT NULL,
> access_point_type VARCHAR2(255), access_point_url VARCHAR2(4096),
> hosting_redirector VARCHAR2(255), service_key VARCHAR2(255) NOT NULL, PRIMARY
> KEY (entity_key)) {color}*Oracle max varchar limit: 4000*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-1015) Oracle database start up issue due to max string length
[
https://issues.apache.org/jira/browse/JUDDI-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176673#comment-17176673
]
ASF subversion and git services commented on JUDDI-1015:
Commit 7a26bedd92cff633d641118d19b5237ac8474105 in juddi's branch
refs/heads/bug/JUDDI-1015 from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=7a26bed ]
Merge branch 'master' into bug/JUDDI-1015
> Oracle database start up issue due to max string length
> ---
>
> Key: JUDDI-1015
> URL: https://issues.apache.org/jira/browse/JUDDI-1015
> Project: jUDDI
> Issue Type: Bug
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.8
>
>
> from the juddi mailing list
>
> {color:#172b4d}Oracle Version of Juddi Due to string limit for a column
> CREATE TABLE j3_binding_template (entity_key VARCHAR2(255) NOT NULL,
> access_point_type VARCHAR2(255), access_point_url VARCHAR2(4096),
> hosting_redirector VARCHAR2(255), service_key VARCHAR2(255) NOT NULL, PRIMARY
> KEY (entity_key)) {color}*Oracle max varchar limit: 4000*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-1009) Browse Businesses using juddiv2 page navigation issue
[ https://issues.apache.org/jira/browse/JUDDI-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17176671#comment-17176671 ] ASF subversion and git services commented on JUDDI-1009: Commit ab728473c9197a48c15934bedafde537d502512d in juddi's branch refs/heads/bug/JUDDI-1015 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=ab72847 ] JUDDI-1009 reworks a number of functions in the ui related to paging operations, limits, offsets, etc. i think everything is working now. Adds some new functionality and some alt text warnings when using uddiv2 connections (offsets are not in the data model) > 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.8 > > 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] [Commented] (JUDDI-1014) Binding Editor – tModel Instance Information
[ https://issues.apache.org/jira/browse/JUDDI-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17160833#comment-17160833 ] ASF subversion and git services commented on JUDDI-1014: Commit 1c7db5d2e0f9863614bd16e5ff4f627c63426a18 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=1c7db5d ] JUDDI-1014 adds a field to display the display name of tmodels when adding tmodel instance info, tmodel instance params > 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 > 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)
[jira] [Commented] (JUDDI-1009) Browse Businesses using juddiv2 page navigation issue
[ https://issues.apache.org/jira/browse/JUDDI-1009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17160813#comment-17160813 ] ASF subversion and git services commented on JUDDI-1009: Commit ab728473c9197a48c15934bedafde537d502512d in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=ab72847 ] JUDDI-1009 reworks a number of functions in the ui related to paging operations, limits, offsets, etc. i think everything is working now. Adds some new functionality and some alt text warnings when using uddiv2 connections (offsets are not in the data model) > 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 > 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] [Commented] (JUDDI-1015) Oracle database start up issue due to max string length
[
https://issues.apache.org/jira/browse/JUDDI-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159606#comment-17159606
]
ASF subversion and git services commented on JUDDI-1015:
Commit 93f2d3693cff16e52129171368d36b2580fc in juddi's branch
refs/heads/bug/JUDDI-1015 from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=93f2d36 ]
Merge branch 'master' into bug/JUDDI-1015
> Oracle database start up issue due to max string length
> ---
>
> Key: JUDDI-1015
> URL: https://issues.apache.org/jira/browse/JUDDI-1015
> Project: jUDDI
> Issue Type: Bug
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.8
>
>
> from the juddi mailing list
>
> {color:#172b4d}Oracle Version of Juddi Due to string limit for a column
> CREATE TABLE j3_binding_template (entity_key VARCHAR2(255) NOT NULL,
> access_point_type VARCHAR2(255), access_point_url VARCHAR2(4096),
> hosting_redirector VARCHAR2(255), service_key VARCHAR2(255) NOT NULL, PRIMARY
> KEY (entity_key)) {color}*Oracle max varchar limit: 4000*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-1015) Oracle database start up issue due to max string length
[
https://issues.apache.org/jira/browse/JUDDI-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159605#comment-17159605
]
ASF subversion and git services commented on JUDDI-1015:
Commit c6e69a48bfe61dde00a8ff8873bb8f946e06e4ea in juddi's branch
refs/heads/bug/JUDDI-1015 from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=c6e69a4 ]
JUDDI-1015 adds oracle and mssql drivers to the mix along with an example for
oracle db
> Oracle database start up issue due to max string length
> ---
>
> Key: JUDDI-1015
> URL: https://issues.apache.org/jira/browse/JUDDI-1015
> Project: jUDDI
> Issue Type: Bug
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.8
>
>
> from the juddi mailing list
>
> {color:#172b4d}Oracle Version of Juddi Due to string limit for a column
> CREATE TABLE j3_binding_template (entity_key VARCHAR2(255) NOT NULL,
> access_point_type VARCHAR2(255), access_point_url VARCHAR2(4096),
> hosting_redirector VARCHAR2(255), service_key VARCHAR2(255) NOT NULL, PRIMARY
> KEY (entity_key)) {color}*Oracle max varchar limit: 4000*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-1008) find_business returns an error when querying a tModel when using the v2 Inquire API
[ https://issues.apache.org/jira/browse/JUDDI-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159604#comment-17159604 ] ASF subversion and git services commented on JUDDI-1008: Commit f9ca9042de955fd61e3c8edf65b6616526ca1a43 in juddi's branch refs/heads/bug/JUDDI-1015 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=f9ca904 ] JUDDI-1008 fix for find by ident bag via v2 findbusiness api > 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.8 > > > 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] [Commented] (JUDDI-1012) MS SQL Server Sequence table change
[ https://issues.apache.org/jira/browse/JUDDI-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159603#comment-17159603 ] ASF subversion and git services commented on JUDDI-1012: Commit bad3192dddc3f4b168e6923da9f051616554c2ed in juddi's branch refs/heads/bug/JUDDI-1015 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=bad3192 ] JUDDI-1012 newer version of hibernate (jre8 min), also adds some additional DDLs for mssql and oracle > 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.8 > > > 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] [Commented] (JUDDI-1008) find_business returns an error when querying a tModel when using the v2 Inquire API
[ https://issues.apache.org/jira/browse/JUDDI-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17156156#comment-17156156 ] ASF subversion and git services commented on JUDDI-1008: Commit f9ca9042de955fd61e3c8edf65b6616526ca1a43 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=f9ca904 ] JUDDI-1008 fix for find by ident bag via v2 findbusiness api > 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.8 > > > 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] [Commented] (JUDDI-1012) MS SQL Server Sequence table change
[ https://issues.apache.org/jira/browse/JUDDI-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155828#comment-17155828 ] ASF subversion and git services commented on JUDDI-1012: Commit bad3192dddc3f4b168e6923da9f051616554c2ed in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=bad3192 ] JUDDI-1012 newer version of hibernate (jre8 min), also adds some additional DDLs for mssql and oracle > 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 >Priority: Major > > 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] [Commented] (JUDDI-1015) Oracle database start up issue due to max string length
[
https://issues.apache.org/jira/browse/JUDDI-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155812#comment-17155812
]
ASF subversion and git services commented on JUDDI-1015:
Commit 7d562f926b974d46b5e0f9e76d774a10ff9dc889 in juddi's branch
refs/heads/bug/JUDDI-1015 from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=7d562f9 ]
JUDDI-1015 incomplete fix for certain columns being too long on specific
database vendors (oracle in this case). this has some test failures and query
issues due to the column type changes.
> Oracle database start up issue due to max string length
> ---
>
> Key: JUDDI-1015
> URL: https://issues.apache.org/jira/browse/JUDDI-1015
> Project: jUDDI
> Issue Type: Bug
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.8
>
>
> from the juddi mailing list
>
> {color:#172b4d}Oracle Version of Juddi Due to string limit for a column
> CREATE TABLE j3_binding_template (entity_key VARCHAR2(255) NOT NULL,
> access_point_type VARCHAR2(255), access_point_url VARCHAR2(4096),
> hosting_redirector VARCHAR2(255), service_key VARCHAR2(255) NOT NULL, PRIMARY
> KEY (entity_key)) {color}*Oracle max varchar limit: 4000*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-1013) GUI adding records
[ https://issues.apache.org/jira/browse/JUDDI-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151155#comment-17151155 ] ASF subversion and git services commented on JUDDI-1013: Commit c8bce39ec3efd546a2dd4e4fd5e072cc218a86a1 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=c8bce39 ] JUDDI-1013 insurance > 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] [Commented] (JUDDI-1013) GUI adding records
[ https://issues.apache.org/jira/browse/JUDDI-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17151152#comment-17151152 ] ASF subversion and git services commented on JUDDI-1013: Commit b2388cb66f11981733201a24de9234c205b217a7 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=b2388cb ] JUDDI-1013 auto refreshes the page after the save > 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] [Commented] (JUDDI-1006) Saving an Access Point Type
[ https://issues.apache.org/jira/browse/JUDDI-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17142545#comment-17142545 ] ASF subversion and git services commented on JUDDI-1006: Commit ac30b6e710334643f4ce33e5dd9f34d52db3 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=ac3 ] JUDDI-1006 fixed, along with some light refactoring > Saving an Access Point Type > --- > > Key: JUDDI-1006 > URL: https://issues.apache.org/jira/browse/JUDDI-1006 > Project: jUDDI > Issue Type: Bug > Components: core >Reporter: Alex O'Ree >Priority: Minor > > Using juddi default (v3) you can create an access point type of Mailto which > saves to the database and is displayed properly in the UI. When using > juddiv2, the access point type displays as endpoint. > > Using juddiv2 create an Access Point using a random binding template key, > access point type “Mailto” and Access Point Value: > “[[t...@email.com|mailto:[t...@email.com]|mailto:t...@email.com]” and save > the access point. The value endPoint is saved in the database, not Mailto. > If the database contains a value of Mailto in the access_point_type field, it > still displays endPoint in the UI. > > Note that the response from the v2 Inquire API returns the value of mailto if > this value is in the database. > URLType="mailto">[mailto:t...@email.commailto:t...@email.com%3c/ns2:accessPoint]> -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-1003) spring-web jar supplied with latest JUDDI distribution has security vulnerability
[
https://issues.apache.org/jira/browse/JUDDI-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054191#comment-17054191
]
ASF subversion and git services commented on JUDDI-1003:
Commit a28db0a7a6f30a15bcdd588057a1cfb410a9ff28 in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=a28db0a ]
JUDDI-1003 updates spring web dependency
JUDDI-1005 related, fixes the distrubtion so that the executable jar for the
migration tool is included
NOJIRA minor jsp code cleanup
> spring-web jar supplied with latest JUDDI distribution has security
> vulnerability
> -
>
> Key: JUDDI-1003
> URL: https://issues.apache.org/jira/browse/JUDDI-1003
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6, 3.3.7
>Reporter: Amol Bhonsle
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.8
>
>
> The jar for spring-web (JUDDI 3.3.7 comes with spring-web-3.2.18.RELEASE)
> which is provided in distribution has following Security Vulnerability.
>
> The {{org.springframework:spring-web}} package is vulnerable to
> deserialization of untrusted data leading to Remote Code Execution (RCE).
> The {{readRemoteInvocation}} method in {{HttpInvokerServiceExporter.class}}
> does not properly verify or restrict untrusted objects prior to deserializing
> them. An attacker can exploit this vulnerability by sending malicious
> requests containing crafted objects, which when deserialized, execute
> arbitrary code on the vulnerable system.
>
> The {{spring-core}} and {{spring-web}} modules of Spring Framework are
> vulnerable to a multipart content pollution vulnerability. The
> {{generateMultipartBoundary()}} method in the {{MimeTypeUtils}} class uses a
> predictable method of generating random values to use as boundary values for
> multipart requests to other servers. This means that an attacker may be able
> to predict the boundary values and inject them into requests at unexpected
> locations, causing the recipient server to incorrectly interpret the
> multipart request. This will result in unexpected behavior depending on the
> requests being processed, including privilege escalation if authorization
> data is sent in the multipart request.
> Note:
> {quote}In order for the attacker to succeed, they would have to be able to
> guess the multipart boundary value chosen by server A for the multipart
> request to server B, which requires the attacker to also have control of the
> server or the ability to see the HTTP log of server A through a separate
> attack vector.
> {quote}
>
> Spring Framework is vulnerable to Cross-Site Tracing (XST) attacks. The
> {{HiddenHttpMethodFilter}} class lets an attacker change the HTTP request
> method to {{TRACE}}. An attacker can exploit this behavior with an Cross-Site
> Scripting (XSS) attack by sending a TRACE request and recovering information
> that would not normally be accessible, such as Cookies with the HTTPOnly flag.
>
> Please check and provide fix for this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema
[
https://issues.apache.org/jira/browse/JUDDI-1005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054192#comment-17054192
]
ASF subversion and git services commented on JUDDI-1005:
Commit a28db0a7a6f30a15bcdd588057a1cfb410a9ff28 in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=a28db0a ]
JUDDI-1003 updates spring web dependency
JUDDI-1005 related, fixes the distrubtion so that the executable jar for the
migration tool is included
NOJIRA minor jsp code cleanup
> Need To have correct options to upgrade JUDDI DB Schema
> ---
>
> Key: JUDDI-1005
> URL: https://issues.apache.org/jira/browse/JUDDI-1005
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6, 3.3.7
>Reporter: Amol Bhonsle
>Priority: Major
> Attachments:
> uddi-migration-tool-3.3.8-SNAPSHOT-jar-with-dependencies.jar
>
>
> We are trying to update JUDDI DB from JUDDI-3.0.4 to JUDDI-3.3.7. JUDDI DB is
> hosted on SQL Server. We use openjpa-2.3.0 which is provided by juddi-3.3.7
> distribution.
>
> As per openjpa-2.3.0 documentation:
> {{drop option of SchemaTool should do following:}}
> {{drop}}: Drop all schema components in the schema XML. Tables will only be
> dropped if they would have 0 columns after dropping all columns listed in the
> XML.
> and add option should do following:
> {{add}}: This is the default action if you do not specify one. It brings the
> schema up-to-date with the given XML document by adding tables, columns,
> indexes, etc. This action never drops any schema components.
> Also it is allowed in persistence.xml to use options as comma separated, so
> we tried following option in persistence.xml to drop old tables and create
> new tables as per juddi-3.3.7 schema but it did not work:
> value="buildSchema(SchemaAction='drop,add')"/>
>
> This gives following Exception when JUDDI is deployed by tomcat :
>
> {code:java}
> SEVERE: Exception sending context initialized event to listener instance of
> class org.springframework.web.context.ContextLoaderListenerSEVERE: Exception
> sending context initialized event to listener instance of class
> org.springframework.web.context.ContextLoaderListenerorg.springframework.beans.factory.BeanCreationException:
> Error creating bean with name 'inquiry': Cannot create inner bean '(inner
> bean)#fa6535a' of type [org.apache.juddi.api.impl.UDDIInquiryImpl] while
> setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name '(inner bean)#fa6535a': Instantiation of bean failed; nested
> exception is org.springframework.beans.BeanInstantiationException: Failed to
> instantiate [org.apache.juddi.api.impl.UDDIInquiryImpl]: Constructor threw
> exception; nested exception is general error> org.apache.openjpa.persistence.PersistenceException: The
> object 'PK__j3_clerk__5609ADDDCF01D08E' is dependent on column 'clerk_name'.
> \{stmnt 1807668378 ALTER TABLE j3_clerk DROP COLUMN clerk_name} [code=5074,
> state=S0001] at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:389)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:134)
> at
> org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:691)
> at
> org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:196)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1358)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1204)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:557)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:517)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:323)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory$$Lambda$208/1654431226.getObject(Unknown
> Source) at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:321)
> at
>
[jira] [Commented] (JUDDI-937) PolicyRoundRobin not working without service cache
[
https://issues.apache.org/jira/browse/JUDDI-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17027938#comment-17027938
]
ASF subversion and git services commented on JUDDI-937:
---
Commit 13101ecb48ad76fbb3a8c4aee84852887aae340d in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=13101ec ]
Merge branch 'bug/JUDDI-937'
> PolicyRoundRobin not working without service cache
> --
>
> Key: JUDDI-937
> URL: https://issues.apache.org/jira/browse/JUDDI-937
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-client
>Affects Versions: 3.3.1
>Reporter: Matthieu Ghilain
>Assignee: Alex O'Ree
>Priority: Minor
> Labels: cache, juddi, policy
> Fix For: 3.3.8
>
>
> I use the following method in order to resolve an endpoint:
> {code:title=Resolve endpoint function|borderStyle=solid}
> private String resolveEndpointForServiceID(String uddiServiceId) {
> try {
> UDDIClient uddiClient = new UDDIClient();
> ServiceLocator serviceLocator =
> uddiClient.getServiceLocator("uddiv3");
> serviceLocator.setPolicy(PolicyRoundRobin.class.getName());
> return serviceLocator.lookupEndpoint(uddiServiceId);
> } catch (Exception e) {
> throw new EndpointResolutionFromUDDIException("Could not resolve
> endpoint '"+uddiServiceId+"'.", e);
> }
> }
> {code}
> I have registered two different binding templates in juddi. Using this code I
> always receive the same endpoint. This comes from the fact that the topology
> is reloaded each time the lookupEndpoint is called because there is no cache.
> I guess that the service policy should still be able to make a round robin
> between the binding templates even if no cache is used.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-937) PolicyRoundRobin not working without service cache
[
https://issues.apache.org/jira/browse/JUDDI-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17027937#comment-17027937
]
ASF subversion and git services commented on JUDDI-937:
---
Commit 5ac79c870c2e804ca154ee1dc207e6a8087d609d in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=5ac79c8 ]
JUDDI-937 adding test cases, discovered a caching mechanism that had no way of
being cleared which was resolved.
> PolicyRoundRobin not working without service cache
> --
>
> Key: JUDDI-937
> URL: https://issues.apache.org/jira/browse/JUDDI-937
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-client
>Affects Versions: 3.3.1
>Reporter: Matthieu Ghilain
>Assignee: Alex O'Ree
>Priority: Minor
> Labels: cache, juddi, policy
> Fix For: 3.3.8
>
>
> I use the following method in order to resolve an endpoint:
> {code:title=Resolve endpoint function|borderStyle=solid}
> private String resolveEndpointForServiceID(String uddiServiceId) {
> try {
> UDDIClient uddiClient = new UDDIClient();
> ServiceLocator serviceLocator =
> uddiClient.getServiceLocator("uddiv3");
> serviceLocator.setPolicy(PolicyRoundRobin.class.getName());
> return serviceLocator.lookupEndpoint(uddiServiceId);
> } catch (Exception e) {
> throw new EndpointResolutionFromUDDIException("Could not resolve
> endpoint '"+uddiServiceId+"'.", e);
> }
> }
> {code}
> I have registered two different binding templates in juddi. Using this code I
> always receive the same endpoint. This comes from the fact that the topology
> is reloaded each time the lookupEndpoint is called because there is no cache.
> I guess that the service policy should still be able to make a round robin
> between the binding templates even if no cache is used.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-937) PolicyRoundRobin not working without service cache
[
https://issues.apache.org/jira/browse/JUDDI-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17027936#comment-17027936
]
ASF subversion and git services commented on JUDDI-937:
---
Commit 07790a220657525c85d446ed9427aa9ac3fac6ee in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=07790a2 ]
JUDDI-937 this resolve the caching issue, needs a test case still
> PolicyRoundRobin not working without service cache
> --
>
> Key: JUDDI-937
> URL: https://issues.apache.org/jira/browse/JUDDI-937
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-client
>Affects Versions: 3.3.1
>Reporter: Matthieu Ghilain
>Assignee: Alex O'Ree
>Priority: Minor
> Labels: cache, juddi, policy
> Fix For: 3.3.8
>
>
> I use the following method in order to resolve an endpoint:
> {code:title=Resolve endpoint function|borderStyle=solid}
> private String resolveEndpointForServiceID(String uddiServiceId) {
> try {
> UDDIClient uddiClient = new UDDIClient();
> ServiceLocator serviceLocator =
> uddiClient.getServiceLocator("uddiv3");
> serviceLocator.setPolicy(PolicyRoundRobin.class.getName());
> return serviceLocator.lookupEndpoint(uddiServiceId);
> } catch (Exception e) {
> throw new EndpointResolutionFromUDDIException("Could not resolve
> endpoint '"+uddiServiceId+"'.", e);
> }
> }
> {code}
> I have registered two different binding templates in juddi. Using this code I
> always receive the same endpoint. This comes from the fact that the topology
> is reloaded each time the lookupEndpoint is called because there is no cache.
> I guess that the service policy should still be able to make a round robin
> between the binding templates even if no cache is used.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-1004) JUDDI-3.3.7 With SQL Server Database Gives Primary Key Violation For Table j3_category_bag
[
https://issues.apache.org/jira/browse/JUDDI-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17027935#comment-17027935
]
ASF subversion and git services commented on JUDDI-1004:
Commit a1fb95d9a69617c3fd5d40cf336d7ff53866a431 in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=a1fb95d ]
JUDDI-1004 dependency update, this means juddi will require java 8 as a minimum
runtime
> 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
>
> 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
>
[jira] [Commented] (JUDDI-937) PolicyRoundRobin not working without service cache
[
https://issues.apache.org/jira/browse/JUDDI-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17019635#comment-17019635
]
ASF subversion and git services commented on JUDDI-937:
---
Commit 5ac79c870c2e804ca154ee1dc207e6a8087d609d in juddi's branch
refs/heads/bug/JUDDI-937 from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=5ac79c8 ]
JUDDI-937 adding test cases, discovered a caching mechanism that had no way of
being cleared which was resolved.
> PolicyRoundRobin not working without service cache
> --
>
> Key: JUDDI-937
> URL: https://issues.apache.org/jira/browse/JUDDI-937
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-client
>Affects Versions: 3.3.1
>Reporter: Matthieu Ghilain
>Assignee: Alex O'Ree
>Priority: Minor
> Labels: cache, juddi, policy
> Fix For: 3.3.8
>
>
> I use the following method in order to resolve an endpoint:
> {code:title=Resolve endpoint function|borderStyle=solid}
> private String resolveEndpointForServiceID(String uddiServiceId) {
> try {
> UDDIClient uddiClient = new UDDIClient();
> ServiceLocator serviceLocator =
> uddiClient.getServiceLocator("uddiv3");
> serviceLocator.setPolicy(PolicyRoundRobin.class.getName());
> return serviceLocator.lookupEndpoint(uddiServiceId);
> } catch (Exception e) {
> throw new EndpointResolutionFromUDDIException("Could not resolve
> endpoint '"+uddiServiceId+"'.", e);
> }
> }
> {code}
> I have registered two different binding templates in juddi. Using this code I
> always receive the same endpoint. This comes from the fact that the topology
> is reloaded each time the lookupEndpoint is called because there is no cache.
> I guess that the service policy should still be able to make a round robin
> between the binding templates even if no cache is used.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-937) PolicyRoundRobin not working without service cache
[
https://issues.apache.org/jira/browse/JUDDI-937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17019217#comment-17019217
]
ASF subversion and git services commented on JUDDI-937:
---
Commit 07790a220657525c85d446ed9427aa9ac3fac6ee in juddi's branch
refs/heads/bug/JUDDI-937 from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=07790a2 ]
JUDDI-937 this resolve the caching issue, needs a test case still
> PolicyRoundRobin not working without service cache
> --
>
> Key: JUDDI-937
> URL: https://issues.apache.org/jira/browse/JUDDI-937
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-client
>Affects Versions: 3.3.1
>Reporter: Matthieu Ghilain
>Assignee: Alex O'Ree
>Priority: Minor
> Labels: cache, juddi, policy
>
> I use the following method in order to resolve an endpoint:
> {code:title=Resolve endpoint function|borderStyle=solid}
> private String resolveEndpointForServiceID(String uddiServiceId) {
> try {
> UDDIClient uddiClient = new UDDIClient();
> ServiceLocator serviceLocator =
> uddiClient.getServiceLocator("uddiv3");
> serviceLocator.setPolicy(PolicyRoundRobin.class.getName());
> return serviceLocator.lookupEndpoint(uddiServiceId);
> } catch (Exception e) {
> throw new EndpointResolutionFromUDDIException("Could not resolve
> endpoint '"+uddiServiceId+"'.", e);
> }
> }
> {code}
> I have registered two different binding templates in juddi. Using this code I
> always receive the same endpoint. This comes from the fact that the topology
> is reloaded each time the lookupEndpoint is called because there is no cache.
> I guess that the service policy should still be able to make a round robin
> between the binding templates even if no cache is used.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-993) InVm transport for embedded juddi needs to handle authentication
[ https://issues.apache.org/jira/browse/JUDDI-993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17019200#comment-17019200 ] ASF subversion and git services commented on JUDDI-993: --- Commit baba62cc23039af5bd486ccb39978908ec21f3cd in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=baba62c ] JUDDI-993 sample for running juddi in an embedded server, with and without http access. also changes a few hopefully minor things in juddi core and client. > InVm transport for embedded juddi needs to handle authentication > - > > Key: JUDDI-993 > URL: https://issues.apache.org/jira/browse/JUDDI-993 > Project: jUDDI > Issue Type: Improvement > Components: juddi-client >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > > currently, all authentication scenarios are not processed for an embedded > juddi server type of setup. This is probably ok for some scenarios but for > web scenarios, such as merging juddi-gui and the services war, it would be > insufficient. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-1003) spring-web jar supplied with latest JUDDI distribution has security vulnerability
[
https://issues.apache.org/jira/browse/JUDDI-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018685#comment-17018685
]
ASF subversion and git services commented on JUDDI-1003:
Commit 05896ecd4e1c8b35edb90efbc4623db77b9ac186 in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=05896ec ]
JUDDI-1003 resolved by updating dependencies
NOJIRA switched to ssl nexus repo for central
> spring-web jar supplied with latest JUDDI distribution has security
> vulnerability
> -
>
> Key: JUDDI-1003
> URL: https://issues.apache.org/jira/browse/JUDDI-1003
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6, 3.3.7
>Reporter: Amol Bhonsle
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.8
>
>
> The jar for spring-web (JUDDI 3.3.7 comes with spring-web-3.2.18.RELEASE)
> which is provided in distribution has following Security Vulnerability.
>
> The {{org.springframework:spring-web}} package is vulnerable to
> deserialization of untrusted data leading to Remote Code Execution (RCE).
> The {{readRemoteInvocation}} method in {{HttpInvokerServiceExporter.class}}
> does not properly verify or restrict untrusted objects prior to deserializing
> them. An attacker can exploit this vulnerability by sending malicious
> requests containing crafted objects, which when deserialized, execute
> arbitrary code on the vulnerable system.
>
> The {{spring-core}} and {{spring-web}} modules of Spring Framework are
> vulnerable to a multipart content pollution vulnerability. The
> {{generateMultipartBoundary()}} method in the {{MimeTypeUtils}} class uses a
> predictable method of generating random values to use as boundary values for
> multipart requests to other servers. This means that an attacker may be able
> to predict the boundary values and inject them into requests at unexpected
> locations, causing the recipient server to incorrectly interpret the
> multipart request. This will result in unexpected behavior depending on the
> requests being processed, including privilege escalation if authorization
> data is sent in the multipart request.
> Note:
> {quote}In order for the attacker to succeed, they would have to be able to
> guess the multipart boundary value chosen by server A for the multipart
> request to server B, which requires the attacker to also have control of the
> server or the ability to see the HTTP log of server A through a separate
> attack vector.
> {quote}
>
> Spring Framework is vulnerable to Cross-Site Tracing (XST) attacks. The
> {{HiddenHttpMethodFilter}} class lets an attacker change the HTTP request
> method to {{TRACE}}. An attacker can exploit this behavior with an Cross-Site
> Scripting (XSS) attack by sending a TRACE request and recovering information
> that would not normally be accessible, such as Cookies with the HTTPOnly flag.
>
> Please check and provide fix for this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-1002) tModelInstanceInfo value does not check for maximum length
[ https://issues.apache.org/jira/browse/JUDDI-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018684#comment-17018684 ] ASF subversion and git services commented on JUDDI-1002: Commit 299d918f165696e1da0806e109d71ca363a73416 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=299d918 ] JUDDI-1002 this adds length validation to tmodel instance info > tModelInstanceInfo value does not check for maximum length > -- > > Key: JUDDI-1002 > URL: https://issues.apache.org/jira/browse/JUDDI-1002 > Project: jUDDI > Issue Type: Improvement >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-1002) tModelInstanceInfo value does not check for maximum length
[ https://issues.apache.org/jira/browse/JUDDI-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000306#comment-17000306 ] ASF subversion and git services commented on JUDDI-1002: Commit 299d918f165696e1da0806e109d71ca363a73416 in juddi's branch refs/heads/feature/JUDDI-1002 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=299d918 ] JUDDI-1002 this adds length validation to tmodel instance info > tModelInstanceInfo value does not check for maximum length > -- > > Key: JUDDI-1002 > URL: https://issues.apache.org/jira/browse/JUDDI-1002 > Project: jUDDI > Issue Type: Improvement >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF
[ https://issues.apache.org/jira/browse/JUDDI-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995928#comment-16995928 ] ASF subversion and git services commented on JUDDI-991: --- Commit 044d97ff22f51bca8f58496bac20aea25c5e68d6 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=044d97f ] JUDDI-991 cxf update > JUDDI Uses EOL Version of Apache CXF > > > Key: JUDDI-991 > URL: https://issues.apache.org/jira/browse/JUDDI-991 > Project: jUDDI > Issue Type: Bug > Components: CXF >Affects Versions: 3.3.5 >Reporter: Mark Kloepping >Assignee: Alex O'Ree >Priority: Major > Labels: security > Fix For: 3.3.7 > > > JUDDI uses Apache CXF version 2.7.18 which is an End of Life (EOL) version of > the library. > "Versions of CXF prior to 3.1.x are no longer supported at Apache. They are > now considered end-of-life and are therefore unsupported. Users are highly > encouraged to [migrate|http://cxf.apache.org/docs/migration-guides.html] to > newer versions of CXF." ref: [http://cxf.apache.org/roadmap.html] > Hopefully a future release to JUDDI can include a more recent and supported > version of Apache CXF. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF
[ https://issues.apache.org/jira/browse/JUDDI-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995927#comment-16995927 ] ASF subversion and git services commented on JUDDI-991: --- Commit 4522d6fb5bf61408aa8a4f20e47f2ee2813b48ff in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=4522d6f ] Merge branch 'master' into feature/JUDDI-991 > JUDDI Uses EOL Version of Apache CXF > > > Key: JUDDI-991 > URL: https://issues.apache.org/jira/browse/JUDDI-991 > Project: jUDDI > Issue Type: Bug > Components: CXF >Affects Versions: 3.3.5 >Reporter: Mark Kloepping >Assignee: Alex O'Ree >Priority: Major > Labels: security > Fix For: 3.3.7 > > > JUDDI uses Apache CXF version 2.7.18 which is an End of Life (EOL) version of > the library. > "Versions of CXF prior to 3.1.x are no longer supported at Apache. They are > now considered end-of-life and are therefore unsupported. Users are highly > encouraged to [migrate|http://cxf.apache.org/docs/migration-guides.html] to > newer versions of CXF." ref: [http://cxf.apache.org/roadmap.html] > Hopefully a future release to JUDDI can include a more recent and supported > version of Apache CXF. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF
[ https://issues.apache.org/jira/browse/JUDDI-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995925#comment-16995925 ] ASF subversion and git services commented on JUDDI-991: --- Commit e4112296a261249fc41663341933f3a931f5f07c in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=e411229 ] JUDDI-991 progress with cxf upgrade > JUDDI Uses EOL Version of Apache CXF > > > Key: JUDDI-991 > URL: https://issues.apache.org/jira/browse/JUDDI-991 > Project: jUDDI > Issue Type: Bug > Components: CXF >Affects Versions: 3.3.5 >Reporter: Mark Kloepping >Assignee: Alex O'Ree >Priority: Major > Labels: security > Fix For: 3.3.7 > > > JUDDI uses Apache CXF version 2.7.18 which is an End of Life (EOL) version of > the library. > "Versions of CXF prior to 3.1.x are no longer supported at Apache. They are > now considered end-of-life and are therefore unsupported. Users are highly > encouraged to [migrate|http://cxf.apache.org/docs/migration-guides.html] to > newer versions of CXF." ref: [http://cxf.apache.org/roadmap.html] > Hopefully a future release to JUDDI can include a more recent and supported > version of Apache CXF. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF
[ https://issues.apache.org/jira/browse/JUDDI-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995926#comment-16995926 ] ASF subversion and git services commented on JUDDI-991: --- Commit 8016bf340db08da87391129cfec23a59b1473691 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=8016bf3 ] Merge branch 'master' into feature/JUDDI-991 > JUDDI Uses EOL Version of Apache CXF > > > Key: JUDDI-991 > URL: https://issues.apache.org/jira/browse/JUDDI-991 > Project: jUDDI > Issue Type: Bug > Components: CXF >Affects Versions: 3.3.5 >Reporter: Mark Kloepping >Assignee: Alex O'Ree >Priority: Major > Labels: security > Fix For: 3.3.7 > > > JUDDI uses Apache CXF version 2.7.18 which is an End of Life (EOL) version of > the library. > "Versions of CXF prior to 3.1.x are no longer supported at Apache. They are > now considered end-of-life and are therefore unsupported. Users are highly > encouraged to [migrate|http://cxf.apache.org/docs/migration-guides.html] to > newer versions of CXF." ref: [http://cxf.apache.org/roadmap.html] > Hopefully a future release to JUDDI can include a more recent and supported > version of Apache CXF. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF
[ https://issues.apache.org/jira/browse/JUDDI-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995924#comment-16995924 ] ASF subversion and git services commented on JUDDI-991: --- Commit 044d97ff22f51bca8f58496bac20aea25c5e68d6 in juddi's branch refs/heads/feature/JUDDI-991 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=044d97f ] JUDDI-991 cxf update > JUDDI Uses EOL Version of Apache CXF > > > Key: JUDDI-991 > URL: https://issues.apache.org/jira/browse/JUDDI-991 > Project: jUDDI > Issue Type: Bug > Components: CXF >Affects Versions: 3.3.5 >Reporter: Mark Kloepping >Assignee: Alex O'Ree >Priority: Major > Labels: security > Fix For: 3.3.7 > > > JUDDI uses Apache CXF version 2.7.18 which is an End of Life (EOL) version of > the library. > "Versions of CXF prior to 3.1.x are no longer supported at Apache. They are > now considered end-of-life and are therefore unsupported. Users are highly > encouraged to [migrate|http://cxf.apache.org/docs/migration-guides.html] to > newer versions of CXF." ref: [http://cxf.apache.org/roadmap.html] > Hopefully a future release to JUDDI can include a more recent and supported > version of Apache CXF. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF
[ https://issues.apache.org/jira/browse/JUDDI-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995923#comment-16995923 ] ASF subversion and git services commented on JUDDI-991: --- Commit 4522d6fb5bf61408aa8a4f20e47f2ee2813b48ff in juddi's branch refs/heads/feature/JUDDI-991 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=4522d6f ] Merge branch 'master' into feature/JUDDI-991 > JUDDI Uses EOL Version of Apache CXF > > > Key: JUDDI-991 > URL: https://issues.apache.org/jira/browse/JUDDI-991 > Project: jUDDI > Issue Type: Bug > Components: CXF >Affects Versions: 3.3.5 >Reporter: Mark Kloepping >Assignee: Alex O'Ree >Priority: Major > Labels: security > Fix For: 3.3.7 > > > JUDDI uses Apache CXF version 2.7.18 which is an End of Life (EOL) version of > the library. > "Versions of CXF prior to 3.1.x are no longer supported at Apache. They are > now considered end-of-life and are therefore unsupported. Users are highly > encouraged to [migrate|http://cxf.apache.org/docs/migration-guides.html] to > newer versions of CXF." ref: [http://cxf.apache.org/roadmap.html] > Hopefully a future release to JUDDI can include a more recent and supported > version of Apache CXF. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF
[ https://issues.apache.org/jira/browse/JUDDI-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995921#comment-16995921 ] ASF subversion and git services commented on JUDDI-991: --- Commit e4112296a261249fc41663341933f3a931f5f07c in juddi's branch refs/heads/feature/JUDDI-991 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=e411229 ] JUDDI-991 progress with cxf upgrade > JUDDI Uses EOL Version of Apache CXF > > > Key: JUDDI-991 > URL: https://issues.apache.org/jira/browse/JUDDI-991 > Project: jUDDI > Issue Type: Bug > Components: CXF >Affects Versions: 3.3.5 >Reporter: Mark Kloepping >Assignee: Alex O'Ree >Priority: Major > Labels: security > Fix For: 3.3.7 > > > JUDDI uses Apache CXF version 2.7.18 which is an End of Life (EOL) version of > the library. > "Versions of CXF prior to 3.1.x are no longer supported at Apache. They are > now considered end-of-life and are therefore unsupported. Users are highly > encouraged to [migrate|http://cxf.apache.org/docs/migration-guides.html] to > newer versions of CXF." ref: [http://cxf.apache.org/roadmap.html] > Hopefully a future release to JUDDI can include a more recent and supported > version of Apache CXF. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF
[ https://issues.apache.org/jira/browse/JUDDI-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995922#comment-16995922 ] ASF subversion and git services commented on JUDDI-991: --- Commit 8016bf340db08da87391129cfec23a59b1473691 in juddi's branch refs/heads/feature/JUDDI-991 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=8016bf3 ] Merge branch 'master' into feature/JUDDI-991 > JUDDI Uses EOL Version of Apache CXF > > > Key: JUDDI-991 > URL: https://issues.apache.org/jira/browse/JUDDI-991 > Project: jUDDI > Issue Type: Bug > Components: CXF >Affects Versions: 3.3.5 >Reporter: Mark Kloepping >Assignee: Alex O'Ree >Priority: Major > Labels: security > Fix For: 3.3.7 > > > JUDDI uses Apache CXF version 2.7.18 which is an End of Life (EOL) version of > the library. > "Versions of CXF prior to 3.1.x are no longer supported at Apache. They are > now considered end-of-life and are therefore unsupported. Users are highly > encouraged to [migrate|http://cxf.apache.org/docs/migration-guides.html] to > newer versions of CXF." ref: [http://cxf.apache.org/roadmap.html] > Hopefully a future release to JUDDI can include a more recent and supported > version of Apache CXF. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-1000) Update embedded tomcat to the latest version available
[ https://issues.apache.org/jira/browse/JUDDI-1000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995883#comment-16995883 ] ASF subversion and git services commented on JUDDI-1000: Commit bec02735c517deb20c54f1b2804add40216f3055 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=bec0273 ] JUDDI-1000 resolved > Update embedded tomcat to the latest version available > -- > > Key: JUDDI-1000 > URL: https://issues.apache.org/jira/browse/JUDDI-1000 > Project: jUDDI > Issue Type: Improvement > Components: juddi-tomcat >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Minor > Fix For: 3.3.7 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000)
[
https://issues.apache.org/jira/browse/JUDDI-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995854#comment-16995854
]
ASF subversion and git services commented on JUDDI-999:
---
Commit 854d5708bed7f025613916c182db9bbc879ba6cb in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=854d570 ]
JUDDI-999 merging
> Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000)
> ---
>
> Key: JUDDI-999
> URL: https://issues.apache.org/jira/browse/JUDDI-999
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6
>Reporter: Rahul S
>Assignee: Alex O'Ree
>Priority: Major
> Labels: jUDDI, juddi
> Fix For: 3.3.7
>
> Attachments: juddi-core-3.3.7-SNAPSHOT.jar,
> juddi-core-openjpa-3.3.7-SNAPSHOT.jar
>
>
> We were using SQLServer with JUDDI 3.0.4. It is working fine so far.
> Now, we are trying to move to JUDDI version 3.3.6. We are encountering
> following issue on start-up.
> {code:java}
> Caused by:
> org.apache.openjpa.persistence.PersistenceException: The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info (id BIGINT NOT
> NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255) NOT NULL,
> entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131,
> state=S0002]Caused by:
> org.apache.openjpa.persistence.PersistenceException: The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info (id BIGINT NOT
> NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255) NOT NULL,
> entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131, state=S0002]
> at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:559) at
> org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:455) at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:160)
> at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:164)
> at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newBrokerImpl(JDBCBrokerFactory.java:122)
> at
> org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:209)
> at
> org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:155)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:226)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:153)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:59)
> at
> org.apache.juddi.config.PersistenceManager.getEntityManager(PersistenceManager.java:48)
> at
> org.apache.juddi.config.AppConfig.getPersistentConfiguration(AppConfig.java:174)
> at org.apache.juddi.config.AppConfig.loadConfiguration(AppConfig.java:160)
> at org.apache.juddi.config.AppConfig.(AppConfig.java:82) at
> org.apache.juddi.config.AppConfig.getInstance(AppConfig.java:272) at
> org.apache.juddi.config.AppConfig.getConfiguration(AppConfig.java:298) at
> org.apache.juddi.api.impl.AuthenticatedService.(AuthenticatedService.java:75)
> at org.apache.juddi.api.impl.UDDIInquiryImpl.(UDDIInquiryImpl.java:88)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at
> java.lang.reflect.Constructor.newInstance(Unknown Source) at
> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:142) ...
> 36 moreCaused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: The size
> (8192) given to the column 'instance_parms' exceeds the maximum allowed for
> any data type (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info
> (id BIGINT NOT NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255)
> NOT NULL, entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131,
> state=S0002] at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:203)
> at
>
[jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000)
[
https://issues.apache.org/jira/browse/JUDDI-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995850#comment-16995850
]
ASF subversion and git services commented on JUDDI-999:
---
Commit 539b31b8d2d7e7e6db13814943eec80cef3f3c4c in juddi's branch
refs/heads/bug/JUDDI-999 from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=539b31b ]
JUDDI-999 fix for mssql issue with tmodelinstanceinfo varchar being too big
> Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000)
> ---
>
> Key: JUDDI-999
> URL: https://issues.apache.org/jira/browse/JUDDI-999
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-tomcat
>Affects Versions: 3.3.6
>Reporter: Rahul S
>Assignee: Alex O'Ree
>Priority: Major
> Labels: jUDDI, juddi
> Fix For: 3.3.7
>
> Attachments: juddi-core-3.3.7-SNAPSHOT.jar,
> juddi-core-openjpa-3.3.7-SNAPSHOT.jar
>
>
> We were using SQLServer with JUDDI 3.0.4. It is working fine so far.
> Now, we are trying to move to JUDDI version 3.3.6. We are encountering
> following issue on start-up.
> {code:java}
> Caused by:
> org.apache.openjpa.persistence.PersistenceException: The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info (id BIGINT NOT
> NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255) NOT NULL,
> entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131,
> state=S0002]Caused by:
> org.apache.openjpa.persistence.PersistenceException: The size (8192) given to
> the column 'instance_parms' exceeds the maximum allowed for any data type
> (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info (id BIGINT NOT
> NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255) NOT NULL,
> entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131, state=S0002]
> at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:559) at
> org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:455) at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:160)
> at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:164)
> at
> org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newBrokerImpl(JDBCBrokerFactory.java:122)
> at
> org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:209)
> at
> org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:155)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:226)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:153)
> at
> org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:59)
> at
> org.apache.juddi.config.PersistenceManager.getEntityManager(PersistenceManager.java:48)
> at
> org.apache.juddi.config.AppConfig.getPersistentConfiguration(AppConfig.java:174)
> at org.apache.juddi.config.AppConfig.loadConfiguration(AppConfig.java:160)
> at org.apache.juddi.config.AppConfig.(AppConfig.java:82) at
> org.apache.juddi.config.AppConfig.getInstance(AppConfig.java:272) at
> org.apache.juddi.config.AppConfig.getConfiguration(AppConfig.java:298) at
> org.apache.juddi.api.impl.AuthenticatedService.(AuthenticatedService.java:75)
> at org.apache.juddi.api.impl.UDDIInquiryImpl.(UDDIInquiryImpl.java:88)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at
> java.lang.reflect.Constructor.newInstance(Unknown Source) at
> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:142) ...
> 36 moreCaused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: The size
> (8192) given to the column 'instance_parms' exceeds the maximum allowed for
> any data type (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info
> (id BIGINT NOT NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255)
> NOT NULL, entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131,
> state=S0002] at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
> at
> org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:203)
> at
>
[jira] [Commented] (JUDDI-558) Access Control Enhancements
[ https://issues.apache.org/jira/browse/JUDDI-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995148#comment-16995148 ] ASF subversion and git services commented on JUDDI-558: --- Commit d352ac0aa6118934bd5bab204ea14dec873651c6 in juddi's branch refs/heads/feature/JUDDI-558 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=d352ac0 ] JUDDI-558 processing with enhanced security, still has lots of unit test failures, work in progress > Access Control Enhancements > --- > > Key: JUDDI-558 > URL: https://issues.apache.org/jira/browse/JUDDI-558 > Project: jUDDI > Issue Type: Improvement > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.4 > > Attachments: UDDI Access Control Proposal.pdf, access control > enhancements incomplete.patch > > > Implementation of revised access control mechanism that enables basic CRUD > access control lists on a per business, per service basis with inheritable > controls from a parent object -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-558) Access Control Enhancements
[ https://issues.apache.org/jira/browse/JUDDI-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16995149#comment-16995149 ] ASF subversion and git services commented on JUDDI-558: --- Commit 56fb8a92c1ee463ec166b386d9642cd3453d184d in juddi's branch refs/heads/feature/JUDDI-558 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=56fb8a9 ] JUDDI-558 WIP > Access Control Enhancements > --- > > Key: JUDDI-558 > URL: https://issues.apache.org/jira/browse/JUDDI-558 > Project: jUDDI > Issue Type: Improvement > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.4 > > Attachments: UDDI Access Control Proposal.pdf, access control > enhancements incomplete.patch > > > Implementation of revised access control mechanism that enables basic CRUD > access control lists on a per business, per service basis with inheritable > controls from a parent object -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-558) Access Control Enhancements
[ https://issues.apache.org/jira/browse/JUDDI-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873672#comment-16873672 ] ASF subversion and git services commented on JUDDI-558: --- Commit 4c90588d54defbb0cdaf7faf5abd5dac6754fe11 in juddi's branch refs/heads/feature/JUDDI-558 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=4c90588 ] JUDDI-558 amother interface change to better handling the filtering of publisher assertions > Access Control Enhancements > --- > > Key: JUDDI-558 > URL: https://issues.apache.org/jira/browse/JUDDI-558 > Project: jUDDI > Issue Type: Improvement > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.4 > > Attachments: UDDI Access Control Proposal.pdf, access control > enhancements incomplete.patch > > > Implementation of revised access control mechanism that enables basic CRUD > access control lists on a per business, per service basis with inheritable > controls from a parent object -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JUDDI-558) Access Control Enhancements
[ https://issues.apache.org/jira/browse/JUDDI-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873636#comment-16873636 ] ASF subversion and git services commented on JUDDI-558: --- Commit a3cf0c6de7e326e7c1b70586fb9d112a3a43be65 in juddi's branch refs/heads/feature/JUDDI-558 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=a3cf0c6 ] [JUDDI-558] inquiry service now filters requst data. can now get/set permissions, however only the read access permission is current implemented. api is still evolving > Access Control Enhancements > --- > > Key: JUDDI-558 > URL: https://issues.apache.org/jira/browse/JUDDI-558 > Project: jUDDI > Issue Type: Improvement > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.4 > > Attachments: UDDI Access Control Proposal.pdf, access control > enhancements incomplete.patch > > > Implementation of revised access control mechanism that enables basic CRUD > access control lists on a per business, per service basis with inheritable > controls from a parent object -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JUDDI-558) Access Control Enhancements
[ https://issues.apache.org/jira/browse/JUDDI-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873635#comment-16873635 ] ASF subversion and git services commented on JUDDI-558: --- Commit 428071de42426fd4794befe91ae7665f02d43cb7 in juddi's branch refs/heads/feature/JUDDI-558 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=428071d ] Merge branch 'master' into feature/JUDDI-558 > Access Control Enhancements > --- > > Key: JUDDI-558 > URL: https://issues.apache.org/jira/browse/JUDDI-558 > Project: jUDDI > Issue Type: Improvement > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.4 > > Attachments: UDDI Access Control Proposal.pdf, access control > enhancements incomplete.patch > > > Implementation of revised access control mechanism that enables basic CRUD > access control lists on a per business, per service basis with inheritable > controls from a parent object -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JUDDI-996) Admin gui, get all client subscriptions throws a classcast error
[ https://issues.apache.org/jira/browse/JUDDI-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16873634#comment-16873634 ] ASF subversion and git services commented on JUDDI-996: --- Commit 74e4985301ed7444f649f2e55cd2391a59acae99 in juddi's branch refs/heads/feature/JUDDI-558 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=74e4985 ] JUDDI-996 fixed with tests > Admin gui, get all client subscriptions throws a classcast error > > > Key: JUDDI-996 > URL: https://issues.apache.org/jira/browse/JUDDI-996 > Project: jUDDI > Issue Type: Bug > Components: juddi-gui >Affects Versions: 3.2.1, 3.3, 3.3.1, 3.3.2, 3.3.3, 3.3.4, 3.3.5, 3.3.6 >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.7 > > > Error org.apache.juddi.model.ReplicationConfiguration cannot be cast to > org.apache.juddi.model.Subscription > > java.lang.ClassCastException: org.apache.juddi.model.ReplicationConfiguration > cannot be cast to org.apache.juddi.model.Subscription > at > org.apache.juddi.api.impl.JUDDIApiImpl.getAllClientSubscriptionInfo(JUDDIApiImpl.java:1333) > at > org.apache.juddi.adminconsole.hub.UddiAdminHub.getAllClientSubscriptionInfo(UddiAdminHub.java:597) > at > org.apache.juddi.adminconsole.hub.UddiAdminHub.go(UddiAdminHub.java:409) > at org.apache.jsp.admin.ajax.go_jsp._jspService(go_jsp.java:227) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JUDDI-997) Admin gui has strange behavior and no feedback if the login fails
[ https://issues.apache.org/jira/browse/JUDDI-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869097#comment-16869097 ] ASF subversion and git services commented on JUDDI-997: --- Commit c64ec446760f5efec489c3a967388145c98b2973 in juddi's branch refs/heads/feature/JUDDI-558 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=c64ec44 ] JUDDI-997 made some minor changes, should resolve this > Admin gui has strange behavior and no feedback if the login fails > - > > Key: JUDDI-997 > URL: https://issues.apache.org/jira/browse/JUDDI-997 > Project: jUDDI > Issue Type: Bug > Components: juddi-gui >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Minor > > javascrpt error i18n_loading not defined... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JUDDI-996) Admin gui, get all client subscriptions throws a classcast error
[ https://issues.apache.org/jira/browse/JUDDI-996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869080#comment-16869080 ] ASF subversion and git services commented on JUDDI-996: --- Commit 74e4985301ed7444f649f2e55cd2391a59acae99 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=74e4985 ] JUDDI-996 fixed with tests > Admin gui, get all client subscriptions throws a classcast error > > > Key: JUDDI-996 > URL: https://issues.apache.org/jira/browse/JUDDI-996 > Project: jUDDI > Issue Type: Bug >Affects Versions: 3.3.6 >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.7 > > > Error org.apache.juddi.model.ReplicationConfiguration cannot be cast to > org.apache.juddi.model.Subscription > > java.lang.ClassCastException: org.apache.juddi.model.ReplicationConfiguration > cannot be cast to org.apache.juddi.model.Subscription > at > org.apache.juddi.api.impl.JUDDIApiImpl.getAllClientSubscriptionInfo(JUDDIApiImpl.java:1333) > at > org.apache.juddi.adminconsole.hub.UddiAdminHub.getAllClientSubscriptionInfo(UddiAdminHub.java:597) > at > org.apache.juddi.adminconsole.hub.UddiAdminHub.go(UddiAdminHub.java:409) > at org.apache.jsp.admin.ajax.go_jsp._jspService(go_jsp.java:227) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JUDDI-558) Access Control Enhancements
[ https://issues.apache.org/jira/browse/JUDDI-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16869059#comment-16869059 ] ASF subversion and git services commented on JUDDI-558: --- Commit 72f163f5334e873b97e757797a26c2e8a052a5ae in juddi's branch refs/heads/feature/JUDDI-558 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=72f163f ] JUDDI-558 with the correct ticket number this time...some progess...still doesn't really work yet > Access Control Enhancements > --- > > Key: JUDDI-558 > URL: https://issues.apache.org/jira/browse/JUDDI-558 > Project: jUDDI > Issue Type: Improvement > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.4 > > Attachments: UDDI Access Control Proposal.pdf, access control > enhancements incomplete.patch > > > Implementation of revised access control mechanism that enables basic CRUD > access control lists on a per business, per service basis with inheritable > controls from a parent object -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JUDDI-995) Add automated generation of sha512 hashes during the build
[ https://issues.apache.org/jira/browse/JUDDI-995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16764598#comment-16764598 ] ASF subversion and git services commented on JUDDI-995: --- Commit e42cd72767797606fc51ec092356601a2c45b513 in juddi's branch refs/heads/master from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=e42cd72 ] JUDDI-995 automated sha512 checksums > Add automated generation of sha512 hashes during the build > -- > > Key: JUDDI-995 > URL: https://issues.apache.org/jira/browse/JUDDI-995 > Project: jUDDI > Issue Type: Improvement > Components: build >Reporter: Alex O'Ree >Priority: Minor > > the asf release guys want us to use a strong hash mechanism. found a plugin > that will auto generate it -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JUDDI-994) Bash scripts containing windows CRLF line endings
[ https://issues.apache.org/jira/browse/JUDDI-994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16705863#comment-16705863 ] ASF subversion and git services commented on JUDDI-994: --- Commit 96a502b5911e4146ef98d00f4bfe99f127959932 in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=96a502b ] JUDDI-994 > Bash scripts containing windows CRLF line endings > - > > Key: JUDDI-994 > URL: https://issues.apache.org/jira/browse/JUDDI-994 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Priority: Major > Fix For: 3.3.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JUDDI-992) FindBinding API call doesn't exactly match the spec
[ https://issues.apache.org/jira/browse/JUDDI-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16690991#comment-16690991 ] ASF subversion and git services commented on JUDDI-992: --- Commit 2f5a2492e49a64da73e29bc5ba0a8bf151b49bdb in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=2f5a249 ] JUDDI-992 fix for several issues with find binding with and without the service key. Also had to do some light refactoring of List to List for many of the apis in juddi-core. Shouldn't effect too many users. > FindBinding API call doesn't exactly match the spec > --- > > Key: JUDDI-992 > URL: https://issues.apache.org/jira/browse/JUDDI-992 > Project: jUDDI > Issue Type: Bug > Components: core >Reporter: Alex O'Ree >Priority: Major > > this appears to affect most versions starting with 3.1.5 and newer > The spec isn't exactly clear on what the expected behavior is supposed to be > in the case when nothing is specified except for the service key in a > findBinding api call. The most logical thing is to return all bindings for > that service. The current version of juddi throws an exception stating that > it is not a valid request. According to the spec, it looks like it is. The > spec actually doesn't really specify what isn't valid except for conflicting > find qualifiers > > Example XML request that fits this profile > > xmlns:ns2="http://www.w3.org/2000/09/xmldsig#; maxRows="10" > serviceKey="uddi:juddi.apache.org:4ff68cf9-0463-45c4-bb9e-5a12f321a9c1">sortByNameAscapproximateMatch > > This was discovered in trying to bring Apache Scout up to current jUDDI API > levels and debugging unit test failures against 3.3.5. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JUDDI-988) Update to tomcat 9
[ https://issues.apache.org/jira/browse/JUDDI-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16592729#comment-16592729 ] ASF subversion and git services commented on JUDDI-988: --- Commit be925ac62748a7341024efca96ecef32a8f9b117 in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=be925ac ] JUDDI-988 a remaining tomcat9 update issue related to context.xml > Update to tomcat 9 > -- > > Key: JUDDI-988 > URL: https://issues.apache.org/jira/browse/JUDDI-988 > Project: jUDDI > Issue Type: Improvement > Components: juddi-tomcat >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.6 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JUDDI-987) CVE-2018-1307 XML Entity Expansion
[ https://issues.apache.org/jira/browse/JUDDI-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16358615#comment-16358615 ] ASF subversion and git services commented on JUDDI-987: --- Commit 442fb55723cf1af1490395b2b005e787026801b3 in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=442fb55 ] JUDDI-987 adding security advisory > CVE-2018-1307 XML Entity Expansion > -- > > Key: JUDDI-987 > URL: https://issues.apache.org/jira/browse/JUDDI-987 > Project: jUDDI > Issue Type: Bug > Components: core >Affects Versions: 3.2, 3.2.1, 3.3, 3.3.1, 3.3.2, 3.3.3, 3.3.4 >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.5 > > > CVEID CVE-2018-1307 > > VERSION: 3.2 through 3.3.4 > > PROBLEMTYPE: XML Entity Expansion > > REFERENCES: [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-4267] > > DISCRIPTION: If using the WADL2Java or WSDL2Java classes, which parse a local > or remote XML document and then mediates the data structures into UDDI data > structures, there are little protections present against entity expansion and > DTD type of attacks. This was fixed with > https://issues.apache.org/jira/browse/JUDDI-987 > > Severity: Moderate > > Mitigation: > > Update your juddi-client dependencies to 3.3.5 or newer and/or discontinue > use of the effected classes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (JUDDI-988) Update to tomcat 8
[ https://issues.apache.org/jira/browse/JUDDI-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16258083#comment-16258083 ] ASF subversion and git services commented on JUDDI-988: --- Commit cb163b2dab599ee7610150f45f1ac82641c42621 in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=cb163b2 ] JUDDI-988 rolling back the tomcat8 updates, too many issues with slow startup and tld scans, cleaning up pom version settings and updating the changelog > Update to tomcat 8 > --- > > Key: JUDDI-988 > URL: https://issues.apache.org/jira/browse/JUDDI-988 > Project: jUDDI > Issue Type: Improvement > Components: juddi-tomcat >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.4 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-988) Update to tomcat 8
[ https://issues.apache.org/jira/browse/JUDDI-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257769#comment-16257769 ] ASF subversion and git services commented on JUDDI-988: --- Commit 15d3c0d7b43071e9e3ef59cf7f980a119d87669e in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=15d3c0d ] NOJIRA reverting back to version 3.3.5-SNAPSHOT JUDDI-989 fixing line endings JUDDI-988 updating to tomcat8 > Update to tomcat 8 > --- > > Key: JUDDI-988 > URL: https://issues.apache.org/jira/browse/JUDDI-988 > Project: jUDDI > Issue Type: Improvement > Components: juddi-tomcat >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-989) catalina.sh start script needs to remove DOS line endings
[ https://issues.apache.org/jira/browse/JUDDI-989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16257768#comment-16257768 ] ASF subversion and git services commented on JUDDI-989: --- Commit 15d3c0d7b43071e9e3ef59cf7f980a119d87669e in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=15d3c0d ] NOJIRA reverting back to version 3.3.5-SNAPSHOT JUDDI-989 fixing line endings JUDDI-988 updating to tomcat8 > catalina.sh start script needs to remove DOS line endings > - > > Key: JUDDI-989 > URL: https://issues.apache.org/jira/browse/JUDDI-989 > Project: jUDDI > Issue Type: Bug > Components: build >Reporter: Tom Cunningham >Assignee: Alex O'Ree > Fix For: 3.3.5 > > > lilguylaptop:bin cunningt$ ./catalina.sh start > -bash: ./catalina.sh: /bin/sh^M: bad interpreter: No such file or directory > If I run dos2unix on catalina.sh, juddi starts and I see no errors. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-985) Replication change record delete fails with hibernate
[ https://issues.apache.org/jira/browse/JUDDI-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214494#comment-16214494 ] ASF subversion and git services commented on JUDDI-985: --- Commit 9c3336041f310ebd965d11d172ca50d0bd0b75ff in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=9c33360 ] JUDDI-985 potential fix for hibernate issues JUDDI-978 potential fix for ci test failures with hibernate JUDDI-986 hibernate dependencies updated > Replication change record delete fails with hibernate > - > > Key: JUDDI-985 > URL: https://issues.apache.org/jira/browse/JUDDI-985 > Project: jUDDI > Issue Type: Bug > Components: core >Affects Versions: 3.3, 3.3.1, 3.3.2, 3.3.3, 3.3.4 >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > > a-4321-969f-827a4cc1d175-0 Local id from sender:294 > 2017-10-22 11:20:19,660 WARN [org.apache.juddi.api.impl.AuthenticatedService] > - Error applying the change record! > java.lang.IllegalArgumentException: id to load is required for loading > at org.hibernate.event.spi.LoadEvent.(LoadEvent.java:109) > at org.hibernate.event.spi.LoadEvent.(LoadEvent.java:79) > at > org.hibernate.internal.SessionImpl$IdentifierLoadAccessImpl.load(SessionImpl.java:2446) > at org.hibernate.internal.SessionImpl.get(SessionImpl.java:949) > at > org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:807) > at > org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:781) > at > org.apache.juddi.api.impl.UDDIReplicationImpl$PullTimerTask.PersistChangeRecord(UDDIReplicationImpl.java:372) > at > org.apache.juddi.api.impl.UDDIReplicationImpl$PullTimerTask.run(UDDIReplicationImpl.java:276) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > 2017-10-22 11:20:19,660 WARN [org.apache.juddi.api.impl.AuthenticatedService] > - This is the record that failed to persist: encoding="UTF-8" standalone="yes"?> > xmlns:ns2="urn:uddi-org:api_v3" > xmlns:ns3="http://www.w3.org/2000/09/xmldsig#;> > > uddi:juddi.apache.org:node1 > 145 > > > a0dbe2d4-3eea-4321-969f-827a4cc1d175-0 > 2017-10-22T11:20:09.961-04:00 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-986) Update hibernate dependencies
[ https://issues.apache.org/jira/browse/JUDDI-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214496#comment-16214496 ] ASF subversion and git services commented on JUDDI-986: --- Commit 9c3336041f310ebd965d11d172ca50d0bd0b75ff in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=9c33360 ] JUDDI-985 potential fix for hibernate issues JUDDI-978 potential fix for ci test failures with hibernate JUDDI-986 hibernate dependencies updated > Update hibernate dependencies > - > > Key: JUDDI-986 > URL: https://issues.apache.org/jira/browse/JUDDI-986 > Project: jUDDI > Issue Type: Improvement > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-985) Replication change record delete fails with hibernate
[ https://issues.apache.org/jira/browse/JUDDI-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214497#comment-16214497 ] ASF subversion and git services commented on JUDDI-985: --- Commit 79f0ab8c9841367e546251ac606f7335bed92529 in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=79f0ab8 ] JUDDI-985 updating the ddl generator after the hibernate update > Replication change record delete fails with hibernate > - > > Key: JUDDI-985 > URL: https://issues.apache.org/jira/browse/JUDDI-985 > Project: jUDDI > Issue Type: Bug > Components: core >Affects Versions: 3.3, 3.3.1, 3.3.2, 3.3.3, 3.3.4 >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > > a-4321-969f-827a4cc1d175-0 Local id from sender:294 > 2017-10-22 11:20:19,660 WARN [org.apache.juddi.api.impl.AuthenticatedService] > - Error applying the change record! > java.lang.IllegalArgumentException: id to load is required for loading > at org.hibernate.event.spi.LoadEvent.(LoadEvent.java:109) > at org.hibernate.event.spi.LoadEvent.(LoadEvent.java:79) > at > org.hibernate.internal.SessionImpl$IdentifierLoadAccessImpl.load(SessionImpl.java:2446) > at org.hibernate.internal.SessionImpl.get(SessionImpl.java:949) > at > org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:807) > at > org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:781) > at > org.apache.juddi.api.impl.UDDIReplicationImpl$PullTimerTask.PersistChangeRecord(UDDIReplicationImpl.java:372) > at > org.apache.juddi.api.impl.UDDIReplicationImpl$PullTimerTask.run(UDDIReplicationImpl.java:276) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > 2017-10-22 11:20:19,660 WARN [org.apache.juddi.api.impl.AuthenticatedService] > - This is the record that failed to persist: encoding="UTF-8" standalone="yes"?> > xmlns:ns2="urn:uddi-org:api_v3" > xmlns:ns3="http://www.w3.org/2000/09/xmldsig#;> > > uddi:juddi.apache.org:node1 > 145 > > > a0dbe2d4-3eea-4321-969f-827a4cc1d175-0 > 2017-10-22T11:20:09.961-04:00 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-978) Build instability with Replication tests
[ https://issues.apache.org/jira/browse/JUDDI-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214495#comment-16214495 ] ASF subversion and git services commented on JUDDI-978: --- Commit 9c3336041f310ebd965d11d172ca50d0bd0b75ff in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=9c33360 ] JUDDI-985 potential fix for hibernate issues JUDDI-978 potential fix for ci test failures with hibernate JUDDI-986 hibernate dependencies updated > Build instability with Replication tests > > > Key: JUDDI-978 > URL: https://issues.apache.org/jira/browse/JUDDI-978 > Project: jUDDI > Issue Type: Bug > Components: core, uddi-tck >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > > There were some changes made between 3.3.3 and 3.3.4 which continue until > this day that may cause test instability of juddi. From what i can, the > product itself isn't affected by this, however the fact that they are failing > bother me -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-985) Replication change record delete fails with hibernate
[ https://issues.apache.org/jira/browse/JUDDI-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214493#comment-16214493 ] ASF subversion and git services commented on JUDDI-985: --- Commit 79f0ab8c9841367e546251ac606f7335bed92529 in juddi's branch refs/heads/feature/JUDDI-985 from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=79f0ab8 ] JUDDI-985 updating the ddl generator after the hibernate update > Replication change record delete fails with hibernate > - > > Key: JUDDI-985 > URL: https://issues.apache.org/jira/browse/JUDDI-985 > Project: jUDDI > Issue Type: Bug > Components: core >Affects Versions: 3.3, 3.3.1, 3.3.2, 3.3.3, 3.3.4 >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > > a-4321-969f-827a4cc1d175-0 Local id from sender:294 > 2017-10-22 11:20:19,660 WARN [org.apache.juddi.api.impl.AuthenticatedService] > - Error applying the change record! > java.lang.IllegalArgumentException: id to load is required for loading > at org.hibernate.event.spi.LoadEvent.(LoadEvent.java:109) > at org.hibernate.event.spi.LoadEvent.(LoadEvent.java:79) > at > org.hibernate.internal.SessionImpl$IdentifierLoadAccessImpl.load(SessionImpl.java:2446) > at org.hibernate.internal.SessionImpl.get(SessionImpl.java:949) > at > org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:807) > at > org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:781) > at > org.apache.juddi.api.impl.UDDIReplicationImpl$PullTimerTask.PersistChangeRecord(UDDIReplicationImpl.java:372) > at > org.apache.juddi.api.impl.UDDIReplicationImpl$PullTimerTask.run(UDDIReplicationImpl.java:276) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > 2017-10-22 11:20:19,660 WARN [org.apache.juddi.api.impl.AuthenticatedService] > - This is the record that failed to persist: encoding="UTF-8" standalone="yes"?> > xmlns:ns2="urn:uddi-org:api_v3" > xmlns:ns3="http://www.w3.org/2000/09/xmldsig#;> > > uddi:juddi.apache.org:node1 > 145 > > > a0dbe2d4-3eea-4321-969f-827a4cc1d175-0 > 2017-10-22T11:20:09.961-04:00 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-985) Replication change record delete fails with hibernate
[ https://issues.apache.org/jira/browse/JUDDI-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214439#comment-16214439 ] ASF subversion and git services commented on JUDDI-985: --- Commit 9c3336041f310ebd965d11d172ca50d0bd0b75ff in juddi's branch refs/heads/feature/JUDDI-985 from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=9c33360 ] JUDDI-985 potential fix for hibernate issues JUDDI-978 potential fix for ci test failures with hibernate JUDDI-986 hibernate dependencies updated > Replication change record delete fails with hibernate > - > > Key: JUDDI-985 > URL: https://issues.apache.org/jira/browse/JUDDI-985 > Project: jUDDI > Issue Type: Bug > Components: core >Affects Versions: 3.3, 3.3.1, 3.3.2, 3.3.3, 3.3.4 >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > > a-4321-969f-827a4cc1d175-0 Local id from sender:294 > 2017-10-22 11:20:19,660 WARN [org.apache.juddi.api.impl.AuthenticatedService] > - Error applying the change record! > java.lang.IllegalArgumentException: id to load is required for loading > at org.hibernate.event.spi.LoadEvent.(LoadEvent.java:109) > at org.hibernate.event.spi.LoadEvent.(LoadEvent.java:79) > at > org.hibernate.internal.SessionImpl$IdentifierLoadAccessImpl.load(SessionImpl.java:2446) > at org.hibernate.internal.SessionImpl.get(SessionImpl.java:949) > at > org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:807) > at > org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:781) > at > org.apache.juddi.api.impl.UDDIReplicationImpl$PullTimerTask.PersistChangeRecord(UDDIReplicationImpl.java:372) > at > org.apache.juddi.api.impl.UDDIReplicationImpl$PullTimerTask.run(UDDIReplicationImpl.java:276) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > 2017-10-22 11:20:19,660 WARN [org.apache.juddi.api.impl.AuthenticatedService] > - This is the record that failed to persist: encoding="UTF-8" standalone="yes"?> > xmlns:ns2="urn:uddi-org:api_v3" > xmlns:ns3="http://www.w3.org/2000/09/xmldsig#;> > > uddi:juddi.apache.org:node1 > 145 > > > a0dbe2d4-3eea-4321-969f-827a4cc1d175-0 > 2017-10-22T11:20:09.961-04:00 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-986) Update hibernate dependencies
[ https://issues.apache.org/jira/browse/JUDDI-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214441#comment-16214441 ] ASF subversion and git services commented on JUDDI-986: --- Commit 9c3336041f310ebd965d11d172ca50d0bd0b75ff in juddi's branch refs/heads/feature/JUDDI-985 from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=9c33360 ] JUDDI-985 potential fix for hibernate issues JUDDI-978 potential fix for ci test failures with hibernate JUDDI-986 hibernate dependencies updated > Update hibernate dependencies > - > > Key: JUDDI-986 > URL: https://issues.apache.org/jira/browse/JUDDI-986 > Project: jUDDI > Issue Type: Improvement > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-978) Build instability with Replication tests
[ https://issues.apache.org/jira/browse/JUDDI-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214440#comment-16214440 ] ASF subversion and git services commented on JUDDI-978: --- Commit 9c3336041f310ebd965d11d172ca50d0bd0b75ff in juddi's branch refs/heads/feature/JUDDI-985 from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=9c33360 ] JUDDI-985 potential fix for hibernate issues JUDDI-978 potential fix for ci test failures with hibernate JUDDI-986 hibernate dependencies updated > Build instability with Replication tests > > > Key: JUDDI-978 > URL: https://issues.apache.org/jira/browse/JUDDI-978 > Project: jUDDI > Issue Type: Bug > Components: core, uddi-tck >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > > There were some changes made between 3.3.3 and 3.3.4 which continue until > this day that may cause test instability of juddi. From what i can, the > product itself isn't affected by this, however the fact that they are failing > bother me -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-984) Hibernate profile fails to deploy due to extraneous class in the orm xml file
[ https://issues.apache.org/jira/browse/JUDDI-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16214350#comment-16214350 ] ASF subversion and git services commented on JUDDI-984: --- Commit 1461a0cc2483a9ac34de1fe1175c965b5dea8e5f in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=1461a0c ] JUDDI-984 Hibernate profile fails to deploy due to extraneous class in the orm xml file NOJIRA pom cleanup > Hibernate profile fails to deploy due to extraneous class in the orm xml file > - > > Key: JUDDI-984 > URL: https://issues.apache.org/jira/browse/JUDDI-984 > Project: jUDDI > Issue Type: Bug > Components: core >Affects Versions: 3.3, 3.3.1, 3.3.2, 3.3.3, 3.3.4 >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-983) Unable to compile under centos, openjdk8, sun.security.provider.certpath.OCSP api mismatch
[ https://issues.apache.org/jira/browse/JUDDI-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205130#comment-16205130 ] ASF subversion and git services commented on JUDDI-983: --- Commit af452e119631055c5e9a1d5bdc136af46f5bede0 in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=af452e1 ] JUDDI-983 potential fix for api deltas > Unable to compile under centos, openjdk8, sun.security.provider.certpath.OCSP > api mismatch > -- > > Key: JUDDI-983 > URL: https://issues.apache.org/jira/browse/JUDDI-983 > Project: jUDDI > Issue Type: Bug > Components: juddi-client >Reporter: Alex O'Ree >Assignee: Alex O'Ree > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-980) Update juddi's parent pom to the latest apache pom
[ https://issues.apache.org/jira/browse/JUDDI-980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16205103#comment-16205103 ] ASF subversion and git services commented on JUDDI-980: --- Commit caacbf7d40836f7e5e96f980561602776bb5adca in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=caacbf7 ] JUDDI-980 parent pom update > Update juddi's parent pom to the latest apache pom > -- > > Key: JUDDI-980 > URL: https://issues.apache.org/jira/browse/JUDDI-980 > Project: jUDDI > Issue Type: Improvement > Components: build >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Minor > Fix For: 3.3.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-981) Force all tests to run in a random order
[ https://issues.apache.org/jira/browse/JUDDI-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204988#comment-16204988 ] ASF subversion and git services commented on JUDDI-981: --- Commit 57e180549df51873b1217b17dab681afbd9049e0 in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=57e1805 ] JUDDI-981 attempting to fix build issues on bb > Force all tests to run in a random order > > > Key: JUDDI-981 > URL: https://issues.apache.org/jira/browse/JUDDI-981 > Project: jUDDI > Issue Type: Improvement > Components: build, uddi-tck >Reporter: Alex O'Ree >Assignee: Alex O'Ree > > The seemingly random test failures in certain environment can probably be > caught earlier if we enable randomization of the test build order. There's > most likely some test that is not cleaning up after itself. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-981) Force all tests to run in a random order
[ https://issues.apache.org/jira/browse/JUDDI-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204869#comment-16204869 ] ASF subversion and git services commented on JUDDI-981: --- Commit ee347328e430b966c27fc1c65723091e69b6acb4 in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=ee34732 ] JUDDI-983 workaround JUDDI-981 attempting to fix the build > Force all tests to run in a random order > > > Key: JUDDI-981 > URL: https://issues.apache.org/jira/browse/JUDDI-981 > Project: jUDDI > Issue Type: Improvement > Components: build, uddi-tck >Reporter: Alex O'Ree >Assignee: Alex O'Ree > > The seemingly random test failures in certain environment can probably be > caught earlier if we enable randomization of the test build order. There's > most likely some test that is not cleaning up after itself. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-983) Unable to compile under open jdk8, sun.security.provider.certpath.OCSP api mismatch
[ https://issues.apache.org/jira/browse/JUDDI-983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204868#comment-16204868 ] ASF subversion and git services commented on JUDDI-983: --- Commit ee347328e430b966c27fc1c65723091e69b6acb4 in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=ee34732 ] JUDDI-983 workaround JUDDI-981 attempting to fix the build > Unable to compile under open jdk8, sun.security.provider.certpath.OCSP api > mismatch > --- > > Key: JUDDI-983 > URL: https://issues.apache.org/jira/browse/JUDDI-983 > Project: jUDDI > Issue Type: Bug > Components: juddi-client >Reporter: Alex O'Ree > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-981) Force all tests to run in a random order
[ https://issues.apache.org/jira/browse/JUDDI-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16204777#comment-16204777 ] ASF subversion and git services commented on JUDDI-981: --- Commit bfc210ad8553b9bcbf15c153943227b59eeae228 in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=bfc210a ] JUDDI-981 attempting to fix build issues on bb > Force all tests to run in a random order > > > Key: JUDDI-981 > URL: https://issues.apache.org/jira/browse/JUDDI-981 > Project: jUDDI > Issue Type: Improvement > Components: build, uddi-tck >Reporter: Alex O'Ree >Assignee: Alex O'Ree > > The seemingly random test failures in certain environment can probably be > caught earlier if we enable randomization of the test build order. There's > most likely some test that is not cleaning up after itself. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-982) Removing the juddi-client-plugins module
[ https://issues.apache.org/jira/browse/JUDDI-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197880#comment-16197880 ] ASF subversion and git services commented on JUDDI-982: --- Commit 2a8bed4efd34bccb11e0f97192a3e273355ad5fa in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=2a8bed4 ] JUDDI-982 deleting the client plugin module. JUDDI-977 more findbugs fixes > Removing the juddi-client-plugins module > > > Key: JUDDI-982 > URL: https://issues.apache.org/jira/browse/JUDDI-982 > Project: jUDDI > Issue Type: Task > Components: build >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > > in module was added a while ago and was just stubbed out as an example. It > didn't actually have an implementation though so kind of pointless -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-977) reduce findbugs warnings
[ https://issues.apache.org/jira/browse/JUDDI-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197881#comment-16197881 ] ASF subversion and git services commented on JUDDI-977: --- Commit 2a8bed4efd34bccb11e0f97192a3e273355ad5fa in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=2a8bed4 ] JUDDI-982 deleting the client plugin module. JUDDI-977 more findbugs fixes > reduce findbugs warnings > > > Key: JUDDI-977 > URL: https://issues.apache.org/jira/browse/JUDDI-977 > Project: jUDDI > Issue Type: Bug > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-981) Force all tests to run in a random order
[ https://issues.apache.org/jira/browse/JUDDI-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197766#comment-16197766 ] ASF subversion and git services commented on JUDDI-981: --- Commit e2521334f05b05551da024054d9b09d732a18786 in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=e252133 ] JUDDI-981 attempting to fix build issues on bb > Force all tests to run in a random order > > > Key: JUDDI-981 > URL: https://issues.apache.org/jira/browse/JUDDI-981 > Project: jUDDI > Issue Type: Improvement > Components: build, uddi-tck >Reporter: Alex O'Ree >Assignee: Alex O'Ree > > The seemingly random test failures in certain environment can probably be > caught earlier if we enable randomization of the test build order. There's > most likely some test that is not cleaning up after itself. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-981) Force all tests to run in a random order
[ https://issues.apache.org/jira/browse/JUDDI-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197613#comment-16197613 ] ASF subversion and git services commented on JUDDI-981: --- Commit d147fa7496319382fd19c5ebe70fc31855f795a8 in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=d147fa7 ] JUDDI-981 enabled > Force all tests to run in a random order > > > Key: JUDDI-981 > URL: https://issues.apache.org/jira/browse/JUDDI-981 > Project: jUDDI > Issue Type: Improvement > Components: build, uddi-tck >Reporter: Alex O'Ree >Assignee: Alex O'Ree > > The seemingly random test failures in certain environment can probably be > caught earlier if we enable randomization of the test build order. There's > most likely some test that is not cleaning up after itself. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-943) WebHelper class: Client name not set in servletContext after getUDDIClient is called
[
https://issues.apache.org/jira/browse/JUDDI-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16197220#comment-16197220
]
ASF subversion and git services commented on JUDDI-943:
---
Commit 6ea7ff2503c0a536c6f35d6806b114688d7d4063 in juddi's branch
refs/heads/master from [~spyhunter99]
[ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=6ea7ff2 ]
JUDDI-943 fixed
> WebHelper class: Client name not set in servletContext after getUDDIClient is
> called
>
>
> Key: JUDDI-943
> URL: https://issues.apache.org/jira/browse/JUDDI-943
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-client
>Affects Versions: 3.3.1
>Reporter: Matthieu Ghilain
>Assignee: Alex O'Ree
>
> The client name is not set after the method:
> WebHelper.getUDDIClient(servletContext) is called and it seems it should be.
> Because the client name is not set a new UDDI client is returned each time
> the method is called despite the same servletContext is passed.
> The problem is here (from WebHelper class):
> {code}
> if (client.getName()!=null) {
> logger.info("Starting Client " +
> client.getName() + "...");
> } else {
> throw new ConfigurationException("A client name
> needs to be specified in the client config file.");
> }
> {code}
> it should be according to me:
> {code}
> if (client.getName()!=null) {
> logger.info("Starting Client " + client.getName() + "...");
> clientName = client.getName();
> } else {
> throw new ConfigurationException("A client name needs to be specified in
> the client config file.");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
