Necessary or not I am not sure, but if you have the control of the api (both server and client), then you can do so, and I am sure it'll work. You can look at the wsdl now to see what is returned. You can file bug report for it (please do) if it appears to be a bug. Your function maynot even work at all.
For example, did you call your function such as this:
handler.query(...);
or:
Object obj = handler.query(...);
If it works, and you have time, you can use reflection to find out what obj is.
[EMAIL PROTECTED] wrote:
There is no arrayHolder. Is one necessary here?
In a message dated 7/15/2004 3:48:01 PM Eastern Standard Time, [EMAIL PROTECTED] writes:
Maybe looking at the api closer. It could be an array holder that hold the value of the return array. If you write both the client and server code, you can also change the api to do so. That should work.
[EMAIL PROTECTED] wrote:
> The program never gets passed this line:
> > java.lang.Object[] yes_list = (String[])handler.query(groupName,
> password, accountName, conditions);
> I receive a runtime error simply stating a classCastException has
> occurred and it stops. NOTHING else is written.
> > THanks for your help so far!
> James
> > In a message dated 7/15/2004 3:36:10 PM Eastern Standard Time,
> [EMAIL PROTECTED] writes:
>
> What does this mean? Can you do this:
>
> java.lang.Object[] yes_list = (String[])handler.query(groupName,
> password, accountName, conditions);
>
> Then:
> String syes_list [];
> if(yes_list != null){
> syes_list [] = new String[yes_list.length];
> ...array copy here.
> }else{
> syes_list = null;
> }
>
> If this works, then search and vote for this bug in Sun's bug
> database.
>
> > Making them Objects[] does not work.
>
>
>
