Created attachment 47290 [details]
screenshot

valid bug.

Rico has fixed similar issue last week. I tried to reproduce this with latest source and it works for me now.

This is reproducible again in 20071015 and now Call WS Op doesn't work even for operations outside of project (in
previous case at least this worked).This is showstopper for Beta 2. Reopening.

Note: This happens when source level is set to 1.6 .

Ajit and Rico can not repduce on windows with jdk 6. with trunk build and jaxrpc plugin from UC.
marking fixed.
can you verify?

still happens, I have:

-latest beta2 build from http://bits.netbeans.org/download/6.0/beta2/latest/
-latest jaxrpc plugin (from this UC:
http://deadlock.netbeans.org/hudson/job/javadoc-nbms/lastSuccessfulBuild/artifact/nbbuild/nbms/updates.xml.gz)

and I did:
-start IDE with clean userdir and install JAXRPC plugin
-create new java application project
-create new websvc client in it (ie for http://www.mindgram.com/api/sched_call.wsdl)
-go to main method in the main class (file which has been created as part of javapp project)
-invoke call ws operation and select "getSchedule" operation

=> OK button in the dialog is still disabled, but should be enabled

important thing I forgot to say is that IDE must be running on JDK6

reproducible with the instructions from Lukas.

With the steps given by Lukas, its reprodicuble on trunk too.
the culprit is JaxWsInvokeOperationProvider.
The check for java project
projectType == ProjectInfo.JSE_PROJECT_TYPE && isJaxWsLibraryOnClasspath(targetSource)
returns true if source level set to 6.
So jaxwscookie is returned instead of jaxrpc.
Since the wsclient is 1.4 the dialog disables the ok button.
-->rico to address jaxws issue.

Created attachment 51188 [details]
Diff file of JaxwsInvokeOperationProvider

Created attachment 51189 [details]
Diff file of JaxrpcInvokeOperationProvider

Fixed in trunk by determining if J2SE project has a JAXRPC or JAXWS
client.

I can still reproduce this with Lukas's steps in (Hudson trunk 4022).

I've tested with old version of JAX-RPC plugin,which most probably doesn't contain the fix. I'll wait for new version of
JAX-RPC plugin and test it again.

I've tested with old version of JAX-RPC plugin,which most probably doesn't contain the fix. I'll wait for new version of
JAX-RPC plugin and test it again.

I've tested with old version of JAX-RPC plugin,which most probably doesn't contain the fix. I'll wait for new version of
JAX-RPC plugin and test it again.

The test looks fine.

My comment :
the line 73 in JaxRpcInvokeOperationProvider can be deleted I think :
if(projectType == ProjectInfo.JSE_PROJECT_TYPE && !isJAXWSProject(project) && !isJAXRPCProject(project)) return true;

(it's not harmfull, however, the test is already included in JaxWsInvokeOperationProvider)

Nevertheless, when I click the OK button in Call WS Operation action (JAX-RPC client, any project type), the NPE is thrown :
java.lang.NullPointerException
        at
org.netbeans.modules.websvc.jaxrpc.actions.JaxrpcInvokeOperationGenerator.generateJavaClientCode(JaxrpcInvokeOperationGenerator.java:577)
        at
org.netbeans.modules.websvc.jaxrpc.actions.JaxrpcInvokeOperationGenerator.insertMethodCall(JaxrpcInvokeOperationGenerator.java:536)
        at org.netbeans.modules.websvc.jaxrpc.actions.JaxRpcInvokeOperation.invokeOperation(JaxRpcInvokeOperation.java:34)
        at
org.netbeans.modules.websvc.core.webservices.action.InvokeOperationAction.performAction(InvokeOperationAction.java:110)
        at org.openide.util.actions.NodeAction.performAction(NodeAction.java:289)
        at org.openide.util.actions.CallableSystemAction$1.run(CallableSystemAction.java:118)

well, original issue is fixed, but after pressing OK button, I'm getting:

java.lang.NullPointerException
	at
org.netbeans.modules.websvc.jaxrpc.actions.JaxrpcInvokeOperationGenerator.generateJavaClientCode(JaxrpcInvokeOperationGenerator.java:577)
	at
org.netbeans.modules.websvc.jaxrpc.actions.JaxrpcInvokeOperationGenerator.insertMethodCall(JaxrpcInvokeOperationGenerator.java:536)
	at org.netbeans.modules.websvc.jaxrpc.actions.JaxRpcInvokeOperation.invokeOperation(JaxRpcInvokeOperation.java:34)
	at org.netbeans.modules.websvc.core.webservices.action.InvokeOperationAction.performAction(InvokeOperationAction.java:110)
	at org.openide.util.actions.NodeAction.performAction(NodeAction.java:289)
...

Anyway there's a workaround for the user to switch source level of the project to 1.5, therefore changing to P2.

Tested on latest hudson dev build and not reproducible anymore.Probably already fixed.

Yes, I got the exception.
The NPE is related to the scenario when JAX-RPC client from another project (J2SE) is called into the current J2EE14
project (webapp or ejb). We should probably disable this scenario.

Fixed.

Diff:
http://websvc.netbeans.org/source/browse/websvc/jaxrpcsupport/src/org/netbeans/modules/websvc/jaxrpc/actions/JaxrpcInvokeOperationGenerator.java?r1=1.3&r2=1.4

There is also a minor issue related to calling WS Operation from another project:
- another project is not added on classpath (issue 112777)

VERIFIED