Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How the internals is working by which class the plugin is started #244

Closed
gdeverlant opened this issue May 11, 2019 · 5 comments

Comments

Projects
None yet
2 participants
@gdeverlant
Copy link
Contributor

commented May 11, 2019

I'm submitting a ... (check one with "x")

[ ] bug report
[ ] feature request
[x ] question
  1. I would like to know which class should I put a breakpoint in to debug DE? I would like to know which class is first instanciated by spring when Alfresco is starting and registering this plugin.
  2. Is there a way to debug DE inside of Eclipse IDE while running Tomcat in Debug mode?
  3. How to setup my eclipse environment to debug this AMP in Tomcat and contribute to it?
@gdeverlant

This comment has been minimized.

Copy link
Contributor Author

commented May 11, 2019

I was able to come up to this debug phase but somehow it is not possible to get eclipse recognize the DefaultFrameworkManager.java class from the FameworkManager.kt file.

image

Why am I able to debug OsgiContainerModuleComponent and not DefaultFrameworkManager?

image

@gdeverlant

This comment has been minimized.

Copy link
Contributor Author

commented May 13, 2019

After installing the 2.0.0 version of DE it seems that there is nothing related with Kotlin anymore. The standard class debugging is working like a charm now. I really don't understand why that DefaultFrameworkManager.kt file appeared from nowhere.

image

@kerkhofsd

This comment has been minimized.

Copy link
Member

commented May 13, 2019

Hi @gdeverlant ,
FYI: In the current master, DE version 2.0.0, we converted all Kotlin classes to Java to simplify the project.

Do you have all the information you need?

@gdeverlant

This comment has been minimized.

Copy link
Contributor Author

commented May 13, 2019

I would say that this is the best move that you guys did! Removing the Kotlin related stuff helped a lot for me to debug step by step all the internal code so that I can understand it.

Kudos !!!!

@kerkhofsd

This comment has been minimized.

Copy link
Member

commented May 13, 2019

Thanks, great to hear!

@kerkhofsd kerkhofsd closed this May 13, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.