axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stuart Bell (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AXIS2-2072) Code generator Eclipse plug-in not working when building from source
Date Tue, 10 Apr 2007 09:26:33 GMT

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

Stuart Bell updated AXIS2-2072:
-------------------------------

    Attachment: screenshot-1.jpg

Lahiru,

I downloaded the updated version of the codegen plugin and I managed to gain access to the
wizard screens at last.  However, once I had put in my wsdl location, I received the attached
screenshot when I attempted to generate a WSDL to Java.  I selected all the default settings
and an example WSDL (which I will also attach).  Are there any restrictions to using encoding
in a WSDL at all?  Do you know what could cause this error?

Thanks,

Stuart

> 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
>         Assigned To: Lahiru Sandakith
>         Attachments: .log, Axis2_Codegen_Wizard_1.2.1.zip, create-project.xml, 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


Mime
View raw message