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 30361

Summary:	Avoid ServletDataObject that subclasses JavaDataObject
Product:	javaee	Reporter:	_ rkubacki <rkubacki>
Component:	Code	Assignee:	Pavel Buzek <pbuzek>
Status:	RESOLVED FIXED
Severity:	blocker	Keywords:	USABILITY
Priority:	P3
Version:	3.x
Hardware:	PC
OS:	All
Issue Type:	TASK	Exception Reporter:
Bug Depends on:
Bug Blocks:	26728, 31628

Description _ rkubacki 2003-01-27 10:48:21 UTC

Currently there are following reasons to do it:

- custom properties (might be solved by looks)
- special default executor
- syncing of depl. descriptor with content of
WEB-INF/classes (after copy/move/delete)

disatvantages: 

- relies on Java module internals 
- doesn't scale (conflicts with other subclasses
of JDO like JDO/RMI/forms)
- works for sources only - front controller in
Struts hasn't this support

Comment 1 Pavel Buzek 2003-06-10 14:13:15 UTC

the new design will use ProjectEnvironmentProvide and looks

Comment 2 Pavel Buzek 2003-12-10 05:28:57 UTC

closing obsolete issues related to prj40_prototype

Comment 3 _ rkubacki 2003-12-10 08:42:52 UTC

I don't agree. Maybe we can live with this in 3.x but in principle it
is a bad approach. All disadvatages are still valid and we should get
rid of it.

Don't forget about usability problems - hard to understand concept of
'Mark as Servlet'/'Cancel servlet' and many threads on nbusers
confirming that the current solution is not very intuitive. To go
further idea of servlet execution is bad IMO. It is always web
module/j2ee app what is deployed (optionally started) and can execute
when there is a request.

Comment 4 Pavel Buzek 2004-06-23 14:00:22 UTC

fixed in trunk