Created attachment 42614 [details]
compapp project to reproduce

Created attachment 42615 [details]
xslt project to reproduce

Additional info:
 - using NB IDE build Dev 070516
 - a similar issue in the past was caused by improperly defined jbi descriptor,
but that is not the case here

I am not sure if the XSLT project generates its jbi.xml correctly. 

Using a slightly older build, the XSLT project builds fine but there is only one endpoint generated. Your test case
tries to test a portType that has nothing to do with the generated endpoint, thus the test error. Trying to open the
transformation.xml file, but got the following exception: 
java.lang.AssertionError: reference should be TMapComponent type to create TMapComponent type Node
	at org.netbeans.modules.xslt.tmap.nodes.NavigatorNodeFactory.createNode(NavigatorNodeFactory.java:95)
	at org.netbeans.modules.xslt.tmap.nodes.NavigatorNodeFactory.getTransformMapNode(NavigatorNodeFactory.java:62)
	at org.netbeans.modules.xslt.tmap.navigator.TMapLogicalPanel.initNavTree(TMapLogicalPanel.java:160)
	at org.netbeans.modules.xslt.tmap.navigator.TMapLogicalPanel.getBeanTreeView(TMapLogicalPanel.java:170)
	at org.netbeans.modules.xslt.tmap.navigator.TMapLogicalPanel.showNavTree(TMapLogicalPanel.java:142)
	at org.netbeans.modules.xslt.tmap.navigator.TMapLogicalPanel.navigate(TMapLogicalPanel.java:88)
	at org.netbeans.modules.xslt.tmap.multiview.tree.TreeMultiViewElement.createTreeView(TreeMultiViewElement.java:285)
	at org.netbeans.modules.xslt.tmap.multiview.tree.TreeMultiViewElement.initializeUI(TreeMultiViewElement.java:293)
	at org.netbeans.modules.xslt.tmap.multiview.tree.TreeMultiViewElement.<init>(TreeMultiViewElement.java:91)
	at org.netbeans.modules.xslt.tmap.multiview.tree.TreeMultiViewElementDesc.createElement(TreeMultiViewElementDesc.java:57)
	at org.netbeans.core.multiview.MultiViewModel.getElementForDescription(MultiViewModel.java:191)
	at org.netbeans.core.multiview.MultiViewModel.getActiveElement(MultiViewModel.java:111)
	at org.netbeans.core.multiview.MultiViewModel.getActiveElement(MultiViewModel.java:107)
	at org.netbeans.core.multiview.MultiViewPeer.privateGetUndoRedo(MultiViewPeer.java:463)
	at org.netbeans.core.multiview.MultiViewPeer.access$500(MultiViewPeer.java:63)
	at org.netbeans.core.multiview.MultiViewPeer$DelegateUndoRedo.removeChangeListener(MultiViewPeer.java:718)
	at org.openide.actions.UndoAction$Listener.propertyChange(UndoAction.java:170)
	at org.openide.util.WeakListenerImpl$PropertyChange.propertyChange(WeakListenerImpl.java:164)
	at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339)
	at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:276)


Using NB 6.0 M10, the XSLT project doesn't even build. I got the following error which points to the XsltProjectJBIGen
ant task:

...
init:
deps-sub-project:
PackageRetrievedFiles:
C:\Documents and Settings\jqian\Desktop\104446\XsltModule1\nbproject\build-impl.xml:141: java.lang.RuntimeException:
java.lang.NullPointerException
BUILD FAILED (total time: 6 seconds)

See also:
http://www.netbeans.org/issues/show_bug.cgi?id=87035
http://www.netbeans.org/issues/show_bug.cgi?id=92997

This problem has prevented me from using SOA. 
Please fix this soon!
rwtibbs

Kevan I looked at your test case and saw that you use incorrect operation (instead described copyEmpl with binding
http://localhost:13011/xsltRRPort there is copyJbiEmpl with binding http://localhost:13012/xsltRRJbiPort )

Kevan could you please check it.

If the test case is incorrect, then it was generated incorrectly by driver test framework.  Please discover the issue
and fix; this ticket has gone unresolved for over 2 months!!

Jun, please looks like problem in test driver.

On the third step of the Test case creating there are shown 3-operations,
So it's possible to choose wrong operation.

Since I still can't build the attached XSLT project, I don't know what is really going on in that project. But I don't
think there is anything wrong about the test driver.

In the following user scenario, I will use our beloved SynchronousSample as an example.

1. Create SynchronousSample;
2. Add a new PortType to the WSDL file in the BPEL project. Also add concrete Binding and Service/Port for the new PortType;
3. Create a new test case in the SynchronousSampleApplication to test the new binding operation created in step 2;
4. Deploy SynchronousSampleApplication;
5. Run the new test case created in step 3.

The test will obviously fail because in the BPEL project's generated jbi.xml file, there is no Provides/Consumes
endpoint that corresponds to the new WSDL Port created in step 2. On the other hand, there is nothing to prevent the
user from creating the test case in step 3. So in this case I would say this is a user error. The failure in the test
run is the correct behavior.

As to the original issue, I am going to mark it as WON'T FIX because it's a user error.

Reassigning to XSLT team to fix the XSLT project build problem.

yes transformmap is of old style and that's the reason why xslt project can't be built.
But the root cause of the bug is that user specified incorrect operation.
When (after manual fixing of transformmap) we changed "Destination" property of Test from
http://localhost:13012/xsltRRJbiPort to http://localhost:13011/xsltRRPort test works OK.
So it's user fault. Close as WONTFIX.