[jira] [Commented] (JUDDI-990) Find a better solution for in browser digital signatures than a java applet
[ https://issues.apache.org/jira/browse/JUDDI-990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16866653#comment-16866653 ] Kurt T Stam commented on JUDDI-990: --- This would require them to have java installed on their machine right? Maybe we can document how to use gpg commands straight up? > Find a better solution for in browser digital signatures than a java applet > --- > > Key: JUDDI-990 > URL: https://issues.apache.org/jira/browse/JUDDI-990 > Project: jUDDI > Issue Type: Improvement > Components: juddi-gui >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Major > > this might work... > https://github.com/PeculiarVentures/xadesjs -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (JUDDI-840) Fix file authentication
[ https://issues.apache.org/jira/browse/JUDDI-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-840. - > Fix file authentication > --- > > Key: JUDDI-840 > URL: https://issues.apache.org/jira/browse/JUDDI-840 > Project: jUDDI > Issue Type: Bug > Components: core >Affects Versions: 3.2 >Reporter: Kurt T Stam >Assignee: Kurt T Stam > Fix For: 3.2.1 > > > It's not easy to read the juddi-user.xml from the /conf directory. I > think it should be an option to read the users/pw info from the > tomcat-users.xml. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (JUDDI-840) Fix file authentication
[ https://issues.apache.org/jira/browse/JUDDI-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam resolved JUDDI-840. --- Resolution: Fixed Added the ability to specify the full path for the juddi-users.xml file. > Fix file authentication > --- > > Key: JUDDI-840 > URL: https://issues.apache.org/jira/browse/JUDDI-840 > Project: jUDDI > Issue Type: Bug > Components: core >Affects Versions: 3.2 >Reporter: Kurt T Stam >Assignee: Kurt T Stam > Fix For: 3.2.1 > > > It's not easy to read the juddi-user.xml from the /conf directory. I > think it should be an option to read the users/pw info from the > tomcat-users.xml. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (JUDDI-587) JUDDI incompatible with Hibernate 4.1.x and 4.2.x
[
https://issues.apache.org/jira/browse/JUDDI-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kurt T Stam closed JUDDI-587.
-
> JUDDI incompatible with Hibernate 4.1.x and 4.2.x
> -
>
> Key: JUDDI-587
> URL: https://issues.apache.org/jira/browse/JUDDI-587
> Project: jUDDI
> Issue Type: Bug
> Components: core
>Affects Versions: 3.1.4
>Reporter: subes
>Assignee: Kurt T Stam
> Fix For: 3.2.1
>
> Attachments: JUDDI-587-patch.txt
>
>
> JUDDI is affected by the following Bug in Hibernate:
> https://hibernate.atlassian.net/browse/HHH-7630
> {quote}
> Caused by: org.hibernate.HibernateException: Could not locate table which
> owns column [entity_key] referenced in order-by mapping
> at
> org.hibernate.persister.entity.JoinedSubclassEntityPersister.determineTableNumberForColumn(JoinedSubclassEntityPersister.java:854)
> at
> org.hibernate.persister.entity.AbstractEntityPersister.getTableAliasForColumn(AbstractEntityPersister.java:4967)
> at
> org.hibernate.persister.collection.AbstractCollectionPersister$StandardOrderByAliasResolver.resolveTableAlias(AbstractCollectionPersister.java:1931)
> at
> org.hibernate.sql.ordering.antlr.OrderByFragmentTranslator$StandardOrderByTranslationImpl.injectAliases(OrderByFragmentTranslator.java:106)
> at
> org.hibernate.persister.collection.AbstractCollectionPersister.getSQLOrderByString(AbstractCollectionPersister.java:747)
> at org.hibernate.loader.JoinWalker.orderBy(JoinWalker.java:938)
> at org.hibernate.loader.JoinWalker.orderBy(JoinWalker.java:850)
> at
> org.hibernate.loader.AbstractEntityJoinWalker.initStatementString(AbstractEntityJoinWalker.java:123)
> at
> org.hibernate.loader.AbstractEntityJoinWalker.initStatementString(AbstractEntityJoinWalker.java:108)
> at
> org.hibernate.loader.AbstractEntityJoinWalker.initAll(AbstractEntityJoinWalker.java:90)
> at
> org.hibernate.loader.AbstractEntityJoinWalker.initAll(AbstractEntityJoinWalker.java:77)
> at
> org.hibernate.loader.entity.CascadeEntityJoinWalker.(CascadeEntityJoinWalker.java:51)
> at
> org.hibernate.loader.entity.CascadeEntityLoader.(CascadeEntityLoader.java:46)
> at
> org.hibernate.persister.entity.AbstractEntityPersister.createLoaders(AbstractEntityPersister.java:3881)
> at
> org.hibernate.persister.entity.AbstractEntityPersister.postInstantiate(AbstractEntityPersister.java:3818)
> at
> org.hibernate.internal.SessionFactoryImpl.(SessionFactoryImpl.java:461)
> at
> org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1750)
> at
> org.hibernate.ejb.EntityManagerFactoryImpl.(EntityManagerFactoryImpl.java:94)
> at
> org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:920)
> ... 45 more
> {quote}
> Maybe this can be fixed inside JUDDI instead of waiting for a fix in
> Hibernate (since it persists for a very long time now).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (JUDDI-823) create a jboss7/eap6 profile with hibernate
[ https://issues.apache.org/jira/browse/JUDDI-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-823. - > create a jboss7/eap6 profile with hibernate > --- > > Key: JUDDI-823 > URL: https://issues.apache.org/jira/browse/JUDDI-823 > Project: jUDDI > Issue Type: New Feature > Components: distributions >Reporter: Alex O'Ree >Assignee: Kurt T Stam > Fix For: 3.2.1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JUDDI-878) Fix Jboss AS 7.x deployment
[
https://issues.apache.org/jira/browse/JUDDI-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144894#comment-14144894
]
Kurt T Stam commented on JUDDI-878:
---
Updated the documentation and added a profile for both wars
> Fix Jboss AS 7.x deployment
> ---
>
> Key: JUDDI-878
> URL: https://issues.apache.org/jira/browse/JUDDI-878
> Project: jUDDI
> Issue Type: Bug
> Components: core, documentation, website
>Reporter: Daniel Ferreira Castro
>Assignee: Kurt T Stam
>Priority: Minor
> Fix For: 3.2.1
>
> Attachments: 2014-05-23#1231server.log, Install.java, Juddi.png,
> boot.log, fix.png, git.png, jboss-web.xml, juddiv3 (jboss7).war,
> libOpenJPA221.png, modules.xml, persistence.xml, server - 20140429.log,
> server.7z, server.log, server.log, server.log, server.log
>
>
> The online Apache jUDDI Guide specifies at the end of this link (OpenJPA and
> JBossWS-CXF)
> http://juddi.apache.org/docs/3.2/juddi-guide/html_single/#_jbossas_7_x_jbosseap_6_x
> says "and in the `modules/system/layers/base/org/jboss/as/jpa/main/module.xml
> add dependency "
> But this folder structure does not exists on jboss-as7 and there is no
> previous instructions about how to create it and what to put i in. There are
> tow previous instrctions to create:
> /modules/system/layers/base/org/apache/openjpa/main and
> /modules/system/layers/base/org/jboss/as/jpa/openjpa/main
> but not /modules/system/layers/base/org/jboss/as/jpa/main/module.xml
> So, when I try to deploy it to Jboss AS 7.1.1 I get an exception
> 11:42:43,356 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401:
> Read persistence.xml for juddiDatabase
> 11:42:43,864 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2)
> MSC1: Failed to start service
> jboss.module.service."deployment.juddiv3.war".main: org.jboss.msc.service
> .StartException in service
> jboss.module.service."deployment.juddiv3.war".main: Failed to load module:
> deployment.juddiv3.war:main
> at
> org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91)
> [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> [rt.jar:1.7.0_11]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> [rt.jar:1.7.0_11]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_11]
> Caused by: org.jboss.modules.ModuleNotFoundException: Module
> org.apache.openjpa:main is not found in local module loader @655c8c (roots:
> c:\Java\jboss-as-7.1.1.Final\modules)
> at
> org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126)
> at
> org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275)
> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222)
> at
> org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94)
> at org.jboss.modules.Module.addPaths(Module.java:841)
> at org.jboss.modules.Module.link(Module.java:1181)
> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1207)
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208)
> at
> org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70)
> [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> ... 5 more
> 11:42:44,112 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2)
> JBAS015870: Deploy of deployment "juddiv3.war" was rolled back with failure
> message {"JBAS014671: Failed se
> rvices" => {"jboss.module.service.\"deployment.juddiv3.war\".main" =>
> "org.jboss.msc.service.StartException in service
> jboss.module.service.\"deployment.juddiv3.war\".main: Failed
> to load module: deployment.juddiv3.war:main"}}
> 11:42:44,272 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4)
> JBAS015877: Stopped deployment juddiv3.war in 159ms
> 11:42:44,274 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2)
> JBAS014774: Service status report
> JBAS014777: Services which failed to start: service
> jboss.module.service."deployment.juddiv3.war".main:
> org.jboss.msc.service.StartException in service jboss.module.service.
> "deployment.juddiv3.war".main: Failed to load module:
> deployment.juddiv3.war:main
> 11:42:44,283 ERROR [org.jboss.as.server.deployment.scanner]
> (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation f
[jira] [Resolved] (JUDDI-823) create a jboss7/eap6 profile with hibernate
[ https://issues.apache.org/jira/browse/JUDDI-823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam resolved JUDDI-823. --- Resolution: Fixed Added a jboss7up profile for both the juddiv3 and juddi-gui projects. > create a jboss7/eap6 profile with hibernate > --- > > Key: JUDDI-823 > URL: https://issues.apache.org/jira/browse/JUDDI-823 > Project: jUDDI > Issue Type: New Feature > Components: distributions >Reporter: Alex O'Ree >Assignee: Kurt T Stam > Fix For: 3.2.1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JUDDI-878) Fix Jboss AS 7.x deployment
[
https://issues.apache.org/jira/browse/JUDDI-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14144813#comment-14144813
]
Kurt T Stam commented on JUDDI-878:
---
I fixed up the JBossAS7Up deployment profile and tested it on wildfly8.1. So
now you can run the juddiv3.war 'out-of-the-box' when it is build with the
JbossAS7Up profile (you no longer need to modify the container by adding the
openjpa module). Left to do is:
- add JBossAS7Up profile for the juddi-gui since cxf has a conflict
- add documentation on how to add a jUDDI login user using the
add-application-user.sh scripts.
> Fix Jboss AS 7.x deployment
> ---
>
> Key: JUDDI-878
> URL: https://issues.apache.org/jira/browse/JUDDI-878
> Project: jUDDI
> Issue Type: Bug
> Components: core, documentation, website
>Reporter: Daniel Ferreira Castro
>Assignee: Kurt T Stam
>Priority: Minor
> Fix For: 3.2.1
>
> Attachments: 2014-05-23#1231server.log, Install.java, Juddi.png,
> boot.log, fix.png, git.png, jboss-web.xml, juddiv3 (jboss7).war,
> libOpenJPA221.png, modules.xml, persistence.xml, server - 20140429.log,
> server.7z, server.log, server.log, server.log, server.log
>
>
> The online Apache jUDDI Guide specifies at the end of this link (OpenJPA and
> JBossWS-CXF)
> http://juddi.apache.org/docs/3.2/juddi-guide/html_single/#_jbossas_7_x_jbosseap_6_x
> says "and in the `modules/system/layers/base/org/jboss/as/jpa/main/module.xml
> add dependency "
> But this folder structure does not exists on jboss-as7 and there is no
> previous instructions about how to create it and what to put i in. There are
> tow previous instrctions to create:
> /modules/system/layers/base/org/apache/openjpa/main and
> /modules/system/layers/base/org/jboss/as/jpa/openjpa/main
> but not /modules/system/layers/base/org/jboss/as/jpa/main/module.xml
> So, when I try to deploy it to Jboss AS 7.1.1 I get an exception
> 11:42:43,356 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401:
> Read persistence.xml for juddiDatabase
> 11:42:43,864 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2)
> MSC1: Failed to start service
> jboss.module.service."deployment.juddiv3.war".main: org.jboss.msc.service
> .StartException in service
> jboss.module.service."deployment.juddiv3.war".main: Failed to load module:
> deployment.juddiv3.war:main
> at
> org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91)
> [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> [rt.jar:1.7.0_11]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> [rt.jar:1.7.0_11]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_11]
> Caused by: org.jboss.modules.ModuleNotFoundException: Module
> org.apache.openjpa:main is not found in local module loader @655c8c (roots:
> c:\Java\jboss-as-7.1.1.Final\modules)
> at
> org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126)
> at
> org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275)
> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222)
> at
> org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94)
> at org.jboss.modules.Module.addPaths(Module.java:841)
> at org.jboss.modules.Module.link(Module.java:1181)
> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1207)
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208)
> at
> org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70)
> [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> ... 5 more
> 11:42:44,112 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2)
> JBAS015870: Deploy of deployment "juddiv3.war" was rolled back with failure
> message {"JBAS014671: Failed se
> rvices" => {"jboss.module.service.\"deployment.juddiv3.war\".main" =>
> "org.jboss.msc.service.StartException in service
> jboss.module.service.\"deployment.juddiv3.war\".main: Failed
> to load module: deployment.juddiv3.war:main"}}
> 11:42:44,272 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4)
> JBAS015877: Stopped deployment juddiv3.war in 159ms
> 11:42:44,274 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2)
> JBAS014774: Service status report
> JBAS014777: Services which failed
[jira] [Resolved] (JUDDI-587) JUDDI incompatible with Hibernate 4.1.x and 4.2.x
[
https://issues.apache.org/jira/browse/JUDDI-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kurt T Stam resolved JUDDI-587.
---
Resolution: Fixed
https://git-wip-us.apache.org/repos/asf?p=juddi.git;a=commit;h=ea8962baf6027d7714f26309c2a7b87b9e7ac141
Upgraded to JPA 2.0 - Hibernate fixed its issue so it is all working now. I
tested the deployment on wildfly-8.1 - and fixed up the JBoss7UP profile on the
juddiv3.war project.
> JUDDI incompatible with Hibernate 4.1.x and 4.2.x
> -
>
> Key: JUDDI-587
> URL: https://issues.apache.org/jira/browse/JUDDI-587
> Project: jUDDI
> Issue Type: Bug
> Components: core
>Affects Versions: 3.1.4
>Reporter: subes
>Assignee: Kurt T Stam
> Fix For: 3.2.1
>
> Attachments: JUDDI-587-patch.txt
>
>
> JUDDI is affected by the following Bug in Hibernate:
> https://hibernate.atlassian.net/browse/HHH-7630
> {quote}
> Caused by: org.hibernate.HibernateException: Could not locate table which
> owns column [entity_key] referenced in order-by mapping
> at
> org.hibernate.persister.entity.JoinedSubclassEntityPersister.determineTableNumberForColumn(JoinedSubclassEntityPersister.java:854)
> at
> org.hibernate.persister.entity.AbstractEntityPersister.getTableAliasForColumn(AbstractEntityPersister.java:4967)
> at
> org.hibernate.persister.collection.AbstractCollectionPersister$StandardOrderByAliasResolver.resolveTableAlias(AbstractCollectionPersister.java:1931)
> at
> org.hibernate.sql.ordering.antlr.OrderByFragmentTranslator$StandardOrderByTranslationImpl.injectAliases(OrderByFragmentTranslator.java:106)
> at
> org.hibernate.persister.collection.AbstractCollectionPersister.getSQLOrderByString(AbstractCollectionPersister.java:747)
> at org.hibernate.loader.JoinWalker.orderBy(JoinWalker.java:938)
> at org.hibernate.loader.JoinWalker.orderBy(JoinWalker.java:850)
> at
> org.hibernate.loader.AbstractEntityJoinWalker.initStatementString(AbstractEntityJoinWalker.java:123)
> at
> org.hibernate.loader.AbstractEntityJoinWalker.initStatementString(AbstractEntityJoinWalker.java:108)
> at
> org.hibernate.loader.AbstractEntityJoinWalker.initAll(AbstractEntityJoinWalker.java:90)
> at
> org.hibernate.loader.AbstractEntityJoinWalker.initAll(AbstractEntityJoinWalker.java:77)
> at
> org.hibernate.loader.entity.CascadeEntityJoinWalker.(CascadeEntityJoinWalker.java:51)
> at
> org.hibernate.loader.entity.CascadeEntityLoader.(CascadeEntityLoader.java:46)
> at
> org.hibernate.persister.entity.AbstractEntityPersister.createLoaders(AbstractEntityPersister.java:3881)
> at
> org.hibernate.persister.entity.AbstractEntityPersister.postInstantiate(AbstractEntityPersister.java:3818)
> at
> org.hibernate.internal.SessionFactoryImpl.(SessionFactoryImpl.java:461)
> at
> org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1750)
> at
> org.hibernate.ejb.EntityManagerFactoryImpl.(EntityManagerFactoryImpl.java:94)
> at
> org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:920)
> ... 45 more
> {quote}
> Maybe this can be fixed inside JUDDI instead of waiting for a fix in
> Hibernate (since it persists for a very long time now).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (JUDDI-878) Fix Jboss AS 7.x deployment
[
https://issues.apache.org/jira/browse/JUDDI-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kurt T Stam closed JUDDI-878.
-
Resolution: Not a Problem
This jira really is a discussion and not an actionable item. Let's continue on
the user forum.
> Fix Jboss AS 7.x deployment
> ---
>
> Key: JUDDI-878
> URL: https://issues.apache.org/jira/browse/JUDDI-878
> Project: jUDDI
> Issue Type: Bug
> Components: core, documentation, website
>Reporter: Daniel Ferreira Castro
>Assignee: Kurt T Stam
>Priority: Minor
> Fix For: 3.2.1
>
> Attachments: 2014-05-23#1231server.log, Install.java, Juddi.png,
> boot.log, fix.png, git.png, jboss-web.xml, juddiv3 (jboss7).war,
> libOpenJPA221.png, modules.xml, persistence.xml, server - 20140429.log,
> server.7z, server.log, server.log, server.log, server.log
>
>
> The online Apache jUDDI Guide specifies at the end of this link (OpenJPA and
> JBossWS-CXF)
> http://juddi.apache.org/docs/3.2/juddi-guide/html_single/#_jbossas_7_x_jbosseap_6_x
> says "and in the `modules/system/layers/base/org/jboss/as/jpa/main/module.xml
> add dependency "
> But this folder structure does not exists on jboss-as7 and there is no
> previous instructions about how to create it and what to put i in. There are
> tow previous instrctions to create:
> /modules/system/layers/base/org/apache/openjpa/main and
> /modules/system/layers/base/org/jboss/as/jpa/openjpa/main
> but not /modules/system/layers/base/org/jboss/as/jpa/main/module.xml
> So, when I try to deploy it to Jboss AS 7.1.1 I get an exception
> 11:42:43,356 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401:
> Read persistence.xml for juddiDatabase
> 11:42:43,864 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2)
> MSC1: Failed to start service
> jboss.module.service."deployment.juddiv3.war".main: org.jboss.msc.service
> .StartException in service
> jboss.module.service."deployment.juddiv3.war".main: Failed to load module:
> deployment.juddiv3.war:main
> at
> org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91)
> [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
> [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
> [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> [rt.jar:1.7.0_11]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> [rt.jar:1.7.0_11]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_11]
> Caused by: org.jboss.modules.ModuleNotFoundException: Module
> org.apache.openjpa:main is not found in local module loader @655c8c (roots:
> c:\Java\jboss-as-7.1.1.Final\modules)
> at
> org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126)
> at
> org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275)
> at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222)
> at
> org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94)
> at org.jboss.modules.Module.addPaths(Module.java:841)
> at org.jboss.modules.Module.link(Module.java:1181)
> at org.jboss.modules.Module.relinkIfNecessary(Module.java:1207)
> at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208)
> at
> org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70)
> [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
> ... 5 more
> 11:42:44,112 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2)
> JBAS015870: Deploy of deployment "juddiv3.war" was rolled back with failure
> message {"JBAS014671: Failed se
> rvices" => {"jboss.module.service.\"deployment.juddiv3.war\".main" =>
> "org.jboss.msc.service.StartException in service
> jboss.module.service.\"deployment.juddiv3.war\".main: Failed
> to load module: deployment.juddiv3.war:main"}}
> 11:42:44,272 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4)
> JBAS015877: Stopped deployment juddiv3.war in 159ms
> 11:42:44,274 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2)
> JBAS014774: Service status report
> JBAS014777: Services which failed to start: service
> jboss.module.service."deployment.juddiv3.war".main:
> org.jboss.msc.service.StartException in service jboss.module.service.
> "deployment.juddiv3.war".main: Failed to load module:
> deployment.juddiv3.war:main
> 11:42:44,283 ERROR [org.jboss.as.server.deployment.scanner]
> (DeploymentScanner-threads - 1) {"JBAS014653: Composite ope
[jira] [Commented] (JUDDI-878) Fix Jboss AS 7.x deployment
[ https://issues.apache.org/jira/browse/JUDDI-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018785#comment-14018785 ] Kurt T Stam commented on JUDDI-878: --- Hi Daniel, Can we move this discussion to the jUDDI user forum? You will use a much larger group of poeple that are willing to help on the user forum, Jira is really for issue tracking. I'm going to close this jira as I'm not sure there are any actionable items in it. Hopefully we can discuss on the forum and then formulate some new jiras. On a side note I happen to work for JBoss/Red Hat and am more then willing to help you out. Keep in mind though that the jUDDI project tries to deploy to any EE server, and that there are quite a few of those, and as an Apache project we can on ship code based on the Apache license or equivalent, and so we do create bundle based on tomcat. For other app servers we created scripts + documentation. All of this is on a volunteer basis. The JBossAuthenticator references JBoss libraries with LGPL license, so we cannot ship those. The code fragment is there along with the documentation to get you going. The JBossAuthenticator ships with our examples and you can simply use maven to compile: https://github.com/apache/juddi/tree/master/docs/examples/auth It is used in JBossESB if you want to see it fully integrated with JBoss. --Kurt > Fix Jboss AS 7.x deployment > --- > > Key: JUDDI-878 > URL: https://issues.apache.org/jira/browse/JUDDI-878 > Project: jUDDI > Issue Type: Bug > Components: core, documentation, website >Reporter: Daniel Ferreira Castro >Assignee: Kurt T Stam >Priority: Minor > Fix For: 3.2.1 > > Attachments: 2014-05-23#1231server.log, Install.java, Juddi.png, > boot.log, fix.png, git.png, jboss-web.xml, juddiv3 (jboss7).war, > libOpenJPA221.png, modules.xml, persistence.xml, server - 20140429.log, > server.7z, server.log, server.log, server.log, server.log > > > The online Apache jUDDI Guide specifies at the end of this link (OpenJPA and > JBossWS-CXF) > http://juddi.apache.org/docs/3.2/juddi-guide/html_single/#_jbossas_7_x_jbosseap_6_x > says "and in the `modules/system/layers/base/org/jboss/as/jpa/main/module.xml > add dependency " > But this folder structure does not exists on jboss-as7 and there is no > previous instructions about how to create it and what to put i in. There are > tow previous instrctions to create: > /modules/system/layers/base/org/apache/openjpa/main and > /modules/system/layers/base/org/jboss/as/jpa/openjpa/main > but not /modules/system/layers/base/org/jboss/as/jpa/main/module.xml > So, when I try to deploy it to Jboss AS 7.1.1 I get an exception > 11:42:43,356 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401: > Read persistence.xml for juddiDatabase > 11:42:43,864 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) > MSC1: Failed to start service > jboss.module.service."deployment.juddiv3.war".main: org.jboss.msc.service > .StartException in service > jboss.module.service."deployment.juddiv3.war".main: Failed to load module: > deployment.juddiv3.war:main > at > org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) > [jboss-as-server-7.1.1.Final.jar:7.1.1.Final] > at > org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) > [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at > org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) > [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > [rt.jar:1.7.0_11] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > [rt.jar:1.7.0_11] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_11] > Caused by: org.jboss.modules.ModuleNotFoundException: Module > org.apache.openjpa:main is not found in local module loader @655c8c (roots: > c:\Java\jboss-as-7.1.1.Final\modules) > at > org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126) > at > org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) > at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) > at > org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94) > at org.jboss.modules.Module.addPaths(Module.java:841) > at org.jboss.modules.Module.link(Module.java:1181) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1207) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208) > at > org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70) > [jboss-as-se
[jira] [Updated] (JUDDI-852) find binding's ListDescription's count values are always null
[ https://issues.apache.org/jira/browse/JUDDI-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam updated JUDDI-852: -- Assignee: Alex O'Ree (was: Kurt T Stam) > find binding's ListDescription's count values are always null > - > > Key: JUDDI-852 > URL: https://issues.apache.org/jira/browse/JUDDI-852 > Project: jUDDI > Issue Type: Bug > Components: core >Affects Versions: 3.2 >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2.1 > > > element BindingDetail on operation findBinding -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-852) find binding's ListDescription's count values are always null
[ https://issues.apache.org/jira/browse/JUDDI-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908618#comment-13908618 ] Kurt T Stam commented on JUDDI-852: --- Hi Alex, It looks like this *would* be set *if* pagination is needed (the listDesc reference is passed into the query engine). If all results are returned, then nothing is set. We should not need your code change. That said; if it's not working then there is a bug in the query engine. Does the spec say we always have to return the count values even if pagination is not used? > find binding's ListDescription's count values are always null > - > > Key: JUDDI-852 > URL: https://issues.apache.org/jira/browse/JUDDI-852 > Project: jUDDI > Issue Type: Bug > Components: core >Affects Versions: 3.2 >Reporter: Alex O'Ree >Assignee: Kurt T Stam > Fix For: 3.2.1 > > > element BindingDetail on operation findBinding -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-851) access control roles are incorrect for uddiv2 keys
[ https://issues.apache.org/jira/browse/JUDDI-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-851. - > access control roles are incorrect for uddiv2 keys > -- > > Key: JUDDI-851 > URL: https://issues.apache.org/jira/browse/JUDDI-851 > Project: jUDDI > Issue Type: Bug > Components: core >Affects Versions: 3.2 >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2.1 > > > org.uddi.v2_service.DispositionReport: The proposed key is not within the > partition defined by owning publisher. If you're tring to create a new tModel > in a new partition, try creating a tModel that ends in :keygenerator: > uuid:0ebf9f1d-4b8 > 1-4554-87b0-f4af21b6b569 > This error is obviously not correct for uddiv2 keys. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (JUDDI-859) Switch buildbot config to GIT
[ https://issues.apache.org/jira/browse/JUDDI-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam resolved JUDDI-859. --- Resolution: Fixed I think apart from the windows build machine not having git installed it's all working. > Switch buildbot config to GIT > - > > Key: JUDDI-859 > URL: https://issues.apache.org/jira/browse/JUDDI-859 > Project: jUDDI > Issue Type: Task >Reporter: Kurt T Stam >Assignee: Kurt T Stam > Fix For: 3.2.1 > > > Now that we are on GIT we need to switch the buildbot config to use git. We > should be able to copy from the cordova.conf since they are already on git. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-859) Switch buildbot config to GIT
[ https://issues.apache.org/jira/browse/JUDDI-859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-859. - > Switch buildbot config to GIT > - > > Key: JUDDI-859 > URL: https://issues.apache.org/jira/browse/JUDDI-859 > Project: jUDDI > Issue Type: Task >Reporter: Kurt T Stam >Assignee: Kurt T Stam > Fix For: 3.2.1 > > > Now that we are on GIT we need to switch the buildbot config to use git. We > should be able to copy from the cordova.conf since they are already on git. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (JUDDI-841) save entity permissions with undefined keys
[ https://issues.apache.org/jira/browse/JUDDI-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam resolved JUDDI-841. --- Resolution: Fixed Now the generator will try to use the publishers keyGenerator's domain instead. > save entity permissions with undefined keys > --- > > Key: JUDDI-841 > URL: https://issues.apache.org/jira/browse/JUDDI-841 > Project: jUDDI > Issue Type: Bug > Components: core >Affects Versions: 3.2 >Reporter: Alex O'Ree >Assignee: Kurt T Stam > Fix For: 3.2.1 > > > If i create a tmodel without defining a key, i end up with a guid id > uddi:juddi.apache.org:b7669606-a2e8-4fda-be16-f7b64dc3e936 > however if i try to explicitly save a tmodel with the similar but different > key > uddi:juddi.apache.org:b7669606-a2e8-4fda-be16-f7b64dc3e937 > Error The proposed key is not within the partition defined by owning > publisher. If you're tring to create a new tModel in a new partition, try > creating a tModel that ends in :keygenerator: > uddi:juddi.apache.org:b7669606-a2e8-4fda-be16-f7b64dc3e937 > I'm not too sure if this is a "bug" or not. It does however make it > impossible to restore from backup while maintaining user permissions. > Essentially, we have to save everything as the user root. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-841) save entity permissions with undefined keys
[ https://issues.apache.org/jira/browse/JUDDI-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-841. - > save entity permissions with undefined keys > --- > > Key: JUDDI-841 > URL: https://issues.apache.org/jira/browse/JUDDI-841 > Project: jUDDI > Issue Type: Bug > Components: core >Affects Versions: 3.2 >Reporter: Alex O'Ree >Assignee: Kurt T Stam > Fix For: 3.2.1 > > > If i create a tmodel without defining a key, i end up with a guid id > uddi:juddi.apache.org:b7669606-a2e8-4fda-be16-f7b64dc3e936 > however if i try to explicitly save a tmodel with the similar but different > key > uddi:juddi.apache.org:b7669606-a2e8-4fda-be16-f7b64dc3e937 > Error The proposed key is not within the partition defined by owning > publisher. If you're tring to create a new tModel in a new partition, try > creating a tModel that ends in :keygenerator: > uddi:juddi.apache.org:b7669606-a2e8-4fda-be16-f7b64dc3e937 > I'm not too sure if this is a "bug" or not. It does however make it > impossible to restore from backup while maintaining user permissions. > Essentially, we have to save everything as the user root. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (JUDDI-859) Switch buildbot config to GIT
Kurt T Stam created JUDDI-859: - Summary: Switch buildbot config to GIT Key: JUDDI-859 URL: https://issues.apache.org/jira/browse/JUDDI-859 Project: jUDDI Issue Type: Task Reporter: Kurt T Stam Assignee: Kurt T Stam Fix For: 3.2.1 Now that we are on GIT we need to switch the buildbot config to use git. We should be able to copy from the cordova.conf since they are already on git. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-695) juddi-gui jsp precompile for deployment
[
https://issues.apache.org/jira/browse/JUDDI-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13902786#comment-13902786
]
Kurt T Stam commented on JUDDI-695:
---
--- juddi-gui/pom.xml (revision 1567959)
+++ juddi-gui/pom.xml (working copy)
@@ -127,8 +127,8 @@
-
${project.build.directory}/juddi-gui
-
${project.build.directory}/juddi-gui-precompiled
+
src/main/webapp
+
org.apache.juddi.webconsole.jsp
Something like the above does the pre-compilation. Personally I just want it so
we know things compile.
> juddi-gui jsp precompile for deployment
> ---
>
> Key: JUDDI-695
> URL: https://issues.apache.org/jira/browse/JUDDI-695
> Project: jUDDI
> Issue Type: Task
> Components: juddi-gui
>Reporter: Alex O'Ree
>Assignee: Kurt T Stam
>Priority: Minor
> Fix For: 3.2.1
>
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Updated] (JUDDI-854) update cloud instance
[ https://issues.apache.org/jira/browse/JUDDI-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam updated JUDDI-854: -- Component/s: cloud > update cloud instance > - > > Key: JUDDI-854 > URL: https://issues.apache.org/jira/browse/JUDDI-854 > Project: jUDDI > Issue Type: Task > Components: cloud >Reporter: Kurt T Stam >Assignee: Kurt T Stam > Fix For: 3.2.1 > > > - add a banner to tell people how to get a publisher account. > - update the seed data to reflect the nature of this node -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (JUDDI-854) update cloud instance
Kurt T Stam created JUDDI-854: - Summary: update cloud instance Key: JUDDI-854 URL: https://issues.apache.org/jira/browse/JUDDI-854 Project: jUDDI Issue Type: Task Reporter: Kurt T Stam Assignee: Kurt T Stam Fix For: 3.2.1 - add a banner to tell people how to get a publisher account. - update the seed data to reflect the nature of this node -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-850) juddi-console supporting UDDIv2
[ https://issues.apache.org/jira/browse/JUDDI-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899500#comment-13899500 ] Kurt T Stam commented on JUDDI-850: --- I decided to run the gui on tomcat connecting to jUDDI on a different server and now I'm getting a jUDDI v2 serverside error: 14:47:38,212 INFO [FindBusinessFunction] E_unsupported (10050) The implementor does not support a feature or API. find_business: findQualifier=approximateMatch 14:47:38,212 ERROR [AbstractService] E_unsupported (10050) The implementor does not support a feature or API. find_business: findQualifier=approximateMatch 14:47:38,212 ERROR [AbstractService] A serious error has occured while assembling the SOAP Fault. javax.xml.soap.SOAPException: Fault code 'Client' must be namespace qualified at org.jboss.ws.core.soap.SOAPFaultImpl.setFaultCode(SOAPFaultImpl.java:191) at org.jboss.ws.core.soap.SOAPFaultImpl.setFaultCode(SOAPFaultImpl.java:175) at org.apache.juddi.registry.AbstractService.doPost(AbstractService.java:326) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:744) > juddi-console supporting UDDIv2 > --- > > Key: JUDDI-850 > URL: https://issues.apache.org/jira/browse/JUDDI-850 > Project: jUDDI > Issue Type: Bug > Components: juddi-gui >Affects Versions: 3.2 >Reporter: Kurt T Stam >Assignee: Alex O'Ree > Fix For: 3.2.1 > > > By allowing the user to select a uddiv2 connection, I think we are saying > that we support this combination? > When I try to use the console with juddi v2, I get a the following exception > when it is trying to create a subscription connection in the UDDIHub: > org.apache.juddi.v3.client.transport.TransportException: > com.sun.xml.bind.v2.runtime.JAXBContextImpl cannot be cast to > com.sun.xml.bind.api.JAXBRIContext > when it is trying to: > subscription = transport.getUDDISubscriptionService(); > Which is understandable since the UDDI v2 protocol does not support this. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-850) juddi-console supporting UDDIv2
[
https://issues.apache.org/jira/browse/JUDDI-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899268#comment-13899268
]
Kurt T Stam commented on JUDDI-850:
---
To reproduce, run jUDDI v2 and set the following connection info the uddi.xml
of the console:
{code:title=uddi.xml|borderStyle=solid}
default
UDDIv2 Node (localhost)
org.apache.juddi.v3.client.transport.JAXWSv2TranslationTransport
http://localhost:8080/juddi/inquiry
http://localhost:8080/juddi/publish
{code}
> juddi-console supporting UDDIv2
> ---
>
> Key: JUDDI-850
> URL: https://issues.apache.org/jira/browse/JUDDI-850
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-gui
>Affects Versions: 3.2
>Reporter: Kurt T Stam
>Assignee: Alex O'Ree
> Fix For: 3.2.1
>
>
> By allowing the user to select a uddiv2 connection, I think we are saying
> that we support this combination?
> When I try to use the console with juddi v2, I get a the following exception
> when it is trying to create a subscription connection in the UDDIHub:
> org.apache.juddi.v3.client.transport.TransportException:
> com.sun.xml.bind.v2.runtime.JAXBContextImpl cannot be cast to
> com.sun.xml.bind.api.JAXBRIContext
> when it is trying to:
> subscription = transport.getUDDISubscriptionService();
> Which is understandable since the UDDI v2 protocol does not support this.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Comment Edited] (JUDDI-850) juddi-console supporting UDDIv2
[
https://issues.apache.org/jira/browse/JUDDI-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899268#comment-13899268
]
Kurt T Stam edited comment on JUDDI-850 at 2/12/14 4:47 PM:
To reproduce, run jUDDI v2 and set the following connection info the uddi.xml
in the console:
{code:title=uddi.xml|borderStyle=solid}
default
UDDIv2 Node (localhost)
org.apache.juddi.v3.client.transport.JAXWSv2TranslationTransport
http://localhost:8080/juddi/inquiry
http://localhost:8080/juddi/publish
{code}
was (Author: kurtstam):
To reproduce, run jUDDI v2 and set the following connection info the uddi.xml
of the console:
{code:title=uddi.xml|borderStyle=solid}
default
UDDIv2 Node (localhost)
org.apache.juddi.v3.client.transport.JAXWSv2TranslationTransport
http://localhost:8080/juddi/inquiry
http://localhost:8080/juddi/publish
{code}
> juddi-console supporting UDDIv2
> ---
>
> Key: JUDDI-850
> URL: https://issues.apache.org/jira/browse/JUDDI-850
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-gui
>Affects Versions: 3.2
>Reporter: Kurt T Stam
>Assignee: Alex O'Ree
> Fix For: 3.2.1
>
>
> By allowing the user to select a uddiv2 connection, I think we are saying
> that we support this combination?
> When I try to use the console with juddi v2, I get a the following exception
> when it is trying to create a subscription connection in the UDDIHub:
> org.apache.juddi.v3.client.transport.TransportException:
> com.sun.xml.bind.v2.runtime.JAXBContextImpl cannot be cast to
> com.sun.xml.bind.api.JAXBRIContext
> when it is trying to:
> subscription = transport.getUDDISubscriptionService();
> Which is understandable since the UDDI v2 protocol does not support this.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (JUDDI-850) juddi-console supporting UDDIv2
Kurt T Stam created JUDDI-850: - Summary: juddi-console supporting UDDIv2 Key: JUDDI-850 URL: https://issues.apache.org/jira/browse/JUDDI-850 Project: jUDDI Issue Type: Bug Components: juddi-gui Affects Versions: 3.2 Reporter: Kurt T Stam Assignee: Alex O'Ree Fix For: 3.2.1 By allowing the user to select a uddiv2 connection, I think we are saying that we support this combination? When I try to use the console with juddi v2, I get a the following exception when it is trying to create a subscription connection in the UDDIHub: org.apache.juddi.v3.client.transport.TransportException: com.sun.xml.bind.v2.runtime.JAXBContextImpl cannot be cast to com.sun.xml.bind.api.JAXBRIContext when it is trying to: subscription = transport.getUDDISubscriptionService(); Which is understandable since the UDDI v2 protocol does not support this. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-841) save entity permissions with undefined keys
[ https://issues.apache.org/jira/browse/JUDDI-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894579#comment-13894579 ] Kurt T Stam commented on JUDDI-841: --- It seems to me that we should pick the publisher's domain when generating a key on the server side, rather then the root domain when generating a key. I think this is a bug. > save entity permissions with undefined keys > --- > > Key: JUDDI-841 > URL: https://issues.apache.org/jira/browse/JUDDI-841 > Project: jUDDI > Issue Type: Bug > Components: core >Affects Versions: 3.2 >Reporter: Alex O'Ree >Assignee: Kurt T Stam > Fix For: 3.2.1 > > > If i create a tmodel without defining a key, i end up with a guid id > uddi:juddi.apache.org:b7669606-a2e8-4fda-be16-f7b64dc3e936 > however if i try to explicitly a tmodel with the similar but different key > uddi:juddi.apache.org:b7669606-a2e8-4fda-be16-f7b64dc3e937 > Error The proposed key is not within the partition defined by owning > publisher. If you're tring to create a new tModel in a new partition, try > creating a tModel that ends in :keygenerator: > uddi:juddi.apache.org:b7669606-a2e8-4fda-be16-f7b64dc3e937 > I'm not too sure if this is a "bug" or not. It does however make it > impossible to restore from backup while maintaining user permissions. > Essentially, we have to save everything as the user root. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (JUDDI-840) Fix file authentication
Kurt T Stam created JUDDI-840: - Summary: Fix file authentication Key: JUDDI-840 URL: https://issues.apache.org/jira/browse/JUDDI-840 Project: jUDDI Issue Type: Bug Reporter: Kurt T Stam Assignee: Kurt T Stam Fix For: 3.2.1 It's not easy to read the juddi-user.xml from the /conf directory. I think it should be an option to read the users/pw info from the tomcat-users.xml. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (JUDDI-837) Update jUDDI incubation site to better reflect that it has graduated
[ https://issues.apache.org/jira/browse/JUDDI-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam updated JUDDI-837: -- Fix Version/s: 3.2.1 > Update jUDDI incubation site to better reflect that it has graduated > > > Key: JUDDI-837 > URL: https://issues.apache.org/jira/browse/JUDDI-837 > Project: jUDDI > Issue Type: Task > Components: website >Affects Versions: 3.2 > Environment: Apache Incubator >Reporter: Alex O'Ree >Assignee: Steve Viens >Priority: Minor > Fix For: 3.2.1 > > Original Estimate: 2h > Remaining Estimate: 2h > > Source of this work is in the following thread: > http://mail-archives.apache.org/mod_mbox/juddi-dev/201312.mbox/browser > Will update the jUDDI page on the Apache Incubator site to reflect that jUDDI > graduated in March 2014. Also fix broken urls to source control, issue > tracking and mailing lists to point to current. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Comment Edited] (JUDDI-837) Update jUDDI incubation site to better reflect that it has graduated
[ https://issues.apache.org/jira/browse/JUDDI-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892438#comment-13892438 ] Kurt T Stam edited comment on JUDDI-837 at 2/5/14 7:48 PM: --- Hi Steve, The website is in SVN http://svn.apache.org/repos/asf/juddi/cms-site/trunk/ and any updates made should replicate out within 10 minutes or so, after visiting: https://cms.apache.org/juddi/publish While you're add it, maybe you can update the link on the sourceforge site too? Cheers, --Kurt was (Author: kurtstam): Hi Steve, The website is in SVN http://svn.apache.org/repos/asf/juddi/cms-site/trunk/ and any updates made should replicate out within 10 minutes or so. While you're add it, maybe you can update the link on the sourceforge site too? Cheers, --Kurt > Update jUDDI incubation site to better reflect that it has graduated > > > Key: JUDDI-837 > URL: https://issues.apache.org/jira/browse/JUDDI-837 > Project: jUDDI > Issue Type: Task > Components: website >Affects Versions: 3.2 > Environment: Apache Incubator >Reporter: Alex O'Ree >Assignee: Steve Viens >Priority: Minor > Original Estimate: 2h > Remaining Estimate: 2h > > Source of this work is in the following thread: > http://mail-archives.apache.org/mod_mbox/juddi-dev/201312.mbox/browser > Will update the jUDDI page on the Apache Incubator site to reflect that jUDDI > graduated in March 2014. Also fix broken urls to source control, issue > tracking and mailing lists to point to current. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (JUDDI-837) Update jUDDI incubation site to better reflect that it has graduated
[ https://issues.apache.org/jira/browse/JUDDI-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892438#comment-13892438 ] Kurt T Stam commented on JUDDI-837: --- Hi Steve, The website is in SVN http://svn.apache.org/repos/asf/juddi/cms-site/trunk/ and any updates made should replicate out within 10 minutes or so. While you're add it, maybe you can update the link on the sourceforge site too? Cheers, --Kurt > Update jUDDI incubation site to better reflect that it has graduated > > > Key: JUDDI-837 > URL: https://issues.apache.org/jira/browse/JUDDI-837 > Project: jUDDI > Issue Type: Task > Components: website >Affects Versions: 3.2 > Environment: Apache Incubator >Reporter: Alex O'Ree >Assignee: Steve Viens >Priority: Minor > Original Estimate: 2h > Remaining Estimate: 2h > > Source of this work is in the following thread: > http://mail-archives.apache.org/mod_mbox/juddi-dev/201312.mbox/browser > Will update the jUDDI page on the Apache Incubator site to reflect that jUDDI > graduated in March 2014. Also fix broken urls to source control, issue > tracking and mailing lists to point to current. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-691) NPE querying for Publisher Assertions
[ https://issues.apache.org/jira/browse/JUDDI-691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-691. - > NPE querying for Publisher Assertions > -- > > Key: JUDDI-691 > URL: https://issues.apache.org/jira/browse/JUDDI-691 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > > under certain conditions (perhaps if no services exists), the publish service > can throw a NPE. The conditions aren't entirely clear, but I ran across it > when writing a unit test. > java.lang.NullPointerException > at > org.apache.juddi.api.impl.UDDIPublicationImpl.getPublisherAssertions(UDDIPublicationImpl.java:408) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-796) refactor admin console class paths to prevent collisions with juddi-gui
[ https://issues.apache.org/jira/browse/JUDDI-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-796. - > refactor admin console class paths to prevent collisions with juddi-gui > --- > > Key: JUDDI-796 > URL: https://issues.apache.org/jira/browse/JUDDI-796 > Project: jUDDI > Issue Type: Improvement > Components: core, juddi-gui >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-733) Remove juddi-console project
[ https://issues.apache.org/jira/browse/JUDDI-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-733. - > Remove juddi-console project > > > Key: JUDDI-733 > URL: https://issues.apache.org/jira/browse/JUDDI-733 > Project: jUDDI > Issue Type: Task >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2, 3.3 > > > The juddi-console portlet project hasn't functioned correctly since 3.1.4. We > should probably just remove it from the trunk -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-709) juddi-gui only the first node is listed in the config settings pages
[ https://issues.apache.org/jira/browse/JUDDI-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-709. - > juddi-gui only the first node is listed in the config settings pages > > > Key: JUDDI-709 > URL: https://issues.apache.org/jira/browse/JUDDI-709 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > > when defining more than one config "node" element, only the first one is > listed and editable. this should allow for multiple configurations -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-826) saveBusiness on an existing business fails no browsers other than chrome
[
https://issues.apache.org/jira/browse/JUDDI-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kurt T Stam closed JUDDI-826.
-
> saveBusiness on an existing business fails no browsers other than chrome
>
>
> Key: JUDDI-826
> URL: https://issues.apache.org/jira/browse/JUDDI-826
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-gui
>Reporter: Kurt T Stam
>Assignee: Kurt T Stam
> Fix For: 3.2
>
>
> I had signed a business and tried to Re-Save it to remove my signature. I was
> logged in as root and this resulted in some sort of javascript error; the URL
> says:
> javascript:saveBusiness();$('#confirmDialog').modal('hide');
> and the page displays:
> [object Object]
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Closed] (JUDDI-730) juddi-gui operational status missing from tmodels
[ https://issues.apache.org/jira/browse/JUDDI-730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-730. - > juddi-gui operational status missing from tmodels > - > > Key: JUDDI-730 > URL: https://issues.apache.org/jira/browse/JUDDI-730 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-687) update business editor to have warning when using v2 keys
[ https://issues.apache.org/jira/browse/JUDDI-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-687. - > update business editor to have warning when using v2 keys > - > > Key: JUDDI-687 > URL: https://issues.apache.org/jira/browse/JUDDI-687 > Project: jUDDI > Issue Type: Improvement >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-696) juddi-gui may not generate aes keys using oracle jre without jce
[ https://issues.apache.org/jira/browse/JUDDI-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-696. - > juddi-gui may not generate aes keys using oracle jre without jce > > > Key: JUDDI-696 > URL: https://issues.apache.org/jira/browse/JUDDI-696 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Blocker > Fix For: 3.2 > > > Due to a logic problem, the juddi-gui may fail to operate when using oracle's > jre/jdk that does not have the Unlimited Strength JCE installed due to the > default key being 256 bit. OpenJDK is not affected -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-749) juddi-gui may throw NPE on redeploy
[ https://issues.apache.org/jira/browse/JUDDI-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-749. - > juddi-gui may throw NPE on redeploy > --- > > Key: JUDDI-749 > URL: https://issues.apache.org/jira/browse/JUDDI-749 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2, 3.3 > > > If some has an open session (browser) and juddi-gui is redeployed, such as > editing web.xml, the session becomes invalidated. This error is thrown by the > resource loader for locale specific strings. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-807) Test juddi-gui-disg applet on MacOS
[ https://issues.apache.org/jira/browse/JUDDI-807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-807. - > Test juddi-gui-disg applet on MacOS > --- > > Key: JUDDI-807 > URL: https://issues.apache.org/jira/browse/JUDDI-807 > Project: jUDDI > Issue Type: Task > Components: juddi-gui >Reporter: Alex O'Ree >Assignee: Kurt T Stam > Fix For: 3.2 > > > try to sign something and save using a pki cert -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-793) i18n juddiv3 admin console
[ https://issues.apache.org/jira/browse/JUDDI-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-793. - > i18n juddiv3 admin console > -- > > Key: JUDDI-793 > URL: https://issues.apache.org/jira/browse/JUDDI-793 > Project: jUDDI > Issue Type: Improvement > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-795) juddi-gui settings config page logic issue
[ https://issues.apache.org/jira/browse/JUDDI-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-795. - > juddi-gui settings config page logic issue > -- > > Key: JUDDI-795 > URL: https://issues.apache.org/jira/browse/JUDDI-795 > Project: jUDDI > Issue Type: Bug > Components: juddi-gui >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > > i renamed something like > client.nodes.node(0).name="default-ssl" to "default" and it wiped out a whole > other section. something is out of whack -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-830) importFromWSDL password field should be of type password
[ https://issues.apache.org/jira/browse/JUDDI-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-830. - > importFromWSDL password field should be of type password > > > Key: JUDDI-830 > URL: https://issues.apache.org/jira/browse/JUDDI-830 > Project: jUDDI > Issue Type: Bug > Components: juddi-gui >Reporter: Kurt T Stam >Assignee: Kurt T Stam > Fix For: 3.2 > > > It shows my password in plain text when I type it. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-755) juddi-client add tModel helper functions
[ https://issues.apache.org/jira/browse/JUDDI-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-755. - > juddi-client add tModel helper functions > > > Key: JUDDI-755 > URL: https://issues.apache.org/jira/browse/JUDDI-755 > Project: jUDDI > Issue Type: New Feature >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2, 3.3 > > > it would be really nice we had some helper functions that would take in a > business service and then append (if not already present), commonly used > tModels to it depending on if it's soap, rest or something else. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-785) find with CASE_INSENSITIVE_SORT throws JPA exception
[ https://issues.apache.org/jira/browse/JUDDI-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-785. - > find with CASE_INSENSITIVE_SORT throws JPA exception > > > Key: JUDDI-785 > URL: https://issues.apache.org/jira/browse/JUDDI-785 > Project: jUDDI > Issue Type: Bug > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Blocker > Fix For: 3.2 > > > JUDDI_764caseInsensitiveSortTModelKey(org.apache.juddi.v3.tck.UDDI_070_FindEntityIntegrationTest) > Time elapsed: 0.066 sec <<< ERROR! > javax.xml.ws.soap.SOAPFaultException: "Encountered "upper" at character 670, > but expected: ["AVG", "COUNT", "KEY", "MAX", "MIN", "SUM", "VALUE", > ]." while parsing JPQL "select t from Tmodel t where 1=1 and > t.entityKey in ( ?1, ?2, ?3, ?4, ?5, ?6, ?7, ?8, ?9, ?10, ?11, ?12, ?13, ?14, > ?15, ?16, ?17, ?18, ?19, ?20, ?21, ?22, ?23, ?24, ?25, ?26, ?27, ?28, ?29, > ?30, ?31, ?32, ?33, ?34, ?35, ?36, ?37, ?38, ?39, ?40, ?41, ?42, ?43, ?44, > ?45, ?46, ?47, ?48, ?49, ?50, ?51, ?52, ?53, ?54, ?55, ?56, ?57, ?58, ?59, > ?60, ?61, ?62, ?63, ?64, ?65, ?66, ?67, ?68, ?69, ?70, ?71, ?72, ?73, ?74, > ?75, ?76, ?77, ?78, ?79, ?80, ?81, ?82, ?83, ?84, ?85, ?86, ?87, ?88, ?89, > ?90, ?91, ?92, ?93, ?94, ?95, ?96, ?97, ?98, ?99, ?100, ?101, ?102, ?103, > ?104, ?105, ?106, ?107, ?108, ?109, ?110, ?111, ?112, ?113, ?114, ?115, ?116, > ?117, ?118, ?119) order by upper(t.name) asc, t.modified desc". See nested > stack trace for original parse error. > FindTModel fb = new FindTModel(); > fb.setAuthInfo(authInfoJoe); > fb.setFindQualifiers(new FindQualifiers()); > > fb.getFindQualifiers().getFindQualifier().add(UDDIConstants.CASE_INSENSITIVE_SORT_TMODEL); > > fb.getFindQualifiers().getFindQualifier().add(UDDIConstants.APPROXIMATE_MATCH); > fb.setName(new Name(UDDIConstants.WILDCARD, null)); > inquiry.findTModel(fb); -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-742) Add test cases for inquiry REST API
[ https://issues.apache.org/jira/browse/JUDDI-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-742. - > Add test cases for inquiry REST API > --- > > Key: JUDDI-742 > URL: https://issues.apache.org/jira/browse/JUDDI-742 > Project: jUDDI > Issue Type: Task >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-752) UDDI_040_BusinessServiceLoadTest fails to run
[ https://issues.apache.org/jira/browse/JUDDI-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-752. - > UDDI_040_BusinessServiceLoadTest fails to run > - > > Key: JUDDI-752 > URL: https://issues.apache.org/jira/browse/JUDDI-752 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Blocker > Fix For: 3.2, 3.3 > > > Basically, the test case is incorrectly setting the parent business's key > when creating N services -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-614) Add additional configuration options juddi-client uddi.xml
[ https://issues.apache.org/jira/browse/JUDDI-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-614. - > Add additional configuration options juddi-client uddi.xml > -- > > Key: JUDDI-614 > URL: https://issues.apache.org/jira/browse/JUDDI-614 > Project: jUDDI > Issue Type: Improvement >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > > Add alternative authentication mechanisms > X2UDDI (WSDL/WADL, etc) ignore SSL errors, > client -> UDDI server ignore SSL errors. > we may also want to roll in settings for signature validation and > certificate verification into it. reference DigSigUtil > trust store overrides -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-818) add sort by name for all pickers
[ https://issues.apache.org/jira/browse/JUDDI-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-818. - > add sort by name for all pickers > > > Key: JUDDI-818 > URL: https://issues.apache.org/jira/browse/JUDDI-818 > Project: jUDDI > Issue Type: Improvement > Components: juddi-gui >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-683) Implement configurable warning banner
[ https://issues.apache.org/jira/browse/JUDDI-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-683. - > Implement configurable warning banner > - > > Key: JUDDI-683 > URL: https://issues.apache.org/jira/browse/JUDDI-683 > Project: jUDDI > Issue Type: New Feature >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Minor > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-816) business and service editor krgrp kr's are not saved
[ https://issues.apache.org/jira/browse/JUDDI-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-816. - > business and service editor krgrp kr's are not saved > > > Key: JUDDI-816 > URL: https://issues.apache.org/jira/browse/JUDDI-816 > Project: jUDDI > Issue Type: Bug > Components: juddi-gui >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > > includes binding template krgrp krs -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-771) fix juddi admin console status page "happy juddi"
[ https://issues.apache.org/jira/browse/JUDDI-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-771. - > fix juddi admin console status page "happy juddi" > - > > Key: JUDDI-771 > URL: https://issues.apache.org/jira/browse/JUDDI-771 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > > the former "happy juddi" page is back, however the part that tests for > database connectivity is broken. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-690) juddi-client java wsdl2uddi may not include uddi-org:protocol:http for all bindings/ports using soap 1.2
[ https://issues.apache.org/jira/browse/JUDDI-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-690. - > juddi-client java wsdl2uddi may not include uddi-org:protocol:http for all > bindings/ports using soap 1.2 > > > Key: JUDDI-690 > URL: https://issues.apache.org/jira/browse/JUDDI-690 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > > keyName="uddi-org:protocol:http" keyValue="uddi:uddi.org:protocol:http" /> > is missing from several of the generated tmodels > source wsdl: > http://wsf.cdyne.com/WeatherWS/Weather.asmx?WSDL > affected ports/bindings > WeatherHttpPost > WeatherSoap12 > WeatherHttpGet > soap 1.1 bindings/port translation are not affected -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-777) mvn build process is broken in windows
[ https://issues.apache.org/jira/browse/JUDDI-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-777. - > mvn build process is broken in windows > -- > > Key: JUDDI-777 > URL: https://issues.apache.org/jira/browse/JUDDI-777 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Kurt T Stam >Priority: Blocker > Fix For: 3.2 > > > [copy] Copying 1 file to > C:\juddi\trunk\juddi-tomcat\target\tomcat\apache-tomcat-6.0.26\lib > [copy] Copying 1 file to > C:\juddi\trunk\juddi-tomcat\target\tomcat\apache-tomcat-6.0.26\endorsed > ackage-tomcat: > INFO] Executed tasks > INFO] > INFO] --- maven-assembly-plugin:2.2-beta-3:single (source-release-assembly) @ > juddi-tomcat --- > INFO] > INFO] Reactor Summary: > INFO] > INFO] jUDDI Tomcat Packaging FAILURE [2:34.348s] > INFO] UDDI TCK Tests SKIPPED > INFO] UDDI TCK Test Runner .. SKIPPED > INFO] jUDDI User Guide -(en-US) . SKIPPED > INFO] jUDDI Dev Guide -(en-US) .. SKIPPED > INFO] jUDDI Document Packaging .. SKIPPED > INFO] jUDDI Distribution Assembly ... SKIPPED > INFO] UDDI Client Distribution Assembly . SKIPPED > INFO] > INFO] BUILD FAILURE > INFO] > INFO] Total time: 2:45.507s > INFO] Finished at: Wed Jan 08 19:21:18 EST 2014 > INFO] Final Memory: 22M/211M > INFO] > ERROR] Failed to execute goal > org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-3:single > (source-release-assembly > on project juddi-tomcat: Execution source-release-assembly of goal > org.apache.maven.plugins:maven-assembly-plugin:2.2- > eta-3:single failed: Illegal/unsupported escape sequence near index 10 > ERROR] > (?!((?!C:\juddi\trunk\juddi-tomcat\target\\)[^\\]+\\)*src\\).*C:\juddi\trunk\juddi-tomcat\target.* > ERROR] ^ > ERROR] -> [Help 1] > ERROR] > ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > ERROR] Re-run Maven using the -X switch to enable full debug logging. > ERROR] > ERROR] For more information about the errors and possible solutions, please > read the following articles: > ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-737) Alter Inquiry API REST endpoints to conform to the recommended uri pattern
[ https://issues.apache.org/jira/browse/JUDDI-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-737. - > Alter Inquiry API REST endpoints to conform to the recommended uri pattern > -- > > Key: JUDDI-737 > URL: https://issues.apache.org/jira/browse/JUDDI-737 > Project: jUDDI > Issue Type: Improvement >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Minor > Fix For: 3.2 > > > http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908158 -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-735) juddi api wsdls do not have fault information listed
[ https://issues.apache.org/jira/browse/JUDDI-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-735. - > juddi api wsdls do not have fault information listed > > > Key: JUDDI-735 > URL: https://issues.apache.org/jira/browse/JUDDI-735 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2, 3.3 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-633) Building a Find Qualifiers for comparison operator such as "greater then" and "less than" for QoS queries
[ https://issues.apache.org/jira/browse/JUDDI-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-633. - > Building a Find Qualifiers for comparison operator such as "greater then" and > "less than" for QoS queries > - > > Key: JUDDI-633 > URL: https://issues.apache.org/jira/browse/JUDDI-633 > Project: jUDDI > Issue Type: New Feature > Components: juddi-client, juddi-tomcat >Affects Versions: 3.1.5 > Environment: Windows 8 Pro. > Tomcat 7.0 > MySQL 5.6 >Reporter: Avinash Ganpat Mahajan >Assignee: Alex O'Ree > Labels: features > Fix For: 3.2 > > Original Estimate: 1,224h > Remaining Estimate: 1,224h > > I am trying to implement QoS aware UDDI searching mechanism. > As QoS attributes are stored in KeyedReferences so needs to have some > qualifiers to give flexibility for searching such as for cost. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-731) add constant values for EntityCreator packages and refactor
[ https://issues.apache.org/jira/browse/JUDDI-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-731. - > add constant values for EntityCreator packages and refactor > --- > > Key: JUDDI-731 > URL: https://issues.apache.org/jira/browse/JUDDI-731 > Project: jUDDI > Issue Type: Improvement >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-663) juddi-gui-disg jar signer is signing the wrong jar file
[ https://issues.apache.org/jira/browse/JUDDI-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-663. - > juddi-gui-disg jar signer is signing the wrong jar file > --- > > Key: JUDDI-663 > URL: https://issues.apache.org/jira/browse/JUDDI-663 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Kurt T Stam > Fix For: 3.2 > > > It needs to sign the jar containing the dependencies -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-693) juddi-gui setup automatic logouts
[ https://issues.apache.org/jira/browse/JUDDI-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-693. - > juddi-gui setup automatic logouts > - > > Key: JUDDI-693 > URL: https://issues.apache.org/jira/browse/JUDDI-693 > Project: jUDDI > Issue Type: Task >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Minor > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-721) juddi-gui edit subscription page incomplete
[ https://issues.apache.org/jira/browse/JUDDI-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-721. - > juddi-gui edit subscription page incomplete > --- > > Key: JUDDI-721 > URL: https://issues.apache.org/jira/browse/JUDDI-721 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > > apparently i forgot to finish the edit existing subscription part of the > page. specifically the population of fields when editing and when saving, > find qualifiers are not parsed, stored or rendered correctly -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-653) Build fails on Ubuntu using OpenJDK
[ https://issues.apache.org/jira/browse/JUDDI-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-653. - > Build fails on Ubuntu using OpenJDK > --- > > Key: JUDDI-653 > URL: https://issues.apache.org/jira/browse/JUDDI-653 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2, 3.3 > > > Fails on the digital signature applet for the ui. > ERROR] Failed to execute goal on project juddi-gui-dsig: Could not resolve > dependencies for project org.apache.juddi:juddi-gui-dsig:jar:3.2.0-SNAPSHOT: > Could not find artifact com.sun.jdk:plugin:jar:1.6.0 at specified path > /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/plugin.jar -> [Help 1] -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-672) create example notifier implementation
[ https://issues.apache.org/jira/browse/JUDDI-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-672. - > create example notifier implementation > -- > > Key: JUDDI-672 > URL: https://issues.apache.org/jira/browse/JUDDI-672 > Project: jUDDI > Issue Type: New Feature >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > > see juddi-examples\subscription-notification-handler -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-776) WSDL/WADL2UDDI truncate or split up long descriptions
[ https://issues.apache.org/jira/browse/JUDDI-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-776. - > WSDL/WADL2UDDI truncate or split up long descriptions > - > > Key: JUDDI-776 > URL: https://issues.apache.org/jira/browse/JUDDI-776 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > > I pointed WSDL2UDDI at this > http://svn.apache.org/repos/asf/juddi/trunk/uddi-ws/src/main/resources/juddi_api_v1.wsdl > And since we have wsdl documentation now (golf claps), it is longer than what > UDDI allows. We either need to truncate it or chop it up into multiple > description elements > javax.xml.ws.soap.SOAPFaultException: The field 'description' must be less > than 256 characters > at > com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178) > at > com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:119) > at > com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:108) > at > com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:78) > at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:135) > at com.sun.proxy.$Proxy56.saveService(Unknown Source) > at org.apache.juddi.samples.WsdlImport.Fire(WsdlImport.java:205) > at > org.apache.juddi.samples.EntryPoint.processInput(EntryPoint.java:214) > at org.apache.juddi.samples.EntryPoint.main(EntryPoint.java:58) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:283) > at java.lang.Thread.run(Thread.java:744) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-791) Login/Logout in admin and juddi-gui
[ https://issues.apache.org/jira/browse/JUDDI-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-791. - > Login/Logout in admin and juddi-gui > --- > > Key: JUDDI-791 > URL: https://issues.apache.org/jira/browse/JUDDI-791 > Project: jUDDI > Issue Type: Bug >Reporter: Kurt T Stam >Assignee: Kurt T Stam > Fix For: 3.2 > > Attachments: JUDDI-791-patch.txt > > > Can we add the username that is logged in, to the admin and juddi-gui? And > then hide the login forms; and display a logout button? At the moment it is > very hard to figure out if you have a valid session; and if you do have one > how to invalidate it. > Also let's talk about replacing the jUDDIAuthenticator with something just a > bit more restrictive so at least the password is checked. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-803) keyGenerator not valid
[ https://issues.apache.org/jira/browse/JUDDI-803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-803. - > keyGenerator not valid > -- > > Key: JUDDI-803 > URL: https://issues.apache.org/jira/browse/JUDDI-803 > Project: jUDDI > Issue Type: Bug > Components: juddi-gui >Reporter: Kurt T Stam >Assignee: Alex O'Ree > Fix For: 3.2 > > > Hi Alex, > Not sure what's going on. I thought this worked before. I'm trying create > keyPartition. I'm setting my key to 'uddi:www.kurt.com:keyGenerator' > and am getting the error: 'A tModel partition key generator must have a name > that ends with :keyGenerator ' -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-760) correct links for mailing list
[ https://issues.apache.org/jira/browse/JUDDI-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-760. - > correct links for mailing list > -- > > Key: JUDDI-760 > URL: https://issues.apache.org/jira/browse/JUDDI-760 > Project: jUDDI > Issue Type: Task >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2, 3.3 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-805) service edit may fail to render correctly under certain conditions
[ https://issues.apache.org/jira/browse/JUDDI-805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-805. - > service edit may fail to render correctly under certain conditions > -- > > Key: JUDDI-805 > URL: https://issues.apache.org/jira/browse/JUDDI-805 > Project: jUDDI > Issue Type: Bug > Components: juddi-gui >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > > if the button's don't show up, then something failed, such as an NPE -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-705) SaveNode crashes
[
https://issues.apache.org/jira/browse/JUDDI-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kurt T Stam closed JUDDI-705.
-
> SaveNode crashes
>
>
> Key: JUDDI-705
> URL: https://issues.apache.org/jira/browse/JUDDI-705
> Project: jUDDI
> Issue Type: Bug
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
> Fix For: 3.2
>
>
> Code:
> SaveNode node = new SaveNode();
> node.setAuthInfo(rootAuthToken.getAuthInfo());
> Node n = new Node();
> n.setClientName("juddicloud");
> n.setName("juddicloud");
>
> n.setCustodyTransferUrl("http://uddi-jbossoverlord.rhcloud.com/services/custody-transfer";);
> n.setDescription("juddicloud");
>
> n.setInquiryUrl("http://uddi-jbossoverlord.rhcloud.com/services/inquiry";);
>
> n.setJuddiApiUrl("http://uddi-jbossoverlord.rhcloud.com/services/juddi-api";);
>
> n.setPublishUrl("http://uddi-jbossoverlord.rhcloud.com/services/publish";);
> n.setSecurityUrl(
> "http://uddi-jbossoverlord.rhcloud.com/services/security";);
>
> n.setSubscriptionListenerUrl("http://uddi-jbossoverlord.rhcloud.com/services/subscription-listener";);
>
> n.setSubscriptionUrl("http://uddi-jbossoverlord.rhcloud.com/services/subscription";);
> node.getNode().add(n);
> juddi.saveNode(node);
> Service stack trace:
> INFO: Application
> {urn:juddi-apache-org:v3_service}JUDDIApiService#{urn:juddi-ap
> ache-org:v3_service}save_Node has thrown exception, unwinding now:
> org.apache.ju
> ddi.v3.error.AuthTokenRequiredException: Invalid authentication information
> Nov 09, 2013 9:49:28 PM org.apache.cxf.phase.PhaseInterceptorChain
> doDefaultLogg
> ing
> WARNING: Application
> {urn:juddi-apache-org:v3_service}JUDDIApiService#{urn:juddi
> -apache-org:v3_service}save_Node has thrown exception, unwinding now
> org.apache.cxf.interceptor.Fault: The transaction has been rolled back. See
> the
> nested exceptions for details on the errors that occurred.
> at
> org.apache.cxf.service.invoker.AbstractInvoker.createFault(AbstractIn
> voker.java:162)
> at
> org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.createFault(AbstractJ
> AXWSMethodInvoker.java:213)
> at
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker
> .java:128)
> at
> org.apache.cxf.jaxws.AbstractJAXWSMethodInvoker.invoke(AbstractJAXWSM
> ethodInvoker.java:178)
> at
> org.apache.cxf.jaxws.JAXWSMethodInvoker.invoke(JAXWSMethodInvoker.jav
> a:68)
> at
> org.apache.cxf.service.invoker.AbstractInvoker.invoke(AbstractInvoker
> .java:75)
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInv
> okerInterceptor.java:58)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:47
> 1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecu
> tor.java:37)
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(Se
> rviceInvokerInterceptor.java:107)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseIntercept
> orChain.java:271)
> at
> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainIniti
> ationObserver.java:121)
> at
> org.apache.cxf.transport.http.AbstractHTTPDestination.invoke(Abstract
> HTTPDestination.java:239)
> at
> org.apache.cxf.transport.servlet.ServletController.invokeDestination(
> ServletController.java:223)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletCont
> roller.java:203)
> at
> org.apache.cxf.transport.servlet.ServletController.invoke(ServletCont
> roller.java:137)
> at
> org.apache.cxf.transport.servlet.CXFNonSpringServlet.invoke(CXFNonSpr
> ingServlet.java:158)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(Ab
> stractHTTPServlet.java:243)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.doPost(AbstractH
> TTPServlet.java:163)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at
> org.apache.cxf.transport.servlet.AbstractHTTPServlet.service(Abstract
> HTTPServlet.java:219)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
> icationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
> ilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
> alve.java:233)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
> alve.java:191)
> at
> org.apache.catalina.authenticator.Authenticato
[jira] [Closed] (JUDDI-787) SORT_BY_NAME_DESC find qualifier for find Binding is an invalid combo, not flagged by juddi
[ https://issues.apache.org/jira/browse/JUDDI-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-787. - > SORT_BY_NAME_DESC find qualifier for find Binding is an invalid combo, not > flagged by juddi > --- > > Key: JUDDI-787 > URL: https://issues.apache.org/jira/browse/JUDDI-787 > Project: jUDDI > Issue Type: Bug > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-740) juddi REST services do not function for JSON encoded responses
[ https://issues.apache.org/jira/browse/JUDDI-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-740. - > juddi REST services do not function for JSON encoded responses > -- > > Key: JUDDI-740 > URL: https://issues.apache.org/jira/browse/JUDDI-740 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-829) adjust validation rules for bindingTemplate/tModelInstanceInfo
[ https://issues.apache.org/jira/browse/JUDDI-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-829. - > adjust validation rules for bindingTemplate/tModelInstanceInfo > -- > > Key: JUDDI-829 > URL: https://issues.apache.org/jira/browse/JUDDI-829 > Project: jUDDI > Issue Type: Bug > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > > ref JUDDI-780 > the UDDIv2 spec states that a binding template must have a > TModelInstanceDetails, however there is no requirement for a > TModelInstanceInfo instance (0 or more) > in UDDIv3. "The tModelInstanceDetails structure is a list of one or more > tModelInstanceInfo elements." (1 or more) > Obviously, this is a significant difference from v2 to v3. Either we need to > change the schema and generated v2 code, or somehow adjust the validation > rules based on the api version -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-768) Confirm juddi smtp notifier can deliver to authenticated mail servers
[ https://issues.apache.org/jira/browse/JUDDI-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-768. - > Confirm juddi smtp notifier can deliver to authenticated mail servers > - > > Key: JUDDI-768 > URL: https://issues.apache.org/jira/browse/JUDDI-768 > Project: jUDDI > Issue Type: Task > Environment: using hmail on windows as a mail server >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > > I was testing with the juddi-tck-runner and was only able to get the smtp > tests to pass when the juddi smtp notifier did not need to authenticate to > deliver mail. I'm not sure what the root cause is. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-780) Add uddiv2 support for the client and server side
[ https://issues.apache.org/jira/browse/JUDDI-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-780. - > Add uddiv2 support for the client and server side > - > > Key: JUDDI-780 > URL: https://issues.apache.org/jira/browse/JUDDI-780 > Project: jUDDI > Issue Type: Improvement > Components: core, juddi-client >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-623) WSDL files are not syncronized with JUDDI API ws
[ https://issues.apache.org/jira/browse/JUDDI-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-623. - > WSDL files are not syncronized with JUDDI API ws > > > Key: JUDDI-623 > URL: https://issues.apache.org/jira/browse/JUDDI-623 > Project: jUDDI > Issue Type: Bug >Affects Versions: 3.1.5 >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Blocker > Fix For: 3.2 > > > According to the WSDL, the JUDDI API ws, there is a method called > save_Clerk, that takes in an input of "save_clerkInfo" and spits out a > clerk array. > However in the Java code base, it looks like it was renamed at some > point to "ClerkDetail" instead of clerk[] and "SaveClerk" instead of > "save_clerkInfo". -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-692) juddi-gui confirm all end user verbiage is i18n-ized
[ https://issues.apache.org/jira/browse/JUDDI-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-692. - > juddi-gui confirm all end user verbiage is i18n-ized > > > Key: JUDDI-692 > URL: https://issues.apache.org/jira/browse/JUDDI-692 > Project: jUDDI > Issue Type: Task >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-739) juddi-gui businessEditor throws up
[ https://issues.apache.org/jira/browse/JUDDI-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-739. - > juddi-gui businessEditor throws up > -- > > Key: JUDDI-739 > URL: https://issues.apache.org/jira/browse/JUDDI-739 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2, 3.3 > > > Somehow the document formatted removed a few necessary characters. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-710) juddi-gui consolidate all config settings
[ https://issues.apache.org/jira/browse/JUDDI-710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-710. - > juddi-gui consolidate all config settings > - > > Key: JUDDI-710 > URL: https://issues.apache.org/jira/browse/JUDDI-710 > Project: jUDDI > Issue Type: Improvement >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > > move all config settings from the current config.properties into the uddi.xml > format. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-625) Add REST style bindings for inquiry find_XXX
[ https://issues.apache.org/jira/browse/JUDDI-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-625. - > Add REST style bindings for inquiry find_XXX > > > Key: JUDDI-625 > URL: https://issues.apache.org/jira/browse/JUDDI-625 > Project: jUDDI > Issue Type: Improvement > Components: core, CXF >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-686) track and map requestors IP address to auth token
[ https://issues.apache.org/jira/browse/JUDDI-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-686. - > track and map requestors IP address to auth token > - > > Key: JUDDI-686 > URL: https://issues.apache.org/jira/browse/JUDDI-686 > Project: jUDDI > Issue Type: Improvement >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > > basically, we can make auth token's a bit more secure by obtaining the > requestor's ip address and store that along with the auth token (server > side). upon validating an new request, we can then compare IP addresses. if > they are different, invalidate the token and force reauthentication -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-782) Add v2 API
[ https://issues.apache.org/jira/browse/JUDDI-782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-782. - > Add v2 API > -- > > Key: JUDDI-782 > URL: https://issues.apache.org/jira/browse/JUDDI-782 > Project: jUDDI > Issue Type: Sub-task > Components: core, juddi-client >Reporter: Kurt T Stam >Assignee: Alex O'Ree > Fix For: 3.2 > > > Split uddi-ws into uddiv2, uddiv3 and juddiv1 api modules. Hopefully each > can be generated straight from the wsdl. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-794) 'admin' users cannot delete items not owned by them
[ https://issues.apache.org/jira/browse/JUDDI-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-794. - > 'admin' users cannot delete items not owned by them > --- > > Key: JUDDI-794 > URL: https://issues.apache.org/jira/browse/JUDDI-794 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-718) juddi-client UDDIClerkServlet does not register annotated services on startup
[ https://issues.apache.org/jira/browse/JUDDI-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-718. - > juddi-client UDDIClerkServlet does not register annotated services on startup > - > > Key: JUDDI-718 > URL: https://issues.apache.org/jira/browse/JUDDI-718 > Project: jUDDI > Issue Type: Bug >Affects Versions: 3.1.5 >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > > the UDDIClerkServlet is designed (I think) to make registration of endpoints > easier by hooking into the servlet lifecycle for automatic registration and > unregistration on startup and shutdown. Currently it does this for only > wsdl's defined in the juddi client config and not for annotated services. > Might as well do both -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-827) misc usability enhancements
[ https://issues.apache.org/jira/browse/JUDDI-827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-827. - > misc usability enhancements > --- > > Key: JUDDI-827 > URL: https://issues.apache.org/jira/browse/JUDDI-827 > Project: jUDDI > Issue Type: Bug > Components: juddi-gui >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > > adding name/lang filtering on all browse and modal pages > truncate long name/descriptions from browse/modal pages -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-834) login always uses the 'default' nodename
[ https://issues.apache.org/jira/browse/JUDDI-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-834. - > login always uses the 'default' nodename > > > Key: JUDDI-834 > URL: https://issues.apache.org/jira/browse/JUDDI-834 > Project: jUDDI > Issue Type: Bug > Components: juddi-gui >Reporter: Kurt T Stam >Assignee: Kurt T Stam > Fix For: 3.2 > > > I'm have juddi deployed to eap. I navigate to the juddi-gui and pick 'jboss7' > in the settings. In the debugger I can see it picking the correct settings in > the UDDIHub. I try logging in, and I see it using the 'default' node instead > so now the endpoint is wrong and login fails > 14:15:19,087 ERROR > [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/juddiv3].[UDDISecurityWS]] > (http-/127.0.0.1:8080-2) JBWEB000235: Allocate exception for servlet > UDDISecurityWS: javax.xml.ws.WebServiceException: JBWS024032: Cannot obtain > endpoint jboss.ws:context=juddiv3,endpoint=UDDISecurityWS > at > org.jboss.wsf.stack.cxf.transport.ServletHelper.initServiceEndpoint(ServletHelper.java:97) > [jbossws-cxf-server-4.1.4.Final-redhat-7.jar:4.1.4.Final-redhat-7] > at > org.jboss.wsf.stack.cxf.transport.ServletHelper.initEndpoint(ServletHelper.java:71) > [jbossws-cxf-server-4.1.4.Final-redhat-7.jar:4.1.4.Final-redhat-7] > at org.jboss.wsf.stack.cxf.CXFServletExt.loadBus(CXFServletExt.java:67) > [jbossws-cxf-server-4.1.4.Final-redhat-7.jar:4.1.4.Final-redhat-7] > at org.jboss.wsf.stack.cxf.CXFServletExt.init(CXFServletExt.java:61) > [jbossws-cxf-server-4.1.4.Final-redhat-7.jar:4.1.4.Final-redhat-7] > at > org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194) > [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at > org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:950) > [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:151) > [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) > [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at > org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:407) > [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at > org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) > [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at > org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) > [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at > org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) > [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) > [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) > [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) > [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) > [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) > [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) > [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) > [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] > at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_51] -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-694) juddi-gui enable jsp precompiling (build time)
[ https://issues.apache.org/jira/browse/JUDDI-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-694. - > juddi-gui enable jsp precompiling (build time) > -- > > Key: JUDDI-694 > URL: https://issues.apache.org/jira/browse/JUDDI-694 > Project: jUDDI > Issue Type: Task >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Minor > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-763) juddi-gui wadl importer fails to run (no feedback)
[ https://issues.apache.org/jira/browse/JUDDI-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-763. - > juddi-gui wadl importer fails to run (no feedback) > -- > > Key: JUDDI-763 > URL: https://issues.apache.org/jira/browse/JUDDI-763 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-711) digital signature util - add support for trust store validation via system properties
[ https://issues.apache.org/jira/browse/JUDDI-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-711. - > digital signature util - add support for trust store validation via system > properties > - > > Key: JUDDI-711 > URL: https://issues.apache.org/jira/browse/JUDDI-711 > Project: jUDDI > Issue Type: Bug > Components: juddi-client >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-804) find tModel NPE
[ https://issues.apache.org/jira/browse/JUDDI-804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-804. - > find tModel NPE > --- > > Key: JUDDI-804 > URL: https://issues.apache.org/jira/browse/JUDDI-804 > Project: jUDDI > Issue Type: Bug >Reporter: Kurt T Stam >Assignee: Alex O'Ree > Fix For: 3.2 > > > I'm trying to find all the keyGenerator tModel by searching by tModel > By > Unique Identifier > Search term: '%keyGenerator%', leaving the language field > empty, and approximateMatch on. I'm getting an NPE: > 2014-01-22 12:56:45,991 ERROR [org.apache.juddi] - SOAP Fault returned: The > technical model was not found for the given key: %keygeneratorThe technical > model was not found for the given key: %keygenerator > 2014-01-22 12:56:45,992 ERROR [org.apache.juddi] - NPE! Please report! null > java.lang.NullPointerException > at > org.apache.juddi.webconsole.hub.UddiHub.FindtModels(UddiHub.java:1900) > Searching my name works ok. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-714) Adding juddi-client.net to client distribution package
[ https://issues.apache.org/jira/browse/JUDDI-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-714. - > Adding juddi-client.net to client distribution package > -- > > Key: JUDDI-714 > URL: https://issues.apache.org/jira/browse/JUDDI-714 > Project: jUDDI > Issue Type: New Feature >Reporter: Alex O'Ree >Assignee: Kurt T Stam > Fix For: 3.2 > > > we'll need the binaries for juddi-client.net.dll, the xml doc for it and the > source for the examples project. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-814) update install data to reflect wsdl/wadl to uddi mappings
[ https://issues.apache.org/jira/browse/JUDDI-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-814. - > update install data to reflect wsdl/wadl to uddi mappings > - > > Key: JUDDI-814 > URL: https://issues.apache.org/jira/browse/JUDDI-814 > Project: jUDDI > Issue Type: Task > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-661) remove endpoint config from the gui's config.xml (since that is already defined in the uddi.xml)
[ https://issues.apache.org/jira/browse/JUDDI-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-661. - > remove endpoint config from the gui's config.xml (since that is already > defined in the uddi.xml) > > > Key: JUDDI-661 > URL: https://issues.apache.org/jira/browse/JUDDI-661 > Project: jUDDI > Issue Type: Task >Reporter: Kurt T Stam >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-702) reduce code duplication for CryptorFactory
[ https://issues.apache.org/jira/browse/JUDDI-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-702. - > reduce code duplication for CryptorFactory > -- > > Key: JUDDI-702 > URL: https://issues.apache.org/jira/browse/JUDDI-702 > Project: jUDDI > Issue Type: Improvement >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-679) juddi-gui NPE performing find service by id
[ https://issues.apache.org/jira/browse/JUDDI-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-679. - > juddi-gui NPE performing find service by id > --- > > Key: JUDDI-679 > URL: https://issues.apache.org/jira/browse/JUDDI-679 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-701) Run findbugs before release
[ https://issues.apache.org/jira/browse/JUDDI-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-701. - > Run findbugs before release > --- > > Key: JUDDI-701 > URL: https://issues.apache.org/jira/browse/JUDDI-701 > Project: jUDDI > Issue Type: Task >Reporter: Alex O'Ree >Assignee: Alex O'Ree >Priority: Blocker > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-678) juddi-gui does not trap expired auth tokens correctly
[ https://issues.apache.org/jira/browse/JUDDI-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-678. - > juddi-gui does not trap expired auth tokens correctly > - > > Key: JUDDI-678 > URL: https://issues.apache.org/jira/browse/JUDDI-678 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-738) add REST url into the default install data
[ https://issues.apache.org/jira/browse/JUDDI-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-738. - > add REST url into the default install data > -- > > Key: JUDDI-738 > URL: https://issues.apache.org/jira/browse/JUDDI-738 > Project: jUDDI > Issue Type: Task >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-774) juddi-client refactor confusing method names, add javadoc
[ https://issues.apache.org/jira/browse/JUDDI-774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-774. - > juddi-client refactor confusing method names, add javadoc > - > > Key: JUDDI-774 > URL: https://issues.apache.org/jira/browse/JUDDI-774 > Project: jUDDI > Issue Type: Improvement >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (JUDDI-671) Convert the uddi-samples projects maven
[ https://issues.apache.org/jira/browse/JUDDI-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt T Stam closed JUDDI-671. - > Convert the uddi-samples projects maven > --- > > Key: JUDDI-671 > URL: https://issues.apache.org/jira/browse/JUDDI-671 > Project: jUDDI > Issue Type: Bug >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.2 > > > convert the following to maven > subscription-notification-handler > uddi-samples -- This message was sent by Atlassian JIRA (v6.1.5#6160)
