dev  

Messages by Thread

• [jira] [Created] (JUDDI-1006) Saving an Access Point Type Alex O'Ree (Jira)
• [ANNOUNCE] jUDDI v3.3.8 Alex O'Ree
• [GitHub] [juddi] spyhunter99 merged pull request #1: Fixed Spelling. GitBox
• [GitHub] [juddi] spyhunter99 commented on issue #1: Fixed Spelling. GitBox
• [VOTE] jUDDI v3.3.8 Alex O'Ree
  • Re: [VOTE] jUDDI v3.3.8 Alex O'Ree
  • Re: [VOTE] jUDDI v3.3.8 Steve Viens
  • Re: [VOTE] jUDDI v3.3.8 Kurt Stam
  • Re: [VOTE] jUDDI v3.3.8 Anil Saldanha
  • Re: [VOTE] jUDDI v3.3.8 Kurt Stam
  • Re: [VOTE] jUDDI v3.3.8 Alex O'Ree
• [jira] [Reopened] (JUDDI-1003) spring-web jar supplied with latest JUDDI distribution has security vulnerability Amol Bhonsle (Jira)
• [jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema Amol Bhonsle (Jira)
  • [jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema Amol Bhonsle (Jira)
  • [jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema Amol Bhonsle (Jira)
  • [jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema ASF subversion and git services (Jira)
• [jira] [Updated] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema Amol Bhonsle (Jira)
  • [jira] [Updated] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema Amol Bhonsle (Jira)
  • [jira] [Updated] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema Amol Bhonsle (Jira)
  • [jira] [Updated] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema Amol Bhonsle (Jira)
  • [jira] [Updated] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema Amol Bhonsle (Jira)
  • [jira] [Updated] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema Alex O'Ree (Jira)
  • [jira] [Updated] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema Alex O'Ree (Jira)
• [jira] [Created] (JUDDI-1005) Need To have correct options to upgrade JUDDI DB Schema Amol Bhonsle (Jira)
• [GitHub] [juddi] JLLeitschuh opened a new pull request #7: [SECURITY] Use HTTPS to resolve dependencies in Maven Build GitBox
  • [GitHub] [juddi] spyhunter99 merged pull request #7: [SECURITY] Use HTTPS to resolve dependencies in Maven Build GitBox
• [jira] [Resolved] (JUDDI-937) PolicyRoundRobin not working without service cache Alex O'Ree (Jira)
• [jira] [Commented] (JUDDI-1004) JUDDI-3.3.7 With SQL Server Database Gives Primary Key Violation For Table j3_category_bag Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-1004) JUDDI-3.3.7 With SQL Server Database Gives Primary Key Violation For Table j3_category_bag Amol Bhonsle (Jira)
  • [jira] [Commented] (JUDDI-1004) JUDDI-3.3.7 With SQL Server Database Gives Primary Key Violation For Table j3_category_bag Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-1004) JUDDI-3.3.7 With SQL Server Database Gives Primary Key Violation For Table j3_category_bag ASF subversion and git services (Jira)
• [jira] [Updated] (JUDDI-1004) JUDDI-3.3.7 With SQL Server Database Gives Primary Key Violation For Table j3_category_bag Amol Bhonsle (Jira)
  • [jira] [Updated] (JUDDI-1004) JUDDI-3.3.7 With SQL Server Database Gives Primary Key Violation For Table j3_category_bag Amol Bhonsle (Jira)
  • [jira] [Updated] (JUDDI-1004) JUDDI-3.3.7 With SQL Server Database Gives Primary Key Violation For Table j3_category_bag Amol Bhonsle (Jira)
  • [jira] [Updated] (JUDDI-1004) JUDDI-3.3.7 With SQL Server Database Gives Primary Key Violation For Table j3_category_bag Amol Bhonsle (Jira)
  • [jira] [Updated] (JUDDI-1004) JUDDI-3.3.7 With SQL Server Database Gives Primary Key Violation For Table j3_category_bag Alex O'Ree (Jira)
  • [jira] [Updated] (JUDDI-1004) JUDDI-3.3.7 With SQL Server Database Gives Primary Key Violation For Table j3_category_bag Alex O'Ree (Jira)
• [jira] [Created] (JUDDI-1004) JUDDI-3.3.7 With SQL Server Database Gives Primary Key Violation For Table j3_category_bag Amol Bhonsle (Jira)
• [jira] [Comment Edited] (JUDDI-937) PolicyRoundRobin not working without service cache Alex O'Ree (Jira)
• Call for presentations for ApacheCon North America 2020 now open Rich Bowen
• [jira] [Closed] (JUDDI-652) Tomcat logs a number of severe warnings during shutdown from juddi-gui Alex O'Ree (Jira)
• [jira] [Work started] (JUDDI-937) PolicyRoundRobin not working without service cache Alex O'Ree (Jira)
• [jira] [Assigned] (JUDDI-937) PolicyRoundRobin not working without service cache Alex O'Ree (Jira)
• [jira] [Resolved] (JUDDI-969) Derby dead lock Alex O'Ree (Jira)
• [jira] [Resolved] (JUDDI-993) InVm transport for embedded juddi needs to handle authentication and a sample for usage Alex O'Ree (Jira)
• [jira] [Updated] (JUDDI-993) InVm transport for embedded juddi needs to handle authentication and a sample for usage Alex O'Ree (Jira)
  • [jira] [Updated] (JUDDI-993) InVm transport for embedded juddi needs to handle authentication and a sample for usage Alex O'Ree (Jira)
• [jira] [Commented] (JUDDI-993) InVm transport for embedded juddi needs to handle authentication ASF subversion and git services (Jira)
• [jira] [Assigned] (JUDDI-993) InVm transport for embedded juddi needs to handle authentication Alex O'Ree (Jira)
• [jira] [Work started] (JUDDI-993) InVm transport for embedded juddi needs to handle authentication Alex O'Ree (Jira)
• [jira] [Resolved] (JUDDI-1002) tModelInstanceInfo value does not check for maximum length Alex O'Ree (Jira)
• [jira] [Updated] (JUDDI-1002) tModelInstanceInfo value does not check for maximum length Alex O'Ree (Jira)
• [jira] [Resolved] (JUDDI-1003) spring-web jar supplied with latest JUDDI distribution has security vulnerability Alex O'Ree (Jira)
  • [jira] [Resolved] (JUDDI-1003) spring-web jar supplied with latest JUDDI distribution has security vulnerability Alex O'Ree (Jira)
• [jira] [Updated] (JUDDI-1003) spring-web jar supplied with latest JUDDI distribution has security vulnerability Alex O'Ree (Jira)
• [jira] [Assigned] (JUDDI-1003) spring-web jar supplied with latest JUDDI distribution has security vulnerability Alex O'Ree (Jira)
• [jira] [Commented] (JUDDI-1003) spring-web jar supplied with latest JUDDI distribution has security vulnerability Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-1003) spring-web jar supplied with latest JUDDI distribution has security vulnerability Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-1003) spring-web jar supplied with latest JUDDI distribution has security vulnerability Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-1003) spring-web jar supplied with latest JUDDI distribution has security vulnerability ASF subversion and git services (Jira)
  • [jira] [Commented] (JUDDI-1003) spring-web jar supplied with latest JUDDI distribution has security vulnerability ASF subversion and git services (Jira)
• [jira] [Created] (JUDDI-1003) spring-web jar supplied with latest JUDDI distribution has security vulnerability Amol Bhonsle (Jira)
• [ANNOUNCE] jUDDI v3.3.7 Alex O'Ree
• [jira] [Closed] (JUDDI-997) Admin gui has strange behavior and no feedback if the login fails Alex O'Ree (Jira)
• [jira] [Closed] (JUDDI-995) Add automated generation of sha512 hashes during the build Alex O'Ree (Jira)
• [jira] [Closed] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF Alex O'Ree (Jira)
• [jira] [Closed] (JUDDI-996) Admin gui, get all client subscriptions throws a classcast error Alex O'Ree (Jira)
• [jira] [Closed] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
• [jira] [Closed] (JUDDI-1000) Update embedded tomcat to the latest version available Alex O'Ree (Jira)
• [jira] [Commented] (JUDDI-1002) tModelInstanceInfo value does not check for maximum length ASF subversion and git services (Jira)
  • [jira] [Commented] (JUDDI-1002) tModelInstanceInfo value does not check for maximum length ASF subversion and git services (Jira)
• [jira] [Created] (JUDDI-1002) tModelInstanceInfo value does not check for maximum length Alex O'Ree (Jira)
• [jira] [Updated] (JUDDI-1001) Add additional build/test profile for mssql and postgres for both hibernate and openjpa Alex O'Ree (Jira)
• [jira] [Created] (JUDDI-1001) Add additional build/test profile for mssql Alex O'Ree (Jira)
• [jira] [Reopened] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Rahul S (Jira)
• [jira] [Comment Edited] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Amol Bhonsle (Jira)
• [VOTE] jUDDI v3.3.7 Alex O'Ree
  • Re: [VOTE] jUDDI v3.3.7 Alex O'Ree
  • Re: [VOTE] jUDDI v3.3.7 Kurt Stam
  • Re: [VOTE] jUDDI v3.3.7 Kurt Stam
  • Re: [VOTE] jUDDI v3.3.7 Matthieu Ghilain
  • Re: [VOTE] jUDDI v3.3.7 Alex O'Ree
  • Re: [VOTE] jUDDI v3.3.7 Alex O'Ree
  • Re: [VOTE] jUDDI v3.3.7 Alex O'Ree
  • Re: [VOTE] jUDDI v3.3.7 Kurt Stam
  • Re: [VOTE] jUDDI v3.3.7 Alex O'Ree
  • Re: [VOTE] jUDDI v3.3.7 Alex O'Ree
  • Re: [VOTE] jUDDI v3.3.7 Alex O'Ree
  • Re: [VOTE] jUDDI v3.3.7 Anil Saldanha
  • Re: [VOTE] jUDDI v3.3.7 Kurt Stam
  • Re: [VOTE] jUDDI v3.3.7 Alex O'Ree
  • Re: [VOTE] jUDDI v3.3.7 Steve Viens
• [jira] [Resolved] (JUDDI-854) update cloud instance Alex O'Ree (Jira)
• [jira] [Resolved] (JUDDI-991) JUDDI Uses EOL Version of Apache CXF Alex O'Ree (Jira)
• [jira] [Resolved] (JUDDI-995) Add automated generation of sha512 hashes during the build Alex O'Ree (Jira)
• [jira] [Assigned] (JUDDI-995) Add automated generation of sha512 hashes during the build Alex O'Ree (Jira)
• [jira] [Resolved] (JUDDI-1000) Update embedded tomcat to the latest version available Alex O'Ree (Jira)
• [jira] [Commented] (JUDDI-1000) Update embedded tomcat to the latest version available ASF subversion and git services (Jira)
• [jira] [Updated] (JUDDI-995) Add automated generation of sha512 hashes during the build Alex O'Ree (Jira)
• [jira] [Resolved] (JUDDI-998) when using the gui, create, new business name is incorrectly stored as OK Alex O'Ree (Jira)
• [jira] [Commented] (JUDDI-998) when using the gui, create, new business name is incorrectly stored as OK Alex O'Ree (Jira)
• [jira] [Work started] (JUDDI-998) when using the gui, create, new business name is incorrectly stored as OK Alex O'Ree (Jira)
• [jira] [Resolved] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Resolved] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
• [jira] [Created] (JUDDI-1000) Update embedded tomcat to the latest version available Alex O'Ree (Jira)
• [jira] [Updated] (JUDDI-998) when using the gui, create, new business name is incorrectly stored as OK Alex O'Ree (Jira)
  • [jira] [Updated] (JUDDI-998) when using the gui, create, new business name is incorrectly stored as OK Alex O'Ree (Jira)
  • [jira] [Updated] (JUDDI-998) when using the gui, create, new business name is incorrectly stored as OK Alex O'Ree (Jira)
  • [jira] [Updated] (JUDDI-998) when using the gui, create, new business name is incorrectly stored as OK Alex O'Ree (Jira)
• [jira] [Assigned] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
• [jira] [Issue Comment Deleted] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Amol Bhonsle (Jira)
• [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Rahul S (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Rahul S (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Amol Bhonsle (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Rahul S (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) ASF subversion and git services (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) ASF subversion and git services (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Amol Bhonsle (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Amol Bhonsle (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Amol Bhonsle (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Amol Bhonsle (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Amol Bhonsle (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Rahul S (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Rahul S (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Amol Bhonsle (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Amol Bhonsle (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Amol Bhonsle (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Amol Bhonsle (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Amol Bhonsle (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Amol Bhonsle (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Amol Bhonsle (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Amol Bhonsle (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Commented] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
• [jira] [Updated] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Rahul S (Jira)
  • [jira] [Updated] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Rahul S (Jira)
  • [jira] [Updated] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Rahul S (Jira)
  • [jira] [Updated] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Rahul S (Jira)
  • [jira] [Updated] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Updated] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Updated] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Updated] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Amol Bhonsle (Jira)
  • [jira] [Updated] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Updated] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Updated] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Updated] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Alex O'Ree (Jira)
  • [jira] [Updated] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Amol Bhonsle (Jira)
• [jira] [Created] (JUDDI-999) Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000) Rahul S (Jira)
• Fwd: Let's Encrypt certificate expiration notice for domain "demo.juddi.apache.org" Alex O'Ree
  • Re: Let's Encrypt certificate expiration notice for domain "demo.juddi.apache.org" Alex O'Ree
  • Re: Let's Encrypt certificate expiration notice for domain "demo.juddi.apache.org" Alex O'Ree
  • Re: Let's Encrypt certificate expiration notice for domain "demo.juddi.apache.org" Kurt Stam
• ApacheCon North America 2020, project participation Rich Bowen
• [jira] [Created] (JUDDI-998) when using the gui, create, new busimess name is incorrectly stored as OK Alex O'Ree (JIRA)
• [jira] [Commented] (JUDDI-997) Admin gui has strange behavior and no feedback if the login fails ASF subversion and git services (JIRA)
• [jira] [Resolved] (JUDDI-997) Admin gui has strange behavior and no feedback if the login fails Alex O'Ree (JIRA)
• [jira] [Updated] (JUDDI-997) Admin gui has strange behavior and no feedback if the login fails Alex O'Ree (JIRA)
• [jira] [Resolved] (JUDDI-996) Admin gui, get all client subscriptions throws a classcast error Alex O'Ree (JIRA)
• [jira] [Created] (JUDDI-997) Admin gui has strange behavior and no feedback if the login fails Alex O'Ree (JIRA)
• [jira] [Commented] (JUDDI-996) Admin gui, get all client subscriptions throws a classcast error ASF subversion and git services (JIRA)
  • [jira] [Commented] (JUDDI-996) Admin gui, get all client subscriptions throws a classcast error ASF subversion and git services (JIRA)
• [jira] [Work started] (JUDDI-996) Admin gui, get all client subscriptions throws a classcast error Alex O'Ree (JIRA)
• [jira] [Assigned] (JUDDI-996) Admin gui, get all client subscriptions throws a classcast error Alex O'Ree (JIRA)
• [jira] [Created] (JUDDI-996) Admin gui, get all client subscriptions t Alex O'Ree (JIRA)
• [jira] [Updated] (JUDDI-996) Admin gui, get all client subscriptions throws a classcast error Alex O'Ree (JIRA)
  • [jira] [Updated] (JUDDI-996) Admin gui, get all client subscriptions throws a classcast error Alex O'Ree (JIRA)
  • [jira] [Updated] (JUDDI-996) Admin gui, get all client subscriptions throws a classcast error Alex O'Ree (JIRA)
  • [jira] [Updated] (JUDDI-996) Admin gui, get all client subscriptions throws a classcast error Alex O'Ree (JIRA)
  • [jira] [Updated] (JUDDI-996) Admin gui, get all client subscriptions throws a classcast error Alex O'Ree (JIRA)
  • [jira] [Updated] (JUDDI-996) Admin gui, get all client subscriptions throws a classcast error Alex O'Ree (JIRA)
  • [jira] [Updated] (JUDDI-996) Admin gui, get all client subscriptions throws a classcast error Alex O'Ree (JIRA)
  • [jira] [Updated] (JUDDI-996) Admin gui, get all client subscriptions throws a classcast error Alex O'Ree (JIRA)
• Updating the demo site Alex O'Ree
  • Re: Updating the demo site Kurt Stam
  • Re: Updating the demo site Alex O'Ree
  • Re: Updating the demo site Steve Viens
  • Re: Updating the demo site Alex O'Ree
  • Re: Updating the demo site Alex O'Ree

• Earlier messages
• Later messages