Re: [Axis2] Any way to use GoogleSearch.wsdl with Axis2?

[Christian Kloner]

depends what you want to do? just querying for yourself or do you want 
to integrate the google search results into your application?


VinceK wrote:

What would be the best way to use  http://api.google.com/GoogleSearch.wsdl
with Axis2?




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

wsdl stub generation(element without name attribute allowed!!!??!!?!?!)

[Christian Kloner]

hi,

A friend of mine has written a wsdl file which has in the schema part 
elements like this:










as you can see, the element tag

contains no attribute "name" which is not valid if you validate against 
the schema. but in netbeans 5.5 with the enterprise pack, you can 
validate whole wsdl files, and there it is completely valid to have such 
an element tag in it. so i am just wondering if it is valid or not (bug 
of netbeans???). the stubs generated from the above code fragement 
produce the following output:


http://aurigafactory.gridminer.org";>

http://www.localhost:8080/auriga/FactoryInstanceWorkflowEPRSecond.xml



So is this allowed/valid? thanks in advance.
chris

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: question

[Christian Kloner]

hi Bret,

I am using globus4 (axis 1.2) and Axis2 with my dynamic invocation API 
so i am not sure if it this is working but is there the attribute 
"mapping-file" where you can specify the namespace to package mapping 
like below?



"NStoPkg.mappings" file (
New to axis 2.

 


In my ant script I have the following:

 




 

I noticed the generated package name is now this, “com.test.www.client.” 
and “com.test.client.” how do I remove the unwanted www?


 


Regards

 


Bret


This e-mail message and any attachments may contain private, 
confidential, proprietary or privileged material of GoldenGate Software, 
Inc. that is for the sole use of the intended recipient(s) of this 
e-mail message. Any review, copying or distribution or other use of this 
e-mail message or any attachments hereto by anyone other than the 
intended recipient(s) is strictly prohibited. If you are not the 
intended recipient(s) of this e-mail message, please contact GoldenGate 
Software, Inc. (415-777-0200) immediately and permanently delete the 
original e-mail message and any copies of this e-mail message and all 
attachments, if any.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[Axis2] What does the property "Chunk" mean in detail + classdiagrams somewhere?

[Christian Kloner]

hi,

I have to write a report about axis2 and would be very grateful if 
somebody would tell me what this "chunk" means in detail. I know that 
the google Web Serive is working if I turn it off. So there is the 
content-length of Soap message in the HTTP header. Does this "chunk" 
brings any performance and how? didn't find information about it.
So is there somewhere a detailed desciption of the properties which can 
be setted in Axis2?


Are there also somewhere nice class diagrams?

Chris

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Document Literal vs Document Wrapped vs RPC Encoding

[Christian Kloner]

in fact, there are quite a lot of articels, which insists not to use 
rpc/encoded and hopefully the few web services out there which are still 
using rpc/encoded will change it. this is very old style but 
unfurtunatelly axis 1.2 and i think also axis 1.3 has it set as default. 
but axis2 goes in the right direction and comes with a much faster 
engine for doc/literal. :)


besides the basic profile of the ws-i (http://www.ws-i.org/) insists on 
using doc/literal, which results in fewer bytes to transmit, because the 
types of the values are not transmitted! and the ugly array encoding in 
the soap envelope with multi-refs will belong to the past. :)



Alejandro Ariel de Lio schrieb:
I think that the thing is that when you do soap rpc literal messages 
you may find it difficult to validate messages in deserializing time. 
That's because you use the name of the wsdl message element and not 
the name of the xsd element itself.
 
 
-Mensaje original-

*De:* Anne Thomas Manes [mailto:[EMAIL PROTECTED]
*Enviado el:* viernes, 03 de febrero de 2006 4:08
*Para:* axis-user@ws.apache.org
*Asunto:* Re: Document Literal vs Document Wrapped vs RPC Encoding

Quite a few SOAP engines don't support rpc/literal, therefore
doc/literal (wrapped or unwrapped) is a better idea than
rpc/literal. I generally recommend using wrapped doc/literal for
best interop and easiest development and configuration. Note that
.NET supports wrapped doc/literal by default.

Anne

On 2/2/06, *Cyrille Le Clerc* <[EMAIL PROTECTED]
> wrote:

WS-I Basic Profile, the reference for SOAP interoperability,
says it
prefers "literal" rather than "encoded" :
  Extract : "As a result, the Profile prefers the use of literal,
non-encoded XML."
  Chapter : "4.1.7 SOAP encodingStyle Attribute"
  URL :

http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16448072



Unfortunately, I did not find in this spec any clear statement
saying
that "document" (in a wrapped style) is preferred to "rpc".
However, you will find many articles that say "document" is
preferred to "rpc".

Cyrille

--
Cyrille Le Clerc
[EMAIL PROTECTED] 
[EMAIL PROTECTED] 

http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html

On 2/2/06, Jyotishman Pathak <[EMAIL PROTECTED]
> wrote:
> Dov,
>
>  I found this article [1] from IBM to be quite useful. At
the same time, I am interested in knowing more about your
investigation.
>
>  Thanks,
>  - Jyoti
>
>  [1]

http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/?ca=dgr-devx-WebServicesMVP03
>
>
>
>
>
> On 2/2/06, Balaji D L <[EMAIL PROTECTED]
> wrote:
> >
> >
> >
> > Can you share your analyse with us ??
> > It will be very useful.
> > Regards
> > Balaji
> >
> > - Original Message 
> > From: Dov Rosenberg <[EMAIL PROTECTED]
>
> > To:  axis-user@ws.apache.org 
> > Sent: 02 February 2006 14:21:37
> > Subject: Document Literal vs Document Wrapped vs RPC Encoding
> >
> > I have done a bunch of investigating to determine the
differences/benefits/limitations of the 3 styles of WSDL
generation. In general it seems that the preferred version is
Document Literal. Are there any other opinions as to the most
popular version?
> >
> > Thanks in advance
> >
> >
> > --
> > Dov Rosenberg
> > Inquira Inc
> > 370 Centerpointe Circle, ste 1178
> > Altamonte Springs, FL 32701
> > (407) 339-1177 x 102
> > (407) 339-6704 (fax)
> >  [EMAIL PROTECTED] 
> > AOL IM: dovrosenberg
> >
> >
>
>
>
> --
> Jyotishman Pathak
> WWW: http://www.cs.iastate.edu/~jpathak

Re: ArrayList in Webservices

[Christian Kloner]

Yes. Would say the same. But if you want to use Soap on every price so 
you dont know what times will come and you must be interoperable, I must 
say it is not possible to use ArrayLists! You can only use arrays and 
each element must be of the same type. because soap specifies this and 
java is using this specification. if it was not so, soap would have no 
sense! if the types in the array are no primitive datatypes but a 
dataype of your own, you need a deserializer rather serializer to 
register with the specified element namespace/name. So if the soap 
message is parsed it will use the specified deserializer to push the 
soap values into the java class values.


lg,
chris

Jay Glanville schrieb:
If your server and clients are both java, soap may not be the best 
communication protocol for you.  I'd actually recommend a binary based 
protocol like RMI or Hessian/Burlap for such situations.  Binary 
protocols perform better then text based ones.
 
Generally, SOAP is great for interoperating between different 
platforms.  If all the platforms are the same, then there's probably a 
better way.
 
Just my 2 cents.
 
JDG



*From:* Nayana Hegde [mailto:[EMAIL PROTECTED]
*Sent:* Friday, February 03, 2006 8:35 AM
*To:* axis-user@ws.apache.org
*Subject:* Re: ArrayList in Webservices

Hi,
 
  Our application has to support only java. Can anyone let me know

what are the criteria to be satisfied If I have  to write a
Serializer and Deserializer for ArrayList? Thanks for the same

 
On 2/3/06, *Anne Thomas Manes* <[EMAIL PROTECTED]

> wrote:

If you plan to support interoperability with any language
other than Java (or even any SOAP engine other then Axis), you
should not expose Java Collections through your WSDL
interface. You should convert them to arrays.

Anne


On 2/3/06, *Nayana Hegde* <[EMAIL PROTECTED]
> wrote:

Hi,
 
The following is the class which I have exposed as a

webservice.
 
public class Test {


 public ArrayList getArrayList(){
  ArrayList list = new ArrayList();
  TestObject obj = new TestObject();
  obj.setName("First");
  list.add(obj);
  TestObject obj1 = new TestObject();
  obj1.setName("Second");
  list.add(obj1);
  return list;
 }
 public HashMap getMap(){
  HashMap map = new HashMap();
  map.put("First","First");
  map.put("Second","First");
  return map;
 }
}
 
Now when I access the method getArrayList in the client

side it is getting resolved as an Object array instead of
an ArrayList but when I access the getMap() it is getting
resolved correctly. Can you let me know the reason for the
above? Is there any configuration changes that have to be
done for the above to work. 1.2beta3 1009 August 17 2004.
 



  

 

com.db.cc.object.TestObject" qname="ns4:TestObject"
xmlns:ns4="urn:object.cc.db.com "/>
  
 
 
Thanks and Regards,

Nayana