-
1. Re: Resource Path Location Type Unresolvable Service Interface: The specified interface does not exist on the project classpath.
jorgemoralespou_2 Apr 27, 2015 6:48 AM (in response to nello360)Hi Nello,
There is a bug with the JBDS IDE that reports this: https://issues.jboss.org/browse/SWITCHYARD-2363
Also, AFAIK, there has been some updates to the IDE for 2.0 that allows you to create the transformers anyway: https://issues.jboss.org/browse/SWITCHYARD-2365
You can safely use the JBDS/tooling for SY 2.0 if you are using SY 1.1, so I recommend you to update to the latest JBDS 8 and the latest integration stack tooling for SwitchYard.
Cheers,
-
2. Re: Resource Path Location Type Unresolvable Service Interface: The specified interface does not exist on the project classpath.
nello360 Apr 27, 2015 7:21 AM (in response to jorgemoralespou_2)I updated my JBDS, but the problem persists...
I noticed a thing: the java interface that implements the services of my wsdl has methods that have 5 inputs as you can see:
public interface AnomalyFrequentItem {
public java.lang.String getAnomaly(
java.lang.String id,
java.lang.String data,
java.lang.String stato,
java.lang.String wpInteressato,
java.lang.String body);
public java.lang.String getFrequentItemSet(
java.lang.String id,
java.lang.String data,
java.lang.String stato,
java.lang.String wpInteressato,
java.lang.String body);
}
But If I change the methods and I put only one input the problem disappears...
public interface AnomalyFrequentItem {
public java.lang.String getAnomaly(
java.lang.String id,
);
public java.lang.String getFrequentItemSet(
java.lang.String id,
);
}
It is possible that the service can have only one input???
If it is true, how can I solve this problem if I want to consume a service that has method withs more inputs???
Thank's.
-
3. Re: Resource Path Location Type Unresolvable Service Interface: The specified interface does not exist on the project classpath.
jorgemoralespou_2 Apr 27, 2015 8:53 AM (in response to nello360)Nello,
Then that's the problem. SwitchYard currently supports interfaces with one single method, and you'll have to wrap your message into a wrapper object and use transformers to adapt your message contents on each side of the wires.
I've looked at your wsdl, and you have wrapped objects. You should try to recreate the Java interface from the wsdl, and use the wrapper object instead:
So have method "public String getAnomaly(GetFrequentItemSet parameters)", this way you'll be able to have automatic transformer, let's say, using JAXB.
I recommend you looking at the quickstarts, as there are many samples for this type of web services based applications.
Hope it helps.
Also look at:
http://unpoucode.blogspot.se/2014/10/switchyard-contracts.html
Un "POU"co De ...: ...regarding unwrapped in SwitchYard SOAP bindings