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 54724 - Generation of Debug target for EJB Freeform
Summary: Generation of Debug target for EJB Freeform
Status: RESOLVED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: EJB Freeform (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Andrei Badea
URL:
Keywords:
Depends on:
Blocks: 54726
  Show dependency tree
 
Reported: 2005-02-09 10:03 UTC by Martin Adamek
Modified: 2005-03-31 09:08 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 Martin Adamek 2005-02-09 10:03:17 UTC 
J2SE freeform provides generation of build file
with debug target which needs to be customized by
EJB freeform.
Comment 1 Vince Kraemer 2005-02-09 17:27:47 UTC 
This appears to be a new "feature".  We may need to push this to promo-F.

This is especially true since there really is not a well defined
semantic for execution of EJB Module projects, let alone debug.

About the only way to debug a ejb module is to put it into an
application that you would then debug.

Trying to make the menus "match", when the projects have radically
differeing semantics seems like a mistake [I assume that is the
motivation behind filing this issue]
Comment 2 Vince Kraemer 2005-02-09 18:15:43 UTC 
how on earth does this issue block the web FF project?
Comment 3 Martin Adamek 2005-02-10 06:27:38 UTC 
It's there just because of need to fix it on both projects (by same
person)
Comment 4 John Jullion-ceccarelli 2005-03-14 10:44:52 UTC 
As this stands right now, I'd say this is a P2 bug. The target that is generated
is completely useless for debugging an EJB module. Are we planning to fix this
for FCS? I need to at least know what the debug target will look like so I can
document it.
Comment 5 Andrei Badea 2005-03-14 14:37:06 UTC 
I'd say we actually don't know what the debug target should do. You can't debug
an EJB module by itself. Instead, you run the client of the EJB module (usually
a web module) in debug mode and make sure the sources of the EJB module are
available to the debugger. 

I will have to look at it more closely.
Comment 6 John Jullion-ceccarelli 2005-03-14 16:43:29 UTC 
What does debug project do when you run it on a standard EJB module project?
Just starts the server in debug mode, deploys the module, attaches the debugger,
and waits for you to access it with an application client, right?
Comment 7 _ ludo 2005-03-14 16:54:34 UTC 
correct.
Use case very limited, but ...
Comment 8 Andrei Badea 2005-03-31 09:08:42 UTC 
Checking in EjbFreeFormActionProvider.java;
/cvs/j2ee/ejbfreeform/src/org/netbeans/modules/j2ee/ejbfreeform/EjbFreeFormActionProvider.java,v
 <--  EjbFreeFormActionProvider.java
initial revision: 1.1
done
Checking in EjbFreeformProperties.java;
/cvs/j2ee/ejbfreeform/src/org/netbeans/modules/j2ee/ejbfreeform/EjbFreeformProperties.java,v
 <--  EjbFreeformProperties.java
initial revision: 1.1
done
Checking in EJBProjectNature.java;
/cvs/j2ee/ejbfreeform/src/org/netbeans/modules/j2ee/ejbfreeform/EJBProjectNature.java,v
 <--  EJBProjectNature.java
new revision: 1.12; previous revision: 1.11
done
Checking in Bundle.properties;
/cvs/j2ee/ejbfreeform/src/org/netbeans/modules/j2ee/ejbfreeform/Bundle.properties,v
 <--  Bundle.properties
new revision: 1.5; previous revision: 1.4
done