[jira] [Commented] (JUDDI-1002) tModelInstanceInfo value does not check for maximum length

[ASF subversion and git services (Jira)]

[ 
https://issues.apache.org/jira/browse/JUDDI-1002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000306#comment-17000306
 ] 

ASF subversion and git services commented on JUDDI-1002:


Commit 299d918f165696e1da0806e109d71ca363a73416 in juddi's branch 
refs/heads/feature/JUDDI-1002 from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=299d918 ]

JUDDI-1002 this adds length validation to tmodel instance info


> tModelInstanceInfo value does not check for maximum length
> --
>
> Key: JUDDI-1002
> URL: https://issues.apache.org/jira/browse/JUDDI-1002
> Project: jUDDI
>  Issue Type: Improvement
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
>Priority: Minor
>




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

[jira] [Created] (JUDDI-1002) tModelInstanceInfo value does not check for maximum length

[Alex O'Ree (Jira)]

Alex O'Ree created JUDDI-1002:
-

 Summary: tModelInstanceInfo value does not check for maximum length
 Key: JUDDI-1002
 URL: https://issues.apache.org/jira/browse/JUDDI-1002
 Project: jUDDI
  Issue Type: Improvement
Reporter: Alex O'Ree
Assignee: Alex O'Ree






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

Re: [VOTE] jUDDI v3.3.7

[Alex O'Ree]

well i guess we'll cancel the vote until Kurt can figure out what the issue
is.

On Wed, Dec 18, 2019 at 3:06 PM Kurt Stam  wrote:

> Java 8. I don’t see errors in the logs.
>
> On Dec 18, 2019, at 14:35, Alex O'Ree  wrote:
>
> 
> correction java 10
>
> On Wed, Dec 18, 2019 at 2:16 PM Alex O'Ree  wrote:
>
>> Kurt, it started up here ok, what version of java?
>>
>> On Wed, Dec 18, 2019 at 1:19 PM Kurt Stam  wrote:
>>
>>> In the tomcat bundle the server backend /juddiv3 does not seem to start
>>>
>>> On Dec 18, 2019, at 07:37, Kurt Stam  wrote:
>>>
>>> 
>>> Will check it out today!
>>>
>>> On Dec 18, 2019, at 07:29, Alex O'Ree  wrote:
>>>
>>> 
>>> Pingno responses in 4 days.
>>>
>>> Also when further researching [JUDDI-999], it looks like we are not
>>> performing length checks on tmodel instance information tags. I don't think
>>> it's a major issue and it can wait until the next one.
>>>
>>>
>>> On Sat, Dec 14, 2019 at 9:56 PM Alex O'Ree  wrote:
>>>
 Dear jUDDI enthusiasts,

 The new release is here! This release resolves 6 JIRAs, 4 bugs, 1 build
 related issue, and one maintenance issue.

 The release distribution is temporarily available here (without hashes)

 https://www.dropbox.com/sh/28qfjhx0h38h3dg/AADVdOIkStgu88y2ggXU-_F5a?dl=0

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

 and we have a tag at:

 https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=refs/tags/juddi-3.3.7

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

 +1 for me

 Bug

- [JUDDI-991 ] -
JUDDI Uses EOL Version of Apache CXF
- [JUDDI-996 ] -
Admin gui, get all client subscriptions throws a classcast error
- [JUDDI-997 ] -
Admin gui has strange behavior and no feedback if the login fails
- [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)

 Improvement

- [JUDDI-995 ] - Add
automated generation of sha512 hashes during the build
- [JUDDI-1000 ] -
Update embedded tomcat to the latest version available