[Users] UNRESOLVED_INTERFACE with quickstart-3.0, working with 2.2

[kleag]

Hello,

I'm trying to use petals-quickstart-3.0 to see if the ploblem reported in my previous post is solved in the new version, but my services that were working with version 2.2 do not work anymore.

Their deployment fail with:

Code:

[Petals.JBI-Management.DeploymentServiceImpl]-INFO 2009-03-10 01:29:04,943 Service Assembly 'crawlconfigureProvideSA' succesfully started
[Petals.JBI-Messaging.EndpointRegistryImpl]-WARNING 2009-03-10 01:29:07,417 No interface found in the WSDL description of the endpoint {http://weblab-project.org/services/configurable}ConfigurableService-crawlconfigure
[Petals.JBI-Messaging.EndpointRegistryImpl]-WARNING 2009-03-10 01:29:07,417 Set a default interface name for the endpoint {http://weblab-project.org/services/configurable}ConfigurableService-crawlconfigure : {http://weblab-project.org/services/configurable}UNRESOLVED_INTERFACEConfigurableService




The jbi is:

Code:

<?xml version="1.0" encoding="UTF-8"?>
<jbi:jbi version="1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:jbi="http://java.sun.com/xml/ns/jbi"
xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-4.0"
xmlns:soap="http://petals.ow2.org/components/soap/version-3.1"
xmlns:configure="http://weblab-project.org/services/configurable">
<!-- Import a Service into PEtALS or Expose a PEtALS Service => use a BC. -->
<jbi:services binding-component="false">
<!-- Import a Service into PEtALS => provides a Service. -->
<jbi:provides
    interface-name="configure:Configurable"
    service-name="configure:ConfigurableService"
    endpoint-name="crawlconfigure">
<!-- CDK specific fields -->
<petalsCDK:wsdl>interfaces/Configurable.wsdl</petalsCDK:wsdl>
<!-- SOAP specific fields -->
<soap:address>http://localhost:10113</soap:address>
<!--soap:address>https://cea-list-services.webcontent.fr/crawling-configure</soap:address-->
<soap:chunked-mode>false</soap:chunked-mode>
<soap:synchronous-timeout>0</soap:synchronous-timeout>
<soap:ssl-trustStore>/usr/lib/jvm/java-1.6.0-sun-1.6.0.10/jre/lib/security/jssecacerts</soap:ssl-trustStore>
<soap:ssl-trustStoreType>JKS</soap:ssl-trustStoreType>
<soap:ssl-trustStorePassword></soap:ssl-trustStorePassword>
<soap:ssl-keyStore>XXX</soap:ssl-keyStore>
<soap:ssl-keyStoreType>pkcs12</soap:ssl-keyStoreType>
<soap:ssl-keyStorePassword>XXX</soap:ssl-keyStorePassword>
<soap:mode>SOAP</soap:mode>
</jbi:provides>
</jbi:services>
</jbi:jbi>




The wsdl is;

Code:

<?xml version="1.0" encoding="UTF-8"?>
<!-- Created by EADS DS - IPCC -->
<definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
	xmlns:tns="http://weblab-project.org/services/configurable"
	xmlns:types="http://weblab-project.org/services/configurable/types"
	xmlns:error="http://weblab-project.org/services/exception"
	xmlns:xsd="http://www.w3.org/2001/XMLSchema"
	xmlns="http://schemas.xmlsoap.org/wsdl/"
	targetNamespace="http://weblab-project.org/services/configurable"
	name="Configurable">

	<types>
		<xsd:schema>
			<xsd:import
				namespace="http://weblab-project.org/services/configurable/types"
				schemaLocation="ConfigurableTypes.xsd" />
			<xsd:import
				namespace="http://weblab-project.org/services/exception"
				schemaLocation="exception.xsd" />
		</xsd:schema>
	</types>

	<!-- Configure -->
	<message name="configureRequest">
		<part name="args" element="types:configureArgs" />
	</message>
	<message name="configureResponse">
		<part name="return" element="types:configureReturn" />
	</message>
	<message name="configureException">
		<part name="error" element="error:webLabException" />
	</message>

	<!-- ResetConfiguration -->
	<message name="resetConfigurationRequest">
		<part name="args" element="types:resetConfigurationArgs" />
	</message>
	<message name="resetConfigurationResponse">
		<part name="return" element="types:resetConfigurationReturn" />
	</message>
	<message name="resetConfigurationException">
		<part name="error" element="error:webLabException" />
	</message>


	<portType name="Configurable">
		<documentation>
			The configurable interface will be used to define services
			of which behavior depends on a usage context, this context
			corresponding to a particular set of parameters.

			In some services, the configurable interface is optional and
			won't be inevitably realised in every implementations.
		</documentation>
		<operation name="configure">
			<documentation>Configure the service.</documentation>
			<input name="configureInput" message="tns:configureRequest" />
			<output name="configureOutput"
				message="tns:configureResponse" />
			<fault name="configureException"
				message="tns:configureException">
				<documentation>
					To be thrown if an error occurs in configure method.
				</documentation>
			</fault>
		</operation>

		<operation name="resetConfiguration">
			<documentation>
				Reset the configuration of the service to the default
				one.
			</documentation>
			<input name="resetConfigurationInput"
				message="tns:resetConfigurationRequest" />
			<output name="resetConfigurationOutput"
				message="tns:resetConfigurationResponse" />
			<fault name="resetConfigurationException"
				message="tns:resetConfigurationException">
				<documentation>
					To be thrown if an error occurs in
					resetConfiguration method.
				</documentation>
			</fault>
		</operation>
	</portType>

	<binding name="ConfigurableSOAPBinding" type="tns:Configurable">
		<soap:binding transport="http://schemas.xmlsoap.org/soap/http"
			style="document" />
		<operation name="configure">
			<soap:operation soapAction="configure" />
			<input name="configureInput">
				<soap:body use="literal" />
			</input>
			<output name="configureOutput">
				<soap:body use="literal" />
			</output>
			<fault name="configureException">
				<soap:fault name="configureException" use="literal" />
			</fault>
		</operation>

		<operation name="resetConfiguration">
			<soap:operation soapAction="configure" />
			<input name="resetConfigurationInput">
				<soap:body use="literal" />
			</input>
			<output name="resetConfigurationOutput">
				<soap:body use="literal" />
			</output>
			<fault name="resetConfigurationException">
				<soap:fault name="resetConfigurationException"
					use="literal" />
			</fault>
		</operation>
	</binding>

  <service name="ConfigurableService">
    <port name="ConfigurablePort"
      binding="configurable:ConfigurableSOAPBinding">
      <soap:address location="" />
    </port>
  </service>

</definitions>




I suppose that this should still work, shouldn't it ?

Regards,

Gaël




-------------------- m2f --------------------

Read this forum topic online here:
http://petals.ebmwebsourcing.com/forum/viewtopic.php?p=528#528

-------------------- m2f --------------------


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://forum-list.petalslink.org/pipermail/users/attachments/20110316/acb94813/attachment.htm>