1. Create a wsdl.
2. Enter source view
3. Trigger Validate WSDl through context menue
[catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:932)
Looks like a Beta stopper for me.
What build are you using ?
Since it is MacOS specific it looks like Java 6 issue.
Is it reproducible with latest Java 5 ?
We have a lot of problems with current version of Java 6 for MacOS, since no
final version is released yet.
Marking as INCOMPLETE until submitter's feedback.
java version "1.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-164)
Java HotSpot(TM) Client VM (build 1.5.0_07-87, mixed mode, sharing)
OK, at least now we are sure that it is not a Java 6 issue.
Still need evaluation from development team.
Is this behaviour observed on a development build or official build?
Can QE make sure this is reproducible on a release551 build?
This is observed on Windows version as well as Mac OS version. Bill of material: NetBeans IDE 5.5.1 (Build
200702190600). Enterprise Pack: QBuild milestone 6a - 02/09/2007.
This AbstractMethodError is due to downloaded build mismatched.
This is not beta show stopper. However the introduced incompatible API method
still needs to be corrected to be compatible.
Ritesh, please make sure the introduced method getSchemaSource() has reasonable
Waiver since it is not a Beta stopper per evaluation
We do not want add a default implementation of this api.
We know which modules were using the old api and made changes to make sure they
use the new api.
This breakage was one time due to mismatch in net beans base version and
This should be fixed if you are using the 551 beta official build or in
release551. Seems like there is a problem in the version you are using which
does not have the latest netbeans?
Can you try with next build.
Please provide either the process or the links, that would bring me the proper bill-of-material and I'm
more than happy to give it a try. I'm not sure what you understand with "the next build". I need the
documented process of obtaining the Netbeans 5.5.1 version as well as the Enterprise Pack version your
With the following version of ID and EP, the problem is gone:
netbeans-ent_pack-5_5_1-daily-070225_2-windows.exe. Thanks to the patient and terrific team behind
As johaneltes agreed that this was build mismatch between netbeans and entpack and
fixed. I am closing this bug.
Accepting the reporter's comments as verification.