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.
Under some unknown conditions, the xendorsed flag in wsimport gets erased if the build-impl.xml gets regenerated. To reproduce, simply unzip the attached StockQuoteClient project. Before you open it, you will see the build-impl.xml has the xendorsed flag in it. When you open it in the IDE, the build-impl.xml will get regenerated and the xendorsed disappears.
Created attachment 41596 [details] StockQuoteClient project for reproducing the issue
I am unable to reproduce this, with the instructions that you gave. I opened the project and after a few seconds the build-impl.xml was regenerated and the xendorsed option in the wsimport invocation was still there. So I tried to change the project.xml, saved it (which shd trigger another regen), xendorsed still there. Closing as worksforme.
Hi Rico, it turns out the workaround I put in stopped working. It is likely something else changed in the latest build that caused the build-impl to get generated. At this point, since I don't really have control over the regeneration of build-impl.xml, I am reopening this bug as a stopper issue. As for reproducing the issue, simply unzip the attached project. Before you open the project, take a look at the build-impl.xml. The wsimort-client-StockService has the xendorsed flag turned on. After you open the project, you'll noticed that the build-impl.xml gets regenerated and the xendorsed flag is gone.
The problem is that if the project does not have the j2ee.server.instance property set in the private.properties file, it is assumed that the EE project is targeted at GF V1. The sample project was generated with no entries in the private.properties file. The solution is as follows: if the private.properties file does not have the j2ee.server.instance property, look up the j2ee.server.type property in the project.properties file. If it is defined, look up the instances of that type from the server registry and use that information to determine the target server. Fixed in the trunk.
Created attachment 41783 [details] Diff file for WebProject.java
Created attachment 41784 [details] Diff file for WebProjectJAXWSVersionProvider
Created attachment 41785 [details] Diff file for EJBProjectJAXWSVersionProvider
Created attachment 41787 [details] SORRY! Previous one was the wrong diff this is the right one
Created attachment 41788 [details] SORRY! Previous one was the wrong diff this is the right one
The fix looks correct. You can put it to M9 branch.
Applying fix to App Client project. Diff attached.
Created attachment 41907 [details] Diff for AppClientJAXWSVersionProvider
The patch looks fine.
In which milestone has this been fixed? Peter, can you verify this, please? Thanks.
I believe this was fixed before Java ONE so that would be Milestone 9
v.