While i was able to resolve this specific issue (I think, waiting to hear back from the folks running oracle db with a similar issue), i have not yet been able to resolve the side effect of this. I think it was the ability to query by discovery url that is now broken (failing unit tests). I'm not a hibernate/jpa expert but I am researching the issue. As soon as it is resolved, we'll start the release process.
I'm pretty much the only person maintaining jUDDI these days. It's definitely not my full time job, so any help is appreciated. On Wed, Aug 12, 2020 at 11:55 AM Stephen A. Luisser <sluis...@essent.com> wrote: > I am checking on issue JUDDI-1011 - MS SQL Server table - length of field > too large. If related issue JUDDI-999 is closed this one should be closed. > > > > Is there an estimate on when 3.3.9 may be released? > *Confidentiality Notice* > > The contents of this email message, including any attached > files, are confidential and intended solely for the use of the individual > or entity to whom they are addressed. This communication may contain > information that is barred from disclosure under applicable law and/or > contain material protected by the attorney-client privilege. Nothing in > this e-mail message should be construed as a legal opinion. If you are not > the intended recipient or the person responsible for delivering the e-mail > to the intended recipient, be advised that you have received this e-mail in > error and that any use, dissemination, forwarding, printing or copying of > this e-mail is strictly prohibited. If you have received this communication > in error, please notify me immediately by reply e-mail and delete all > copies of the original message. > > >
