Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 334798 - Ctrl-Shift-B hotkey to add breakpoints does not work when in J2EE Perspective
Summary: Ctrl-Shift-B hotkey to add breakpoints does not work when in J2EE Perspective
Status: RESOLVED WORKSFORME
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.3   Edit
Assignee: Diego Sahagun CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-19 10:46 EST by Gary Ng CLA
Modified: 2011-04-15 10:18 EDT (History)
3 users (show)

See Also:

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 Gary Ng CLA 2011-01-19 10:46:54 EST 
Build Identifier: 20100617-1415

When in Java perspective, Ctrl-Shift-B on an editor adds a breakpoint.  This is good. 
When in J2EE perspective, Ctrl-Shift-B does nothing.  Nossing!  Very difficult for visually impaired developers who rely on hotkey support.

Reproducible: Always

Steps to Reproduce:
1.  Open any java source code in an editor
2.  Switch to J2EE perspective
3.  Hit ctrl-shift-B.  No breakpoint is added!
Comment 1 Carl Anderson CLA 2011-01-20 09:56:39 EST 
Gary,

Judging by your Build Identifier, you are using Eclipse 3.6, which corresponds to WTP 3.2.  Is that correct?  And if so, can you please try Helios SR1/Eclipse 3.6.1/WTP 3.2.2?  I just tried this in WTP 3.2.2, and Ctrl+Shift+B set a breakpoint in the Java EE perspective.
Comment 2 Gary Ng CLA 2011-01-20 10:24:47 EST 
Hello Carl,

I am actually using Helios.  According to the "About Eclipse Features", the "Eclipse Web Developer Tool" feature is 3.2.0.v201005241510.

I'll download 3.2.2 and give it a shot.
Comment 3 Carl Anderson CLA 2011-04-15 10:18:47 EDT 
Gary, we really need feedback on this issue.  As I said, it WORKSFORME.  If you can give us a reproducible scenario, please reopen this bug.