This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
If you change j2se platform for project with websvc you cannot compile it. Javac uses the explicit platform but wscompile uses the default and reports unsupported version of classfiles.
Could I get steps to reproduce please? Did you add a new platform? Which one? Did you change javac compile settings? Which ones?
needed for 4.1!
but maybe not possible, as there is no way to control the wscompile tool to change its javac flags...
Due to the addition of building J2EE projects with -target 1.4 when running on JDK 1.5, I think this is a MUST FIX for 4.1. However, as far as I can tell, there is *no* way to tell wscompile to tell javac to use -target 1.4 when compiling the service (or client). So the only way I see to resolve this for 4.1 is this: 1) We wscompile save the source code (we already do this) 2) Throw away the class files it will generate (wish they had /dev/null on windows for an easy way to do this). 3) Augment the build script generated for services and clients to have an additional step that compiles the service/client source using the appropriate javac command. I think this should be doable. Comments?
there is no other solution that what you propose... Unless the jax-rpc team has a better idea, go for it.
*** Issue 56430 has been marked as a duplicate of this issue. ***
This is related to bug #55797. I have a proof of concept that will resolve this, need to integrate changes into build-impl.xsl for web/project and j2ee/ejbjarproject
Integrated build script changes for web services and web service clients into web/project and j2ee/ejbjarproject. The effect of the changes is as follows: There are now 3 web service target directories under build/generated, named wsclient, wsservice, and wsbinary. Client source code is generated to wsclient, service source (except from wsdl case) is generated to wsservice and binaries (.class files) in both cases are put in wsbinary (which is a throw-away directory. These files are not and should not be used.) For clients, after client source code is generated for all clients, javac macro is used to compile them. For services, no such compile step is needed since in all current development use cases, the service source code is in the src tree and was already being compiled with javac macro. However, service generation had to be retargeted to not place generated source in the same location as client generated source.
v.