You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

myeclipseide.adoc 2.8KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657
  1. = MyEclipseIde
  2. _Last updated: 2003-07-08 by wisberg_
  3. MyEclipseIde (https://www.myeclipseide.com/[https://www.myeclipseide.com])
  4. aims to make it easy to develop J2EE applications using Eclipse. AJDT
  5. (https://eclipse.org/ajdt) is an Eclipse plug-in that supports AspectJ.
  6. == Getting started
  7. * To install AJDT with MyEclipseIDE, direct the Eclipse update manager
  8. to https://download.eclipse.org/technology/ajdt/dev/update, install the
  9. plug-in, and follow any post-install instructions.
  10. * To enable a project to use aspects, first select
  11. `Convert to AspectJ project` from the project's context menu (select
  12. project, right click). (XXX Bug: AJDT reverts perspective to Java; go
  13. back to MyEclipseIDE) Note that you must convert each project;
  14. converting the master J2EE project will not affect the child components
  15. (XXX RFE: option to convert child if parent).
  16. * To build, select the menu item `Project > Rebuild Project`. AJDT
  17. creates `default.lst` which lists all source files and compiles them.
  18. You can also recompile by clicking the AJDT build button. (XXX Bug: only
  19. available in the Java perspective)
  20. * To deploy, first add `aspectjrt.jar` to the project's library
  21. directory. For servlets and JSP's, that is in `{Web Root}/WEB-INF/lib`.
  22. For EJB's, it's XXX todo. Then deploy as usual for your application
  23. server.
  24. * If you are using AspectJ in more than one project, you might instead
  25. deploy `aspectjrt.jar` whereever shared libraries belong for your
  26. server.
  27. == Bugs in MyEclipseIDE
  28. . After refactoring to rename a servlet, have to manually update web.xml
  29. . Silent failure when unable to delete a duplicate resource during
  30. deployment.
  31. . Annoyingly modal UI for deployment. Use a view.
  32. . Need validation on saving Web.xml. E.g., servlet mapping names
  33. validated with declared servlet names.
  34. . Deployment dirty flag not working; not updated after editing web.xml
  35. or rebuilding project.
  36. . Apparantly false JSP error? using Sun page and template page, got:
  37. "Fatal error - The markup in the document preceding the root element
  38. must be well-formed." Error persisted even after replacing the entire
  39. contents of the file with the template which worked by default.
  40. . When using the exact template page, get no MyEclipseIDE error, but do
  41. get compile errors in Tomcat. Using Javac, get compile-failed stack
  42. trace with initial line number. Using ajc, just get stack trace. But
  43. precompiling using Ant seems to work.
  44. . Precompiling JSP's:
  45. * MyEclipseIDE has a command to compile all JSP's, but I don't see
  46. (where or how) the updated servlet mappings get into the deployed
  47. web.xml. It would be great to get this working with AJDT.
  48. * I adapted the Tomcat precompile script to use AspectJ's iajc. This
  49. works fine, but like all Jasper2 solutions required the generated
  50. servlet mappings be copied manually into the web.xml file. See
  51. xref:../scripts/precompile-jsp.build.xml[the Ant build script].