For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 3 replies, 2 voices, and was last updated 17 years, 1 month ago by
support-shalini.
-
AuthorPosts
-
Arvato-9MemberHello everyone,
I’ve got a problem with myEclipse 7.5, that’s ignoring breakpoints when I’m trying to test my code. In static methods it works fine but after some beans are instantiated by Spring’s (2.5) it doesn’t react on breakpoints anymore.
I’ve also tried out different myEclipse versions. The same problem occurs on my collegues computers. I’m using Java JDK 1.6.0_14 on Windows XP.
Best regards
Stefan
July 6, 2009 at 11:56 pm #300205
support-shaliniMemberStefan,
Can you give some more information on this?
1. Can you copy paste your installation details here? You can get them from MyEclipse > Installation Summary > Installation Details.
2. What is project that you are working on? What are the technologies that you are using?
3. Are there any errors logged in the problems window?
4. Can you list out the steps to reproduce in detail? Also, Can you give us some code snippets so that we can try to replicate your issue.July 7, 2009 at 3:45 am #300211
Arvato-9MemberHello, I hope this information helps you to reproduce the problem…
___4___ Steps, Code
I’ve writte a JUnit4 test class having the methods listed below.
It reacts on breakpoints correctly and opens the debug perspective if I place a breakpoint in line 16.
But after the ApplicationContext is built (line 18) all breakpoints are being ignored (line 20 ff.)/**
* @throws Exception
*/
@BeforeClass
10 public static void runOnceBeforeTests() throws Exception {try {
…16 logger.debug(“breakpoint 1”);
18 ctx = getContext();
20 Object inventoryImplBean = ctx.getBean(InventoryManagementImpl.SPRING_BEAN_ID);
21
22 inventoryMgr = (InventoryManagementI)inventoryImplBean;} catch (Exception e){
e.printStackTrace();
throw e;
}
}@Test
public void getCustomerById() {try{
100 String customerNo = “12345”
101 String shopNo = “10”;
102 List<CustomerDTO> customerList = customerMgr.getCustomerById(ctx, customerNo );
}
catch (Exception e) {
e.printStackTrace();
fail(e.getMessage());
}___3___ Errors
There are no errors logged in the problems window. Just a few ordinary warning outputs.
___2___ Project & Technologies
The project is a Java based backend system providing remote services. I’m using the SpringFramework (ver 2.5) and JUnit4.
___1___ Installation Details:
*** Date:
Dienstag, 7. Juli 2009 12:39 Uhr MESZ** System properties:
OS=WindowsXP
OS version=5.1.0
Java version=1.6.0_13*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 7.5
Build id: 7.5-20090609*** Eclipse details:
MyEclipse Enterprise WorkbenchVersion: 7.5
Build id: 7.5-20090609Eclipse Plug-in Development Environment
Version: 3.4.2.R342_v20090122-7T7U1E9imVKz-A8Vz-p_jRS
Build id: M20080703-0800Eclipse Platform
Version: 3.4.2.R342_v20090122-9I96EiWElHi8lheoJKJIvhM3JfVsYbRrgVIWL
Build id: M20090211-1700Eclipse Graphical Editing Framework GEF
Version: 3.4.2.v20090218-1145-67728084A56B4I233613552
Build id: 200809101400Eclipse RCP
Version: 3.4.200.R342_v20090122-989JESTEbig-SVaL8UJHcYBr4A63
Build id: M20090211-1700Eclipse Java Development Tools
Version: 3.4.2.r342_v20081217-7o7tEAoEEDWEm5HTrKn-svO4BbDI
Build id: M20090211-1700Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
D:\Programme\MyEclipse 7.5\myeclipse.exe
-name
Myeclipse
–launcher.library
D:\Programme\MyEclipse 7.5\Common\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.dll
-startup
D:\Programme\MyEclipse 7.5\Common\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar
-clean
-configuration
configuration
-vm
D:\Programme\MyEclipse 7.5\Common\binary\com.sun.java.jdk.win32.x86_1.6.0.013\jre\bin\client\jvm.dllJuly 8, 2009 at 10:54 pm #300282
support-shaliniMemberStefan,
Is is possible for you to share your project?
You can send a mail to support@genuitec.com. Please add ATTN: Shalini in the subject and refer to this thread. This will help us reproduce this issue internally and quickly work on resolution. Thanks for your help -
AuthorPosts
