Created attachment 68377 [details]
error message 1

Created attachment 68378 [details]
Error message 2

After the second message box the output window says:

Target "FolioService1-client-wscompile" does not exist in the project "EJBModule1". 
BUILD FAILED (total time: 0 seconds)

Hopefully last comment... the WSDL URL uses https on port 8443 and HTTP BASIC authentication (user/password).  I can
generate and use a client from NB 6.1 and NB 6.0 for this URL.

Support for JAXRPC clients in EJB modules was added in 6.1 but ejb modules schema has not been updated to allow
web-service-clients element therefore validation on project.xml (which was implemented ~1-2months ago) fails.

Passing to Rico and cc'ing David (maintainer of ejbjarproject) since I'm not 100% sure if this can be fixed in a
backward compatible way without updating ejbjar project's schema

I mean "without updating a version of ejbjar project's schema"

I cannot (or perhaps just do not know how to) reproduce it. Enhancing existing schema should resolve the problem - all
you want to do is to add this optional element there. In general Web Services should have had their own schema and data
section in project.xml.

here are steps:
-get some 6.5 build (or use the local one build with cluster.config=j2ee)
-install JAX-RPC module from dev UC[1]
-restart the IDE
-create new EJB module
-go to new File -> Web Services -> Web Service client wizard
-switch to WSDL URL and use there: http://ws.fraudlabs.com/browserobjectwebservice.asmx?wsdl
-change JAX version combo from JAX-WS to JAX-RPC
-finish the wizard

=> fails with validation error

[1]: or get *jaxrpc* (3) + *registry (1) nbms files from
http://deadlock.netbeans.org/hudson/job/nbms-and-javadoc/lastSuccessfulBuild/artifact/nbbuild/nbms/extra/

The problem lies somewhere else - we should never allow creation of JAX-RPC ws client for EJB,since it's impossible due
to missing support for JAX-RPC in EJB. This issue should be about fact,that Client Style dropdownlist in ws client
wizard is enabled for EJB3 module,which is wrong.There should be only JAX-WS option permanently selected and
dropdownlist disabled.

Are you sure about that? I asked a similar question about JAX-RPC/EJB service endpoints instead of clients the in
GlassFish users forums:  

"Can EJB 3.0 expose JAX-WS *and* JAX-RPC endpoints?" Kenneth Saks (lead architect of EJB 3.0 container) said:

From a spec perspective there's no limitation that all components in a module or application have to be one or the
other. Each stateless session bean can be implemented as either a JAX-WS or JAX-RPC endpoint. Of course, JAX-WS is the
recommended approach going forward. JAX-RPC will be a candidate for pruning from a future version of the Java EE
platform and will not be available as an option for the new EJB 3.1 Singleton component.

http://forums.java.net/jive/thread.jspa?messageID=295440

We need to upgrade schema file for project.xml.
It's just a luck it was working in 6.1 since there was no project.xml validation against the schema file.
Working on that for now.

XML schema for project.xml upgraded:
http://hg.netbeans.org/main?cmd=changeset;node=30057fd91295

We also need to update xml schema located at
http://www.netbeans.org/ns/j2ee-ejbjarproject/3.xsd

public schema on the web updated as well:

IDE: [8/27/08 12:16 PM] Committing "3.xsd" started
Checking in 3.xsd;
/cvs/www/www/ns/j2ee-ejbjarproject/3.xsd,v  <--  3.xsd
new revision: 1.4; previous revision: 1.3
done
IDE: [8/27/08 12:16 PM] Committing "3.xsd" finished

=> f.

Integrated into 'main-golden', available in build *200808280201* on http://bits.netbeans.org/dev/nightly/
Changeset: http://hg.netbeans.org/main/rev/30057fd91295
User: mkuchtiak@netbeans.org
Log: #145213: extend schema for project.xml

Verified with NetBeans IDE Dev (Build 200810140201).