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.
Steps to reproduce: - create a new BPEL Blueprint 2 project - start App server - make sure it is created with the default name (just make sure there is no such project already in the folder where you create the project) - try to deploy it Deployment will fail with the following exception in log: Building jar: C:\Documents and Settings\Administrator\BluePrint2\BluePrint2Application\build\BCDeployment.jar IOException: A parsing error occurred; the xml input is not valid copying Sub-Assembly: C:\Documents and Settings\Administrator\BluePrint2\BluePrint2Application\build\null Build AU Failed: java.lang.NullPointerException java.lang.NullPointerException at org.netbeans.modules.compapp.projects.jbi.anttasks.BuildServiceAssembly.execute(BuildServiceAssembly.java:325) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.tools.ant.Target.performTasks(Target.java:369)
You can reproduce this with non-default name too
please run the Blueprint projects according to blueprint documentation - from the description below it looks like you are renaming projects or creating new ones - if you want to do that you need to know what other entries should be changed in order to have the projects work again - this is Netbeans knowledge not knowledge tied to blueprints in particular
We used the default setting to create this sample project. I don't understand why you said we renamed it. In the decsription, the reporter already mentioned "make sure it is created with the default name". The same steps work fine in Coke Beta2 version IDE.
The build we tested: Coke nightly build 060905.
Updated versions of BPEL BluePrints 1-5 have been added to the release55 branch. Projects can be successfully deployed / run in our local testing - waiting for confirmation from Hong that the projects work in the next continuous build.
Marking the bug as fixed - updated versions of BPEL BluePrints 1-5 have been added to the release55 branch. Awaiting retesting by QE.
The behavior described in the description is fixed but we still have problems when non-default name is used. verified in build m20a