11.03.2013 21:51, Daniel Kulp kirjoitti: > Can you "kill -3" the process to get the stack trace? > > My gut feeling is that there is an import in > "file:/home/liferay/wsdl/partner.wsdl" someplace that it's trying to go off > to the internet to grab. > > Dan
Only http besides teh actual service address is
<!-- Soap Binding -->
<binding name="SoapBinding" type="tns:Soap">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="login">
<soap:operation soapAction=""/>
<input>
<soap:header use="literal" message="tns:Header"
part="LoginScopeHeader"/>
<soap:header use="literal" message="tns:Header"
part="CallOptions"/>
<soap:body parts="parameters" use="literal"/>
</input>
All imports are like this.
<import namespace="urn:partner.soap.sforce.com"/>
I have not yet tried the kill -3 ...
>
>
> On Mar 10, 2013, at 9:30 PM, Jari Fredriksson <[email protected]> wrote:
>
>> 2013-03-11 03:22:10,517 INFO
>> [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (main)
>> Creating Service {urn:partner.soap.sforce.com}SforceService from WSDL:
>> file:/home/liferay/wsdl/partner.wsdl
>>
>> I have tried to create a service client using CXF 2.7.3 on a Liferay
>> 6.0.6 on top of JBoss 5.1.0
>>
>> First I tried the code the WSDL2Java created for client.
>> ReflectionServiceFactoryBean hung up, and the server was dead. It sis
>> not serve anything to browsers, but no error messages were in logs and
>> anywhere.
>>
>> Then I tied Spring beans:
>>
>> -----------------------------------------<WEB-INF/beans.xml>-------------------------------------
>>
>> <beans xmlns="http://www.springframework.org/schema/beans";
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>> xmlns:jaxws="http://cxf.apache.org/jaxws";
>> xmlns:jaxrs="http://cxf.apache.org/jaxrs";
>> xmlns:sforce="urn:partner.soap.sforce.com"
>> xsi:schemaLocation="
>> http://www.springframework.org/schema/beans
>> http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
>> http://cxf.apache.org/jaxws
>> http://cxf.apache.org/schemas/jaxws.xsd";>
>>
>> <import resource="classpath:META-INF/cxf/cxf.xml"/>
>> <import resource="classpath:META-INF/cxf/cxf-servlet.xml"/>
>>
>> <bean id="SalesforcePartnerTask"
>> class="fi.dise.provisioning.SalesforcePartnerTask" />
>>
>> <bean id="sForcePort"
>> class="org.springframework.remoting.jaxws.JaxWsPortProxyFactoryBean">
>> <property name="serviceInterface"
>> value="com.sforce.soap.partner.Soap" />
>> <property name="wsdlDocumentUrl"
>> value="file:///opt/dise/salesforce/partner.wsdl" />
>> <property name="namespaceUri" value="urn:partner.soap.sforce.com" />
>> <property name="serviceName" value="SforceService" />
>> <property name="endpointAddress" value="https://mangled"; />
>> </bean>
>> </beans>
>>
>> Same result. Seems that the factory gets called in similar manner either
>> way, and it always hangs.
>>
>> Any ideas?
>>
>> --
>>
>> Your depth of comprehension may tend to make you lax in worldly ways.
>>
>>
--
"It seems to be not only in Vista creative is "a bit" problematic"
Husse Jul 10 2007
signature.asc
Description: OpenPGP digital signature
