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.
This problem will be hit by most medium to large applications that are comprised of multiple modules. When running verifier action on EJB/Web modules App server plugin's verifier action should include all dependencies as per J2EE spec. How to reproduce : Use attached Blueprints Adventure Builder application. Extract this archive to a private directory. Open all projects. Start Appserver and Pointbase database. Run "adventure_setup" ANT project. Make sure all server resources are configured. Now Select each of EJB/Web modules, Run "Build" and "Verify" actions on each of the modules. While running Verifier action on "OPC-EJB" Observe the following errors. This is not appearing when user runs verifier action at J2EE application level. See also similar bug "6359421" for more details. -------------- FAILED TESTS : -------------- Test Name : tests.webservices.EJBEndpointIsSLSBCheck Test Assertion : For a stateless session bean implementation, the ejb-link element associates the port-component with a session element in the ejb-jar.xml file. The ejb-link element may not refer to a session element defined in another module. Please refer to JSR 109 Section #7.1.2 for further information. Test Description : For [ WebServiceBroker#opc-ejb#BrokerServiceIntfPort ] Service implementation bean could not be resolved from the ejb-link specified. Test Name : tests.webservices.EJBEndpointIsSLSBCheck Test Assertion : For a stateless session bean implementation, the ejb-link element associates the port-component with a session element in the ejb-jar.xml file. The ejb-link element may not refer to a session element defined in another module. Please refer to JSR 109 Section #7.1.2 for further information. Test Description : For [ OpcPurchaseOrderService#opc-ejb#PurchaseOrderIntfPort ] Service implementation bean could not be resolved from the ejb-link specified. Test Name : tests.webservices.EJBEndpointIsSLSBCheck Test Assertion : For a stateless session bean implementation, the ejb-link element associates the port-component with a session element in the ejb-jar.xml file. The ejb-link element may not refer to a session element defined in another module. Please refer to JSR 109 Section #7.1.2 for further information. Test Description : For [ OpcOrderTrackingService#opc-ejb#OrderTrackingIntfPort ] Service implementation bean could not be resolved from the ejb-link specified.
Created attachment 27993 [details] Test Application
I guess I missed that in the spec... Do you have a reference for this? BTW: why are you filing a "plugin bug" against j2ee/ejbproject?
Verifier tool is providing this message. May be some body from appserver team have information on Specs. I do not have EJB specs with me.
closing. Verifying a module that has been tailored to a particular application SHOULD NOT verify if the module is examined for "portability" (which is what the verifier does when you point it at a module) in isolation. That is exactly the kind of situation you are running into. The Verifier verifies the thing you ask it to verify. It is NOT clairvoyant and cannot figure out that the module you are verifyings is part of something that you want to use as "context".
It may be good idea to inform user about this situation. Plugin may provide some detailed message in outut windows, so that user should expect this kind of errors. The information presented by verifier action in studio may not be good enough for the user to understand what went wrong.