Okay, I wasn't using the WSTransport, that was the problem. I am
however trying to use the Systinet registry, I saw that there was a
thread from Jan 2010 about this, because I am now getting:
org.apache.juddi.v3.client.transport.TransportException:
{urn:uddi-org:v3_service}UDDI_Security_Port is not a valid service.
Valid services are: {urn:uddi-org:api_v3}UDDI_Security_SoapService
at
org.apache.juddi.v3.client.transport.JAXWSTransport.getUDDISecurityService(JAXWSTransport.java:104)
at
org.apache.juddi.v3.client.transport.Transport.getUDDISecurityService(Transport.java:43)
at juddi.securityapi.HelloWorld.<init>(HelloWorld.java:43)
Was that issue ever resolved? Do I just rebuild the
JAXWSTransport.java with the changed names?
Thanks again, I really really appreciate your amazing support!
Franklin
On Thu, Jun 17, 2010 at 9:57 AM, Kurt T Stam <kurt.s...@gmail.com> wrote:
> Hi Franklin,
>
> You should only need the uddiws.jar and the juddi-client.jar and the
> uddi.xml for the client configuration.
> You should not need the juddi-core.jar (this contains the registry itself),
> which is trying to startup I can see
> from your stacktrace. Anyway make sure to use WSTransport to connect to the
> remote UDDI registry.
> It'll be great to hear your progress. Which registry are you trying to
> connect to?
>
> Cheers,
>
> --Kurt
>
> Franklin Dorbon wrote:
>>
>> I am trying to use the Juddi client to connect to a "non-JUDDI"
>> registry. I thought all I needed to do was to include the juddi-core
>> and juddi-client jars and put the uddi.xml file in a path where my
>> standalone application can access it. But for some reason I get the
>> error (below) while performing the AUTH test. Do I need to add some
>> configuration file to my Java programs path or make some "set
>> properties" calls in my code? I thought the client included the
>> persistence.xml file and therefore ConnectionDriverName would be set?
>>
>> Thanks a million,
>> Franklin
>>
>> 2010-06-17 09:08:57,572 [INFO] org.apache.juddi.Registry - Starting
>> jUDDI registry...
>> 2010-06-17 09:08:58,041 [INFO] org.apache.juddi.config.AppConfig -
>> Reading from properties file: null
>> 203 WARN [main] openjpa.Runtime - The configuration property named
>> "openjpa.Id" was not recognized and will be ignored, although the name
>> closely matches a valid property called "openjpa.Id".
>> 1640 INFO [main] openjpa.Runtime - Starting OpenJPA 2.0.0
>> Exception in thread "main" <openjpa-2.0.0-r422266:935683 fatal user
>> error> org.apache.openjpa.persistence.ArgumentException: A JDBC Driver
>> or DataSource class name must be specified in the ConnectionDriverName
>> property.
>> at
>> org.apache.openjpa.jdbc.schema.DataSourceFactory.newDataSource(DataSourceFactory.java:76)
>> at
>> org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.createConnectionFactory(JDBCConfigurationImpl.java:836)
>> at
>> org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getDBDictionaryInstance(JDBCConfigurationImpl.java:594)
>> at
>> org.apache.openjpa.jdbc.meta.MappingRepository.endConfiguration(MappingRepository.java:1489)
>> at
>> org.apache.openjpa.lib.conf.Configurations.configureInstance(Configurations.java:507)
>> at
>> org.apache.openjpa.lib.conf.Configurations.configureInstance(Configurations.java:432)
>>
>
>
