facebook

web project cannot be deployed [Closed]

  1. MyEclipse Archived
  2.  > 
  3. Bugs
Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #210599 Reply

    THEN
    Member

    What operating system and version are you running?
    Windows XP

    What Eclipse version and build id are you using?
    V3.0.0, 00406251208

    Was Eclipse freshly installed for MyEclipse?
    no (but does not make differences, as my colleague has the same problems)

    If not, was it upgraded to its current version using the update manager?
    no (by uninstalling, starting/stopping eclipse, installing again)
    Are any other external plugins installed? org.vssplugin_1.6.0
    How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.*
    7

    What MyEclipse version are you using?
    3.7.200, 200407091200-3.8-Beta2

    What JDK version are you using to run Eclipse?
    j2sdk1.4.2_04

    What JDK version are you using to launch your application server?
    jdk141_05

    What steps did you take that resulted in the issue?
    I tried to deploy a web project to Bea Weblogic V8.1 (which worked with Beta1 of MyEclipse with no problems)

    What application server are you using?
    Bea Weblogic V8.1

    The error occures when I try to deploy my webproject (containing html, xml, js, .war-File (with servlets))

    I got following error messages:

    after first deploy (2 different cases):
    ——————————————

    case 1)
    – no entry in log file
    – dialog box containing no text
    – a corrupt .war file in the applications directory of the AppServer

    case 2)
    – no error dialog
    – no war file is generated
    – following
    !ENTRY com.genuitec.eclipse.ast.deploy.core 1 1 Jul 22, 2004 14:04:07.13
    !MESSAGE Build Exception
    !STACK 0
    java.lang.IllegalArgumentException:
    at org.eclipse.core.internal.runtime.Assert.isLegal(Assert.java:58)
    at org.eclipse.core.internal.runtime.Assert.isLegal(Assert.java:42)
    at org.eclipse.core.runtime.Status.setMessage(Status.java:174)
    at org.eclipse.core.runtime.Status.<init>(Status.java:81)
    at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer$1.run(Unknown Source)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1673)
    at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1693)
    at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer.privExportWebProject(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.ant.J2EEArchiveDeployer.exportWebProject(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.DeploymentPackager.exportWebProject(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.WebDeployment.deployAsPackageArchive(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.ui.wizard.NewDeploymentWizard$2.run(Unknown Source)
    at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)

    after redeploying a little different:
    —————————————-
    – no error diallog
    – Message, that project should be deployed manually or successfully deployed
    – following error log entry:

    !ENTRY org.eclipse.ui 4 0 Jul 22, 2004 14:24:24.103
    !MESSAGE java.lang.ClassCastException
    !STACK 0
    java.lang.ClassCastException
    at com.genuitec.eclipse.ast.deploy.core.DeploymentPackager.exportWebProject(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.WebDeployment.deployAsPackageArchive(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.Deployment.deploy(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.Deployment.redeploy(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog.Ä…(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog.access$2(Unknown Source)
    at com.genuitec.eclipse.ast.deploy.core.ui.dialog.DeploymentManagerDialog$5.handleEvent(Unknown Source)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2772)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2431)
    at org.eclipse.jface.window.Window.runEventLoop(Window.java:668)
    at org.eclipse.jface.window.Window.open(Window.java:648)
    at com.genuitec.eclipse.ast.deploy.core.ui.action.DeploymentMgmtActionDelegate.runWithEvent(Unknown Source)
    at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:266)
    at org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPluginAction.java:206)
    at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:915)
    at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:866)
    at org.eclipse.jface.action.ActionContributionItem$8.handleEvent(ActionContributionItem.java:824)
    at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82)
    at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:796)
    at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2772)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2431)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1377)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1348)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:254)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:141)
    at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:96)
    at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:335)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:273)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:183)
    at org.eclipse.core.launcher.Main.run(Main.java:644)
    at org.eclipse.core.launcher.Main.main(Main.java:628)

    Deploying the same project to Bea V61 works.

    #210603 Reply

    Riyad Kalla
    Member

    I believe this is the same bug we are tracking in 2 other threads that is related to one of the projects being deployed, has no JAR files in its WEB-INF/lib directory. Is this the case with any of your web applications? If it is, this bug will be fixed in the next release, if not, we can move from there.

    #210771 Reply

    THEN
    Member

    Thanks for the fast answer. I just tried it with a dummy jar file (that means a file that I do not use in the programs) – it had no effect. But perhaps a used jar file is needed to work around the error.

    I got no error message, but the generated war file was corrupt. I cannot definitely say, if it is the same bug as in the other threads – I just hope so.

    Now I am looking forward to the release version –> I hope this bug leaves us as suddenly as it came. 🙂

    Thomas

    #210785 Reply

    Riyad Kalla
    Member

    What happens when you use an exploded deployment, does that work fine?

    #212702 Reply

    THEN
    Member

    Sorry for not answering your message, but I have been out of office for 3 weeks.
    Now, I will try the release version and look if the problem has been distinguished.

    Thanks

    Thomas

    #212720 Reply

    Riyad Kalla
    Member

    Thomas,
    You may run into a handful of other bugs, but we hope to have those fixed in a release by weeks end. So hang tight.

    #213155 Reply

    THEN
    Member

    Hi,

    Tank you for the tip!

    Now, I am testing with version 3.8.2. When I use exploded deployment everything works fine,
    with packaged deployment I have the same problems as with Beta2.

    Perhaps I have some useful information (I really don’t know):
    My colleague made a workspace/project from base and everything works fine.
    I imported a workspace pref file including appserver (WL8) settings and a lot of other common preferences.
    Is it possible that that can have something to do with my problem?

    Thomas

    #213207 Reply

    THEN
    Member

    I think I found something.

    First: of course I am testing with 3.8.1

    I created a new workspace, imported my project. And look –> deployment worked!
    Then I made some changes to the preferences (I changed several settings, I cannot remember which),
    perhaps also to the project. And look again –> deployment did not work anymore.

    Then I found out that the size of the .war file increased dramatically (300 %), so I controlled the preferences
    again and saw that the content on page project deployment changed (without changing it myself, at least not directly – I am sure!).
    When I changed the ‘Web Project External Libraries Deployment policy’ to ‘ignore…’ –> deployment was successfully again
    (with the original file size).

    I think the problem occurs when you try to deploy external libraries with the war file.
    (luckily I do not need this feature at the moment)

    thanks,

    Thomas

    #213213 Reply

    Scott Anderson
    Participant

    Thomas,

    The problem might simply be that when you chose to deploy external libraries that these overwrote / conflicted with some that the server provides at runtime thus giving you an invalid classpath configuration within your war. The “Deploy external libraries” option is certainly not for every web project. 🙂

    #213222 Reply

    THEN
    Member

    Scott,

    thanks for the quick answer. What I am not sure is why “eclipse/myeclipse suddenly chose to deploy external jar files” :).
    I do not know what I did that this setting changed (I did not change it directly, perhaps it was changed indirectly by changing other properties).
    The only thing I know is that suddenly deployment did not work anymore.
    But now, since I know how to handle this problem, it should be no problem anymore. 🙂

    Thanks for your help!

    Thomas

Viewing 10 posts - 1 through 10 (of 10 total)
Reply To: web project cannot be deployed [Closed]

You must be logged in to post in the forum log in