juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt T Stam (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] [Comment Edited] (JUDDI-546) After deployed juddiv3-war-3.1.3 on WebSphere 7 default AXIS Transport URL's are not working
Date Mon, 13 May 2013 15:59:16 GMT

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

Kurt T Stam edited comment on JUDDI-546 at 5/13/13 3:57 PM:
------------------------------------------------------------

Hi Alex,

Can you send me a working war (again). The one you sent me gives me:

11:29:16,114 ERROR [JUDDI_010_PublisherIntegrationTest] javax.xml.bind.JAXBException: org.apache.juddi.api_v3.SavePublisher
is not known to this context
javax.xml.ws.soap.SOAPFaultException: javax.xml.bind.JAXBException: org.apache.juddi.api_v3.SavePublisher
is not known to this context
	at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:188)
	at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:122)

which is exactly the same error I get with the maven build war.

Both wars seem have the same unittest failures:

Failed tests: 
  testJoePublisher(org.apache.juddi.v3.tck.JUDDI_010_PublisherIntegrationTest)
  testSamSyndicator(org.apache.juddi.v3.tck.JUDDI_010_PublisherIntegrationTest)
  testGetAllPublishers(org.apache.juddi.v3.tck.JUDDI_010_PublisherIntegrationTest)
  findEntities(org.apache.juddi.v3.tck.UDDI_070_FindEntityIntegrationTest)
  findSignedEntities(org.apache.juddi.v3.tck.UDDI_070_FindEntityIntegrationTest)
  joePublisherUpdateService_SMTP(org.apache.juddi.v3.tck.UDDI_090_SubscriptionListenerIntegrationTest)


Thx,

--Kurt
                
      was (Author: kurtstam):
    Hi Alex,

Can you send me a working war (again). The one you sent me gives me:

11:29:16,114 ERROR [JUDDI_010_PublisherIntegrationTest] javax.xml.bind.JAXBException: org.apache.juddi.api_v3.SavePublisher
is not known to this context
javax.xml.ws.soap.SOAPFaultException: javax.xml.bind.JAXBException: org.apache.juddi.api_v3.SavePublisher
is not known to this context
	at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:188)
	at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:122)

which is exactly the same error I get with the maven build war.

Thx,

--Kurt
                  
> After deployed juddiv3-war-3.1.3 on WebSphere 7 default AXIS Transport URL's are not
working
> --------------------------------------------------------------------------------------------
>
>                 Key: JUDDI-546
>                 URL: https://issues.apache.org/jira/browse/JUDDI-546
>             Project: jUDDI
>          Issue Type: Bug
>          Components: uddi-tck
>    Affects Versions: 3.1.3
>            Reporter: Lokesh Nagappa
>            Assignee: Kurt T Stam
>            Priority: Critical
>             Fix For: 3.1.5
>
>         Attachments: web.xml
>
>
>  juddiv3-war-3.1.3 on gets deployed on  WebSphere 7 without any problem, but the axis
Transport URL's are not working.
> javax.xml.registry.queryManagerURL=http://<<IPADDRESS>>:<<PORT>>/BFJUDDI/services/inquiry
> javax.xml.registry.lifeCycleManagerURL=http://<<IPADDRESS>>:<<PORT>>/BFJUDDI/services/publish
> javax.xml.registry.securityManagerURL=http://<<IPADDRESS>>:<<PORT>>/BFJUDDI/services/security

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message