Hi Philippe, You have two options. 1) setup a datasource in your tomcat called "jdbc/juddiDB". Write a program to verify your datasource is working. Then try your happyjuddi.jsp and every thing should be ok.
2) Use direct connection to the database. Follow the link below on how to do it. http://www.mail-archive.com/[email protected]/msg00658.html Thanks Lakshman -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, 14 October 2005 6:34 PM To: [email protected] Subject: RE: Problem with running uddi4j examples Sure, here it is (I'm running my tomcat server under port 9090) : # jUDDI Registry Properties (used by RegistryServer) # see http://www.juddi.org for more information # The UDDI Operator Name juddi.operatorName = jUDDI.org # The i18n locale default codes juddi.i18n.languageCode = en juddi.i18n.countryCode = US # The UDDI DiscoveryURL Prefix juddi.discoveryURL = http://localhost:9090/juddi/uddiget.jsp? # The UDDI Operator Contact Email Address juddi.operatorEmailAddress = [EMAIL PROTECTED] # The maximum name size and maximum number # of name elements allows in several of the # FindXxxx and SaveXxxx UDDI functions. juddi.maxNameLength=255 juddi.maxNameElementsAllowed=5 juddi.maxBusinessEntitiesPerUser=25 juddi.maxBusinessServicesPerBusiness=20 juddi.maxBindingTemplatesPerService=10 juddi.maxTModelsPerUser=100 juddi.maxRowsLimit=10 # jUDDI Authentication module to use juddi.auth = org.apache.juddi.auth.DefaultAuthenticator # jUDDI DataStore module currently to use juddi.dataStore = org.apache.juddi.datastore.jdbc.JDBCDataStore # jUDDI DataSource to use juddi.dataSource=java:comp/env/jdbc/juddiDB # jUDDI UUIDGen implementation to use juddi.uuidgen = org.apache.juddi.uuidgen.DefaultUUIDGen # jUDDI Cryptor implementation to use juddi.cryptor = org.apache.juddi.cryptor.DefaultCryptor # jUDDI Validator to use juddi.validator=org.apache.juddi.validator.DefaultValidator # jUDDI Proxy Properties (used by RegistryProxy) juddi.proxy.adminURL = http://localhost:9090/juddi/admin juddi.proxy.inquiryURL = http://localhost:9090/juddi/inquiry juddi.proxy.publishURL = http://localhost:9090/juddi/publish juddi.proxy.transportClass = org.apache.juddi.proxy.AxisTransport juddi.proxy.securityProvider = com.sun.net.ssl.internal.ssl.Provider juddi.proxy.protocolHandler = com.sun.net.ssl.internal.www.protocol > -----Message d'origine----- > De : Lakshman Srilakshmanan > [mailto:[EMAIL PROTECTED] > Envoye : vendredi 14 octobre 2005 01:07 > A : [email protected] > Objet : RE: Problem with running uddi4j examples > > > Hi philippe, > > Could you post your juddi.properties file > > Lakshman > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Friday, 14 October 2005 1:22 AM > To: [email protected] > Subject: RE: Problem with running uddi4j examples > > Hi ! > I have the exact same configuration. Unfortunately my juddi happinness > page > is NOT happy. > I have the classical error you can find in every forum > "- DB connection was not aquired. (null) > - SELECT COUNT(*) FROM PUBLISHER failed (null)" > > Can you please let me know which procedure you followed to configure > your > app ? > > Thanks in advance ! > > Philippe > > > -----Message d'origine----- > > De : Desiree Hilbring [mailto:[EMAIL PROTECTED] > > Envoye : jeudi 13 octobre 2005 17:16 > > A : [email protected] > > Objet : Problem with running uddi4j examples > > > > > > Hi everybody, > > > > I am newbie using jUDDI and have already installed: > > > > - tomcat.5.5.9 > > - axis 1.2.1 > > - MySQL > > - jUDDI-0.9rc4 > > > > the axis and jUDDI happyness pages are both happy. > > > > An now I am trying to run the FindBusinessExample from > uddi4j and get > > the following error: > > > > *********** Running FindBusinessExample *********** > > TransportFactory: Using transport > > name:org.uddi4j.transport.ApacheAxisTransport > > log4j:WARN No appenders could be found for logger > > (org.apache.axis.i18n.ProjectR > > esourceBundle). > > log4j:WARN Please initialize the log4j system properly. > > > > Request message: > > <ns1:find_business generic="2.0" maxRows="5" > > xmlns="urn:uddi-org:api_v2" > > xmlns:n > > s1="urn:uddi-org:api_v2"><ns1:findQualifiers><ns1:findQualifie > > r>caseSens > > itiveMat > > ch</ns1:findQualifier></ns1:findQualifiers><ns1:name>S</ns1:na > > me></ns1:f > > ind_busi > > ness> > > > > Response message: > > <soapenv:Fault > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> > > <faultcode > > xmlns:ns1="http://xml.apache.org/axis/";>ns1:Server.generalExceptio > > n</faultcode> > > <faultstring/> > > <faultactor/> > > <detail/> > > </soapenv:Fault> > > > > at org.uddi4j.UDDIElement.<init>(UDDIElement.java:38) > > at > > org.uddi4j.response.BusinessList.<init>(BusinessList.java:84) > > at > > org.uddi4j.client.UDDIProxy.find_business(UDDIProxy.java:475) > > at FindBusinessExample.run(FindBusinessExample.java:80) > > at FindBusinessExample.main(FindBusinessExample.java:44) > > > > The samples.prop looks the following: > > > > # Property file used to set parameters for UDDI4J samples. > > > > # > > -------------------------------------------------------------- > > --------- > > # inquiryURL: The URL for the inquiry API of the target > UDDI registry > > # publishURL: URL for the publish API of the target UDDI registry > > # A list of UDDI URLs is on the UDDI4J website > http://www.uddi4j.org/ > > # > > # A typical entry would be of the form > > # inquiryURL=http://company.com/uddi_node > > # publishURL=https://company.com/uddi_publish_node > > # > > -------------------------------------------------------------- > > --------- > > # IBM UDDI test site > > inquiryURL=http://localhost:8082/juddi/inquiry > > publishURL=http://localhost:8082/juddi/publish > > > > # > > -------------------------------------------------------------- > > --------- > > # Userid to use when running the publish samples. Userid/passwords > > should > > # not generally be stored in clear text > > # > > -------------------------------------------------------------- > > --------- > > userid = juddi > > password = juddi > > > > # > > -------------------------------------------------------------- > > --------- > > # Transport classname. Typically defined on commandline as > > # -Dorg.uddi4j.TransportClassName=xxx. > > # > > -------------------------------------------------------------- > > --------- > > #TransportClassName=org.uddi4j.transport.ApacheSOAPTransport > > TransportClassName=org.uddi4j.transport.ApacheAxisTransport > > # TransportClassName=org.uddi4j.transport.HPSOAPTransport > > > > # > > -------------------------------------------------------------- > > --------- > > # Debug log enabled or not. Typically defined on command line as > > -Dorg.uddi4j.logEnabled=true > > # > > -------------------------------------------------------------- > > --------- > > #logEnabled=false > > logEnabled=true > > > > # > > -------------------------------------------------------------- > > --------- > > # Values used to determine the implementation of JSSE to > use. Provided > > # for convenience, this is typically configured within the jdk > > # in JAVA_HOME\jre\lib\security > > # > > -------------------------------------------------------------- > > --------- > > # Sun JSSE implementation > > handlerPackageName=com.sun.net.ssl.internal.www.protocol > > securityClassName=com.sun.net.ssl.internal.ssl.Provider > > > > # IBM JSSE implementation > > # handlerPackageName=com.ibm.net.ssl.internal.www.protocol > > # securityClassName=com.ibm.jsse.JSSEProvider > > > > # > > -------------------------------------------------------------- > > --------- > > # UDDI names to use within samples. Samples may or maynot use these > > values, > > # Check the source for the sample > > # > > -------------------------------------------------------------- > > --------- > > businessName=Sample Business > > serviceName=Sample Service > > tmodelName=Sample TModel > > sampleEntityName=S > > assertionRelationship=peer-peer > > > > # > > -------------------------------------------------------------- > > --------- > > # Additional values can be added as needed as a convenient > repository > > # for data relevant to the UDDI4J samples > > # > > -------------------------------------------------------------- > > --------- > > > > Any idea? Thanks for your help in advance. > > >
