For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 23 replies, 6 voices, and was last updated 21 years, 7 months ago by
.
-
Posts
-
Create one EJB project with a single class, no need to add fields or methods, just make sure it’s in some non-default package.
Ok
Create a second web project with no sources, but a single jsp page. Add first project as a dependency. At the top of the jsp page, import the package in which the first project’s class belongs. Any errors?
Yes, “Package does not exist….”
Now change the build path, add the classes directory from the first project. Does the web project rebuild?
No
If not, perform a manual rebuild.
Ok, errors are gone.
Now double check the deployment policy, make sure dependencies are set to deploy. Now deploy. Did the class from the first project get deployed?
No, however deployment policies only apply to Java Projects and external libraries… neither of which the EJB project is.
Armen,
I thank you for the walkthrough and will discuss the class resolution problem with the team ASAP.Armen,
Yes I am running 3.8.1, and now with the quickfix. To summarize, here are my findings for web apps:
(1) Classes in dependent EJB projects are not visible to jsp pages.
(2) No rebuild occurs if java build path is modified.
(3) On manual clean/rebuild, package view only displays build errors in the first jsp page that (incorrectly) fails, all others appear as if they have no build problems.
(4) If you use the workaround mentioned in this threadThis is a bug that will be fixed shortly in the next QuickFix. It sounds like you already have a workaround until then. Thank you very much for providing the reproducible case for us to run this down.
Thanks you guys, I appreciate it. And now I remember going over the fact that dependent EJB projects don’t get deployed, it’s because there are no standards set on what and how it is done, right? I had completely forgotten about that. 😳
And now I remember going over the fact that dependent EJB projects don’t get deployed, it’s because there are no standards set on what and how it is done, right?
Yes, exactly. Although its not completely out of the picture, in the future we may address this with some ‘smart defaults’ or something, but for now its not.
I am using a mac and have run the update to 3.8.1 but have no idea how to specify the -clean option to eclipse. At the moment it looks as though MyEclipse is not installed !!!
The -clean option is added to the command line when running eclipse, something like:
/opt/eclipse/eclipse -clean -vmargs <optional memory args>I’m not farmiliar with mac, but if you have a shortcut of sorts for Eclipse, can you edit it and add that argument and then restart Eclipse using the shortcut?
On the mac, there is an Eclipse.app directory that contains the launch script. You’ll need to edit it with the commandline tools because IIRC it’s an XML file that handles the commandline launch parameters.
