Hi Michael,

Thanks for the reply,

Michael Galpin wrote:
Ok, I removed all mylyn plugins, even the ones that Eclipse said were required! I created a new workspace and reproduced the same steps:
Strange, but the log clearly said that because of the mylyn plugin the workspace plugin loading inconsistent.

Eclipse => Preferences => Web Services => WSO2: Set the WSAS runtime
New => Other => Web => Dynamic Web Project
For runtime selected new => WSO2 => WSAS and checked also create local server
On Web Project Facets, selected all the WSAS facets
Accepted all other defaults
Clicked the start WSAS button in Eclipse
Eclipse crashes
Yep, these are the exact steps needed, Let me obtain and fresh J2EE version of the eclipse and test in on Vista and get back to you.
Greatly appreciate your feedback on this.

New log file attached to bug (eclipse-wsas.log)
Thanks

Note: I don't think I can add comments to the bug in Jira anymore, or I would put this information there.
This is may because that the issue is closed, let me reopen it and update it with the vista test.

Thanks



-- Michael

On Jan 29, 2008 11:06 PM, Lahiru Sandakith <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    Hi Michel,

    Thanks for the reply, I see a workspace inconsistent issue on your
    environment and eclipse fails to load plugins specially there are
    lots of mylyn issues on your workspace regarding the plugin
    org.eclipse.mylyn.tasks.ui_2.1.0.v20070927-0900.jar on eclipse
    system which cause a workspace inconsistence. As I know mylyn is
    now comes with the eclipse core and its stable not have a
    workspace corruptions issue. Shall we remove the mylyn plugins on
    your system and get the plugins loading consistent on your
    environment. In the mean time I am looking in to a clash between
    mylyn and wsas ide plugins.

    Thanks
    Lahiru Sandakith


    Michael Galpin wrote:
    I tried with the nightly snapshot, but still had the same bug. My
    steps exactly:

    download clean Eclipse JavaEE
    download nightly snapshot of wso2-wsas
    run wsas installer
    installed Eclipse plugin
    launched Eclipse
    Eclipse => Preferences => Web Services => WSO2 => Set WSAS runtime
    New => Other => Web => Dynamic Web Project
    Select new runtime => WSO2 WSAS
    Clicked through accepting all other defaults
    Clicked to server tab, it shows WSO2 WSAS server already running
    Pressed WSAS Start Server Button
    Eclipse crashed

    I have attached the Eclipse log to the bug.

    Please let me know if you need me to do more things.

    -- Michael

    On Jan 24, 2008 7:24 PM, Lahiru Sandakith (JIRA) <[EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>> wrote:

            [ http://wso2.org/jira/browse/WSAS-658?page=all ]

        Lahiru Sandakith resolved WSAS-658.
        -----------------------------------

           Resolution: Fixed

        With https://wso2.org/jira/browse/WSFJAVA-59 also resolved on
        trunk, this issue needed to be resolved,
        Michael can you please try wsas nightly builds and confirm
        http://wso2.org/downloads/wsas/nightly-build/

        > IDE shows WSAS as started when it is not
        > ----------------------------------------
        >
        >                 Key: WSAS-658
        >                 URL: http://wso2.org/jira/browse/WSAS-658
        >             Project: WSO2 WSAS
        >          Issue Type: Bug
        >          Components: wsas-ide
        >    Affects Versions: 2.1
        >         Environment: OSX, Vista
        >            Reporter: Michael Galpin
        >         Assigned To: Lahiru Sandakith
        >         Attachments: screenshots.zip
        >
        >
        > Create a dynamic web project that uses WSAS as its runtime
        > The IDE immediately shows WSAS in the Server view and it
        shows it as started, but it does not start it
        > You cannot start WSAS because the IDE says it is already
        started
        > You cannot deploy to WSAS because it is not started
        (connection refused error)
        > You cannot stop WSAS because it is not started  (connection
        refused error -- sometimes crashes Eclipse)
        > The workaround I found was to manually start WSAS before
        starting the IDE. I think it would be sufficient to start
        WSAS before creating the project. If WSAS was manually
        started, then at least one could deploy to it with no problems.

        --
        This message is automatically generated by JIRA.
        -
        If you think it was sent incorrectly contact one of the
        administrators: http://wso2.org/jira/secure/Administrators.jspa
        -
        For more information on JIRA, see:
        http://www.atlassian.com/software/jira





-- Thanks
    Lahiru Sandakith

http://www.wso2.org GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F


--
Thanks
Lahiru Sandakith

http://www.wso2.org GPG Key Fingerprint : 8CD8 68E0 4CBC 75CB 25BC 1AB1 FE5E 7464 1F01 9A0F
_______________________________________________
Wsas-java-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/wsas-java-dev

Reply via email to