Community
Participate
Working Groups
Created attachment 119604 [details] build log am not sure if this is the right component if not please redirect. Trying to deploy on glassfish J2ee 1.4 or 5.0 projects using the J2ee Smoke test and the deploy fails with errors in build log and the server log. See attached documents.
Created attachment 119605 [details] server log
there were no errors in eclipse error log
Sending over to the Rochelle for further investigation, this might not be a WTP failure but rather an adopter failure. I am keeping in the WTP for now to ensure that it is not a problem in generic server adapter framework.
Which version of glassfish? Which version of the glassfish plugin? Can you include a link to the smoke test project for me?
seems like a corrupted manifest in the archives, but I'm not sure where the sources are...
Hi, it was latest glassfish v2. I have downloaded the server adapter using the install runtime option. here is the smoketes results: http://wiki.eclipse.org/WTP_Smoke_Test_Results_R31_120408 this is the scenario: http://wiki.eclipse.org/J2EE_Smoke_Test_(WTP_3.0)
Created attachment 120012 [details] binary1 J2ee 1.4
Created attachment 120013 [details] ear 5.0 here are the ears produced, I still haven't tested it on windows though.
I was able to deploy both ears (via the admin console) to my V2 installation, so the ears seem to be okay. Perhaps you can give me your eclipse projects? Maybe those have the problem.
Created attachment 120157 [details] projects hope that this will help.
Can you tell me which update site to use to get the xdoclet support? It is not in any of the preconfigured ones.
http://sourceforge.net/project/showfiles.php?group_id=31602 version 1.2.3
Thanks. I tried with that and it works for me. Can you: 1) Tell me the path to your project? The log makes it sound like the url might be too long - maybe the problem is your path? I put mine directly on my desktop, so that might account for the difference. 2) Attach the contents of your manifest file for the project which is failing? Perhaps I can diff that to mine and we can see what is wrong there.
I am using OSX 10.5.5 and there should not be a problem with the length, but I have suspected that and put both the server and the workspace in my home folder, but the error remains so the project is in: /Users/gormov/workspace/dynweb5 the server is in /Users/gormov/glassfish I will attach the manifest. Yesterday I think I saw some bug related to the manifest and linux based pc's but I could not find it today.
Created attachment 120561 [details] manifest file
Which manifest is this? I think it's ear14.ear's. If so, mine has no Class-Path: entry where yours has an empty one. I believe that is the problem. Can you check if that is the problem, then if that is possibly a result of wrong project/javaee dependencies in the project?
Dimitar, have you had a chance to check the Class-Path contents in the manifest and see if that is the problem?
Dimitar, I have not heard back from you on whether your manifest is corrupted in the way I suspect. Since it has been about a month, I will close this bug now and assume that is indeed the problem. If you find otherwise, please reopen it with the additional info.
hi sorry about the huge delay. I was on vacation and now I had some time to try some things. So what I have additionally tried is to test with 3.0.4 and the same server result: everything works ok I have installed the server in the root of the OS X and placed the IDE in the root also so character length should be out of the way the results were the same.
it looks like this is the reason https://bugs.eclipse.org/bugs/show_bug.cgi?id=261243 I will put the bug as depends on
Thanks for the additional info, Dimitar. Should this bug still remain open and assigned to me? Or should it be transferred to the owner of the other bug and then transferred back to me if needed once the other bug is fixed?
I haven't been following this defect closely, but unless there is a way to confirm that the problem is indeed due to 261243, it should remain open and assigned to you. But so far it sounds to me that we can't get to deploy part until 261243 is fixed.
I agree with Angel if the issue is gone once the depending bug is fixed we can close this issue as well.
Reproduced under gentoo linux. Mark OS as All
Having fixed the depending problem. I am confident that the changes will apply to this bug, and the problem is indeed caused by the same bug. Thus, I am removing the depends on, and marking as dup of 261243. *** This bug has been marked as a duplicate of bug 261243 ***
