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.

Bug 59612 - sun-web.xml not updated after action "Call EJB" in Servlet
Summary: sun-web.xml not updated after action "Call EJB" in Servlet
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Vince Kraemer
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2005-06-03 16:27 UTC by L Martinek
Modified: 2005-09-05 10:12 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description L Martinek 2005-06-03 16:27:09 UTC 
My automated test fails when uses "Call EJB" in Servlet. Element <ejb-ref> is
not added to sun-web.xml. I was able to reproduce it manually, but not always.

I have Enteprise Application containing Web Application and EJB Module. EJB
Module has one Session Bean and one Entity Bean. Web Application has one Servlet.

Then I did following:
1. Started Pointbase database
2. Connected DB explorer to sample database
3. Added business method to Session Bean
4. Added business method to Entity Bean
5. Added create method to Entity Bean
6. Added home method to Entity Bean
7. And finally called "Call EJB" in Servlet.

Then sun-web.xml was not updated. When I tried to skip some step (e.g.
connecting to pointbase) bug didn't appear.
Comment 1 Milan Kuchtiak 2005-06-06 12:01:15 UTC 
It seems to be a problem in plugin.
The mechanism how plugin listens to changes in web.xml need to be investigated.
Comment 2 L Martinek 2005-06-09 18:31:20 UTC 
Similar situation is for Call EJB in Web Service. <ejb-ref> is also not added to
sun-web.xml.
Comment 3 Vince Kraemer 2005-07-22 17:27:17 UTC 
Is this a new test or a new failure?

If this test had been passing, then we might need to check for changes that
caused a regression.

If the test is new, the debugging strategy may be different.
Comment 4 L Martinek 2005-07-25 09:12:33 UTC 
I found this bug when I was developing automated tests so the test fails from
the biginning.
Comment 5 Vince Kraemer 2005-08-25 17:56:33 UTC 
If the beans have local interfaces and you use the local interface, the
sun-web.xml doesn't need to be updated....

Please re-open if you see this when using the remote interface...