Java: Not a Valid Service Error

Hi -

I am in the process of creating a Fax Service using Java. I seemed to had the services nailed - till I tried it today (after a week), and I started getting this error:

javax.xml.ws.WebServiceException: {http://premconn.premiereconnect.com/PremiereConnect/2008/10}XOA is not a valid service. Valid services are: {http://wsmsg.easylink.com/WSMSG/2011/01}XOA

So, I converted over this entirely to use sync api from this page:

https://apiforums.easylink.com/emapidocs/wsdl/index.html

Compiled fine. When I try to run, now I get this exception,

javax.xml.ws.WebServiceException: {http://ws.easylink.com/Authenticate/2011/01}AuthenticateService is not a valid service. Valid services are: {http://wsmsg.easylink.com/WSMSG/2011/01}XOA

Thanks and appreciate any insights - Suvendra

Find more posts tagged with

Comments

skamens

I presume you're using the production URL (https://messaging.easylink.com/soap/sync)?

I believe what happened is that over this past weekend we switched that URL from an instance of our 2.4 API to an instance of our 2.5 API. This was announced here on the forum site (see https://apiforums.easylink.com/announcements/414).

You should certainly be able to use the WSDL from the page you indicated to connect to the API, and the Authenticate service does exist, so I'm not 100% sure why you're now getting the error.

Can you let us know the URL you are using for submission? Also, if you have a way to capture and send the XML that you are submitting that would be very helpful.

suvendra

Thanks for your response. I got this error for both production and test URLs on that day. I won't be working on this for some days now - will get back when I start working on this. Good thing I could use this time to convert over the code to use the new API. Now to just make sure it works. Thanks.

suvendra

Hi -

Sorry to revive this old post, I was not able to work on this for a few days. Tried it today, I am still getting the same error.

javax.xml.ws.WebServiceException: {http://ws.easylink.com/Authenticate/2011/01}AuthenticateService is not a valid service. Valid services are: {http://wsmsg.easylink.com/WSMSG/2011/01}XOA

I am using JAX-WS to connect and connecting to https://test2messaging.easylink.com/soap/sync/ for testing now.

This is the WSDL location I downloaded it from.

https://apiforums.easylink.com/emapidocs/EMAPI2.5/wsdl/Authenticate201101.wsdl

Thanks for your help.

suvendra

Also, if it helps, it is failing as early as getting the Service Port,

AuthenticateService  auth = new AuthenticateService(new URL(_url), new QName("http://ws.easylink.com/Authenticate/2011/01", "AuthenticateService"));
AuthenticatePortType port = auth.getAuthenticatePort();

Thanks.

skamens

The WSDL deliberately contains an invalid destination for the web service - here's how it reads:

<soap:address location="http://endpoint.easylink.com"/>

</port>

</service>

http://endpoint.easylink.com does not exist.

So you can't use getAuthenticatePort() to determine the destination for the request.

The other concern I see in your earlier post is this:

{http://ws.easylink.com/Authenticate/2011/01}AuthenticateService is not a valid service. Valid services are: {http://wsmsg.easylink.com/WSMSG/2011/01}XOA

This tells me that somewhere you're using the older WSDL that still refers to a monolithic XOA object while trying to access the more current Authenticate schema.

Not knowing your programming environment, I can't say what exactly is going on, but for something as simple as Authenticate I might suggest starting over with a brand new program instead of trying to modify your existing one.

suvendra

Hi -

Thanks for your response. I am using the correct WSDL and generating Java code using JaxWS wsimport utility. So every build creates a fresh stub. I did check that Soap Action was also correctly set to XOAAuthenticate. And I am setting the Endpoint correctly by getting the Binding provider back and changing the Endpoint Address.

Since all the other services use Authenticate anyway, I wanted to make that work - so I know I have a good API call. It is definitely not Easylink API - as I can call it using SOAP-UI. So, it must be something in the code or Weblogic Server. Still working on figuring it out. Not sure, that error may be pretty generic.

Thanks, Suvendra

suvendra

This is resolved. I could successfully validate my connection and send a fax. There were couple of issue - starting with how Maven plugin creates Jax-WS artifacts - and also same type names defined under different namespaces - sharing the same XSD layout. Somehow, Java didn't create good artifacts.