Re: Support - JUDDIv3 issue on statrup of Tomcat
Ok I played around with it a bit and I was able to get it up and running.
In the persistence.xml file, use the Oracle10gDialect dialect.
Add in the oracle ojdbc8 v19.7.0.0 to tomcat's lib folder (other versions
will probably work)
In the oracle database, you'll have to figure out how to create the user
and what not, but I did have to run the juddi ddl specific to oracle db
manually. Normally the JPA stuff will run it automatically but it didn't
seem to trigger in this case. I used the file named 'oracle12c.ddl' in the
docs/ddl folder.
In context.xml
I'm not super familiar with oracle db, securing it, or how to explicitly
get to a database via the jdbc url, but it looks like it's a server side
setting to get it to work. So you're on your own with that.
Finally, there was a minor code change to fix the long string issue. New
drop box link below. Hopefully this will get you going
https://www.dropbox.com/s/j8ra6q9e9lxulh8/juddi-tomcat-3.3.9-SNAPSHOT.zip?dl=0
On Thu, Jul 16, 2020 at 1:47 AM Rakesh Shelar
wrote:
> Alex,
>
> we have set up (oracle as DB) as follows (as you recommended)
> jdbc driver to either the container's lib folder or in
> juddiv3/WEB-INF/lib
> [image: image.png]
>
> in webapps/juddiv3/WEB-INF/classes/META-INF/persistence.xml
>
> [image: image.png]
>
> webapps/juddiv3/META-INF/context.xml
>
> [image: image.png]
>
> There are more fields we need to fix. Can you fix for all the fields and
> related stuff for 4096 lengths. I can see a few of the fields name as
> constants are specific to <>4096. *This is ORACLE related
> issue Oracle varchar2 does not support 4.96 as length. can you test with
> Oracle and not a SQL server?*
>
> we get the following error too (another field now)
>
> {stmnt 1192364865 CREATE TABLE *j3_discovery_url* (id NUMBER NOT NULL, url
> VARCHAR2(4096) NOT NULL, use_type VARCHAR2(255) NOT NULL, entity_key
> VARCHAR2(255) NOT NULL, PRIMARY KEY (id))} [code=910, state=42000]
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:389)
> at
> org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:134)
> at
> org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:691)
> at
> org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:196)
>
> Regards,
>
> Rakesh
>
>
> On Thu, 16 Jul 2020 at 09:39, Rakesh Shelar
> wrote:
>
>> Thanks. Alex
>>
>> But we are using Oracle and not a SQL server. any advice? because in the
>> oracle it says 4096 max string length not supported by Oracle.
>>
>>
>> -Regards,
>> Rakesh
>>
>> On Thu, 16 Jul 2020 at 07:28, Alex O'Ree wrote:
>>
>>>
>>> OK i was able to get it to fire up using hibernate with mssql 2019 but
>>> it'll probably work with older versions
>>>
>>> So add the microsoft jdbc driver to either the container's lib folder or
>>> in juddiv3/WEB-INF/lib
>>>
>>> in webapps/juddiv3/WEB-INF/classes/META-INF/persistence.xml
>>> make sure hibernate.dialect is set to SQLServer2008Dialect , example:
>>> >> value="org.hibernate.dialect.SQLServer2008Dialect"/>
>>>
>>> in webapps/juddiv3/META-INF/context.xml
>>> replace what ever is there for the Juddi Datasource with something
>>> similar to this. Obviously, update it to meet your environment
>>>
>>> >> type="javax.sql.DataSource" username="juddi"
>>> password="yourpasswordhere"
>>>
>>> driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver"
>>> url="jdbc:sqlserver://localhost:1433;databaseName=juddi"
>>> maxActive="8"
>>> />
>>>
>>> And for simplicity, i've updated the drop box download link to have a
>>> newer build that is set to hibernate (several of the jar's are different
>>> from the previous download link). I also added a simple tomcat build,
>>> following the instructions above, it should be possible to get it up and
>>> running with mssql.
>>>
>>> https://www.dropbox.com/sh/k2ojoye8y2916bf/AACRJoqqI5X4zlTKBlhASjCma?dl=0
>>>
>>> On Wed, Jul 15, 2020 at 6:42 PM Alex O'Ree wrote:
>>>
Yes, as i stated earlier, not all of the reported issues have been
resolved. This includes the mssql configuration.
On Wed, Jul 15, 2020 at 10:29 AM Rakesh Shelar <
rakesh.she...@northgateps.com> wrote:
> Alex,
>
> we have tested JUDDI (test) version provided by you. And we are still
> getting the following error
>
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'inquiry': Cannot create inner bean '(inner bean)#46d9c49'
> of type [org.apache.juddi.api.impl.UDDIInquiryImpl] while setting
> constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean
[jira] [Commented] (JUDDI-1015) Oracle database start up issue due to max string length
[
https://issues.apache.org/jira/browse/JUDDI-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159606#comment-17159606
]
ASF subversion and git services commented on JUDDI-1015:
Commit 93f2d3693cff16e52129171368d36b2580fc in juddi's branch
refs/heads/bug/JUDDI-1015 from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=93f2d36 ]
Merge branch 'master' into bug/JUDDI-1015
> Oracle database start up issue due to max string length
> ---
>
> Key: JUDDI-1015
> URL: https://issues.apache.org/jira/browse/JUDDI-1015
> Project: jUDDI
> Issue Type: Bug
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.8
>
>
> from the juddi mailing list
>
> {color:#172b4d}Oracle Version of Juddi Due to string limit for a column
> CREATE TABLE j3_binding_template (entity_key VARCHAR2(255) NOT NULL,
> access_point_type VARCHAR2(255), access_point_url VARCHAR2(4096),
> hosting_redirector VARCHAR2(255), service_key VARCHAR2(255) NOT NULL, PRIMARY
> KEY (entity_key)) {color}*Oracle max varchar limit: 4000*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-1015) Oracle database start up issue due to max string length
[
https://issues.apache.org/jira/browse/JUDDI-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159605#comment-17159605
]
ASF subversion and git services commented on JUDDI-1015:
Commit c6e69a48bfe61dde00a8ff8873bb8f946e06e4ea in juddi's branch
refs/heads/bug/JUDDI-1015 from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=c6e69a4 ]
JUDDI-1015 adds oracle and mssql drivers to the mix along with an example for
oracle db
> Oracle database start up issue due to max string length
> ---
>
> Key: JUDDI-1015
> URL: https://issues.apache.org/jira/browse/JUDDI-1015
> Project: jUDDI
> Issue Type: Bug
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.8
>
>
> from the juddi mailing list
>
> {color:#172b4d}Oracle Version of Juddi Due to string limit for a column
> CREATE TABLE j3_binding_template (entity_key VARCHAR2(255) NOT NULL,
> access_point_type VARCHAR2(255), access_point_url VARCHAR2(4096),
> hosting_redirector VARCHAR2(255), service_key VARCHAR2(255) NOT NULL, PRIMARY
> KEY (entity_key)) {color}*Oracle max varchar limit: 4000*
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (JUDDI-1008) find_business returns an error when querying a tModel when using the v2 Inquire API
[ https://issues.apache.org/jira/browse/JUDDI-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159604#comment-17159604 ] ASF subversion and git services commented on JUDDI-1008: Commit f9ca9042de955fd61e3c8edf65b6616526ca1a43 in juddi's branch refs/heads/bug/JUDDI-1015 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=f9ca904 ] JUDDI-1008 fix for find by ident bag via v2 findbusiness api > find_business returns an error when querying a tModel when using the v2 > Inquire API > --- > > Key: JUDDI-1008 > URL: https://issues.apache.org/jira/browse/JUDDI-1008 > Project: jUDDI > Issue Type: Bug > Components: core >Affects Versions: 3.3.7 >Reporter: Steve Luisser >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.8 > > > The v2 Inquire API find_business returns an error when querying for a tModel. > The v3 call gives a valid response. > V2 Request > > http://schemas.xmlsoap.org/soap/envelope/; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xmlns:xsd="http://www.w3.org/2001/XMLSchema;> > > > > keyName="DUNS" keyValue="12-345-6781" /> > > > > > > V2 Response > http://schemas.xmlsoap.org/soap/envelope/;> > > > soap:Server > At least one search criterion must be supplied. Try using > '%' as a wild card with the a 'approximateMatch' find qualifer for > everything > > operator="uddi:juddi.apache.org:node1" truncated="false"> > > A serious technical error has > occurred while processing the request. > > > > > > > > V3 Request > > http://schemas.xmlsoap.org/soap/envelope/; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; > xmlns:xsd="http://www.w3.org/2001/XMLSchema;> > > > > keyName="DUNS" keyValue="12-345-6781" /> > > > > > > V3 Response > http://schemas.xmlsoap.org/soap/envelope/;> > > xmlns:ns10="urn:uddi-org:vs_v3" xmlns:ns9="urn:uddi-org:repl_v3" > xmlns:ns8="urn:uddi-org:policy_v3" xmlns:ns7="urn:uddi-org:custody_v3" > xmlns:ns6="urn:uddi-org:subr_v3" xmlns:ns5="urn:uddi-org:sub_v3" > xmlns:ns4="urn:uddi-org:vscache_v3" > xmlns:ns3="http://www.w3.org/2000/09/xmldsig#; > xmlns:ns2="urn:uddi-org:api_v3" truncated="false"> > > 1 > 1 > 1 > > > businessKey="uddi:juddi.apache.org:0a528283-47f9-4bf8-b29c-1c1e0338fe28"> > Test Provider > > serviceKey="uddi:juddi.apache.org:249f327a-68bd-4cd7-b358-c0347369e573" > businessKey="uddi:juddi.apache.org:0a528283-47f9-4bf8-b29c-1c1e0338fe28"> > Test Service > > > > > > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (JUDDI-1012) MS SQL Server Sequence table change
[ https://issues.apache.org/jira/browse/JUDDI-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17159603#comment-17159603 ] ASF subversion and git services commented on JUDDI-1012: Commit bad3192dddc3f4b168e6923da9f051616554c2ed in juddi's branch refs/heads/bug/JUDDI-1015 from Alex O'Ree [ https://gitbox.apache.org/repos/asf?p=juddi.git;h=bad3192 ] JUDDI-1012 newer version of hibernate (jre8 min), also adds some additional DDLs for mssql and oracle > MS SQL Server Sequence table change > --- > > Key: JUDDI-1012 > URL: https://issues.apache.org/jira/browse/JUDDI-1012 > Project: jUDDI > Issue Type: Improvement > Components: core >Affects Versions: 3.3.7 >Reporter: Steve Luisser >Assignee: Alex O'Ree >Priority: Major > Fix For: 3.3.8 > > > SQL Server 2012 is the oldest version that is supported by Microsoft. This > and newer versions support sequences. > > File mssql2000.ddl: > > create table hibernate_sequence (next_val numeric(19,0)); > Multiple instances of insert into hibernate_sequence values ( 1 ); > > Suggestion to change this to: > create sequence hibernate_sequence start with 1 increment by 1; > > To remove the sequence use: DROP sequence hibernate_sequence; -- This message was sent by Atlassian Jira (v8.3.4#803005)
