Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <8002075.1182847945994.JavaMail.jira@brutus>
Date: Tue, 26 Jun 2007 01:52:25 -0700 (PDT)
From: "Lahiru Sandakith (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Commented: (AXIS2-2072) Code generator Eclipse plug-in not
 working when building from source
In-Reply-To: <10847593.1170340207013.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AXIS2-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508111 ] 

Lahiru Sandakith commented on AXIS2-2072:
-----------------------------------------

Axis2 is not mean to support rpc/encoded wsdl types for codegen. It has this listed under the Know Limitations 
No support yet for rpc/encoded style WSDL documents (in stub generation). 


> Code generator Eclipse plug-in not working when building from source
> --------------------------------------------------------------------
>
>                 Key: AXIS2-2072
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2072
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: codegen
>    Affects Versions: 1.1.1
>         Environment: Windows XP, Eclipse 3.2.1, JDK 1.4.2
>            Reporter: Stuart Bell
>            Assignee: Lahiru Sandakith
>         Attachments: .log, Axis2_Codegen_Wizard_1.2.1.zip, create-project.xml, HelloServer.wsdl, screenshot-1.jpg
>
>
> Attempted to follow the installation instructions here:  http://ws.apache.org/axis2/tools/1_1/eclipse/wsdl2java-plugin.html
> I've never had such a difficult experience with other Eclipse plug-ins.  I've had to go down the route of building the plug-in from the source.  The create-project.xml for codegen seems to be broken as it is attempting to reference an axis2-1.1.1.jar which no longer exists.  It seems that the Axis libraries have been broken up into multiple JARs.  This seems to have happened changed with retrospectively updating the build script.
> Also, the installation guide for the plugin is very obscure.  I am aware of Maven, but I have never used it.  Do I really have to spend days figuring out Maven just to re-build a plugin??
> Was the plugin never developed to be just dropped into the plugins directory in Eclipse?
> Regards,
> Stuart Bell

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org