Panu Haaramo commented on Nov 10, 2012

Re: Using existing Web Services in an Xpage

Has anyone gotten this to work by placing the Axis JARs to NSF? In the discussion thread I linked below there is some discussion that it does not work because of conflicts with the Axis code that comes with Domino.

Panu Haaramo commented on Nov 9, 2012

Re: Using existing Web Services in an Xpage

Should have read the whole article, in the end it tells about limitations starting in 8.5.2.

Panu Haaramo commented on Nov 9, 2012

Re: Using existing Web Services in an Xpage

According to Paul Calhoun this is not working since 8.5.2:

http://www-10.lotus.com/ldd/xpagesforum.nsf/topicThread.xsp?action=openDocument&documentId=8BCB11252D985E5885257AAF0016BC5A

Robert F Harwood commented on Jan 13, 2012

Re: Using existing Web Services in an Xpage

will check formatting

Robert F Harwood commented on Jan 13, 2012

Re: Using existing Web Services in an Xpage

will check formatting

Markus Wuestemann commented on Sep 8, 2011

Re: Using existing Web Services in an Xpage

Hi,

first i tryed

var service = new org.apache.axis.client.Service;

for this I get the following error:

Script interpreter error, line=4, col=48: [ReferenceError] 'org' not found

okay now I looked in the java perspective for the package name

i found "lotus.domino.axis.client.Service". now i tryed to use this:

var service = new lotus.domino.axis.client.Service;

for this I get the following error:

Script interpreter error, line=3, col=50: Cannot find java public constructor 'lotus.domino.axis.client.Service()'

Whats wrong ?

How can I create an Service object with a public constructor?

I'm working with a Domino 8.5.2

Script interpreter error, line=3, col=50: Cannot find java public constructor 'lotus.domino.axis.client.Service()'

Petri Niemi commented on Jan 18, 2011

Re: Using existing Web Services in an Xpage

For me this helped with complex objects.

this.service.getTypeMappingRegistry().getDefaultTypeMapping().register(

fi.package.TypeClass,

new javax.xml.namespace.QName("http://ws.mesquerytoolsrv.mes.nokia.com/", "TypeName"),

new org.apache.axis.encoding.ser.BeanSerializerFactory(fi.package.TypeClass, new javax.xml.namespace.QName("http://namespace.fi", "TypeName")),

new org.apache.axis.encoding.ser.BeanDeserializerFactory(fi.package.TypeClass, new javax.xml.namespace.QName("http://namespace.fi", "TypeName"))

);

this.call.setReturnType(new javax.xml.namespace.QName("http://namespace.fi", "TypeName"));

Petri Niemi commented on Jan 18, 2011

Re: Using existing Web Services in an Xpage

For me this helped with complicated return objects.

this.service.getTypeMappingRegistry().getDefaultTypeMapping().register(

fi.package.TypeClass,

new javax.xml.namespace.QName("http://ws.mesquerytoolsrv.mes.nokia.com/", "TypeName"),

new org.apache.axis.encoding.ser.BeanSerializerFactory(fi.package.TypeClass, new javax.xml.namespace.QName("http://namespace.fi", "TypeName")),

new org.apache.axis.encoding.ser.BeanDeserializerFactory(fi.package.TypeClass, new javax.xml.namespace.QName("http://namespace.fi", "TypeName"))

);

this.call.setReturnType(new javax.xml.namespace.QName("http://namespace.fi", "TypeName"));

Anders Pamlin commented on Jan 14, 2011

Re: Using existing Web Services in an Xpage

I also get this java.lang.reflect.InvocationTargetException error from the line

var service = new org.apache.axis.client.Service;

I am running Domino 8.5.1.

Debco Support commented on Oct 20, 2010

Using existing Web Services in an Xpage

I can't seem to create the Service, I'm having thesame error as Claudio. Any help?

Claudio Riedi commented on Mar 15, 2010

Using existing Web Services in an Xpage

I get the following error on the first line of your example code

Script interpreter error, line=1, col=73: Error while calling java constructor 'org.apache.axis.client.Service()' (java.lang.reflect.InvocationTargetException).

Internal ClassLoader mismatch

Can you give me any hint?

Thanks

David Leedy commented on Jul 23, 2009

Return Parameters

It looks like this example is for a webservice that returns a single parameter. What would need to be changed if the web service returned multiple parameters?

Thanks!!