You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Nan Null <nu...@gmail.com> on 2010/03/01 20:14:18 UTC
Axis 1.5.1 Issues
I had a bad day with Axis. Usually, Apache projects are very high
quality and I don't encounter issues like these. I hope that the
developers listens and fix it accordingly.
So, let's go to the issue.
1) Building version 1.5.1 doesn't work.
It gave me some weird maven area about missing/invalid Java class.
This turns out to be Axis's issue. The build (pom.xml) file points to
a wrong/obsolete URL. There is a tracker for this. However, it
wasn't easy to find it.
https://issues.apache.org/jira/browse/AXIS2-4549
I am not sure because of my familiarity, but I think it's due to
Maven. I know Maven is great, but this kind of Internet dependency is
really a limitation. For example, the site can be down, and you can't
build. There are so many sites, so this definitely increases the
possibility. It's not as easy as download, and build.
Probably there should be a off line build download for Axis?
2) The svn repository doesn't exist.
What's the point of open source, if the real time source is not
available? At least the website doesn't point to the correct
location:
At the bottom of the page: http://ws.apache.org/axis2/, there is a link:
http://svn.apache.org/viewvc/webservices/axis2/trunk/?root=Apache-SVN
Going there, I don't see any source. Empty directory.
3) extraClasses flag for Java2WSDLTask is not working at all in ant
4) The above flag, even after fixing ant (that is ant would accept the
attribute), it doesn't work at all for generating code.
5) The Java2WSDL flag "-p2n" doesn't work. This is the Java
executable, not the ant task. However, the ant task does work (using
the mapping sub tag).
6) The generated code has some weird code like this:
if (value == null) {
localValueTracker = true;
} else {
localValueTracker = true;
}
This happens to many field setters, not just one or two.
For those saying design should be by contract, and Java2WSDL should be
used. This is a different argument, but I would like to say that with
annotation, web services goes from a method any way. Further more, if
the WSDL are produced correctly, consistently, and in standard
conformation way, it should not be any difference.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
RE: Axis 1.5.1 Issues
Posted by Jonathan Roberts <jr...@rjlg.com>.
This project is epic.
-----Original Message-----
From: Nan Null [mailto:null.nan@gmail.com]
Sent: Monday, March 01, 2010 2:14 PM
To: axis-user@ws.apache.org
Subject: Axis 1.5.1 Issues
I had a bad day with Axis. Usually, Apache projects are very high
quality and I don't encounter issues like these. I hope that the
developers listens and fix it accordingly.
So, let's go to the issue.
1) Building version 1.5.1 doesn't work.
It gave me some weird maven area about missing/invalid Java class.
This turns out to be Axis's issue. The build (pom.xml) file points to
a wrong/obsolete URL. There is a tracker for this. However, it
wasn't easy to find it.
https://issues.apache.org/jira/browse/AXIS2-4549
I am not sure because of my familiarity, but I think it's due to
Maven. I know Maven is great, but this kind of Internet dependency is
really a limitation. For example, the site can be down, and you can't
build. There are so many sites, so this definitely increases the
possibility. It's not as easy as download, and build.
Probably there should be a off line build download for Axis?
2) The svn repository doesn't exist.
What's the point of open source, if the real time source is not
available? At least the website doesn't point to the correct
location:
At the bottom of the page: http://ws.apache.org/axis2/, there is a
link:
http://svn.apache.org/viewvc/webservices/axis2/trunk/?root=Apache-SVN
Going there, I don't see any source. Empty directory.
3) extraClasses flag for Java2WSDLTask is not working at all in ant
4) The above flag, even after fixing ant (that is ant would accept the
attribute), it doesn't work at all for generating code.
5) The Java2WSDL flag "-p2n" doesn't work. This is the Java
executable, not the ant task. However, the ant task does work (using
the mapping sub tag).
6) The generated code has some weird code like this:
if (value == null) {
localValueTracker = true;
} else {
localValueTracker = true;
}
This happens to many field setters, not just one or two.
For those saying design should be by contract, and Java2WSDL should be
used. This is a different argument, but I would like to say that with
annotation, web services goes from a method any way. Further more, if
the WSDL are produced correctly, consistently, and in standard
conformation way, it should not be any difference.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Re: Axis 1.5.1 Issues
Posted by Nan Null <nu...@gmail.com>.
Andreas,
I just created a new issue for this here:
https://issues.apache.org/jira/browse/AXIS2-4660
-Vy
On Sun, Mar 14, 2010 at 12:13 PM, Nan Null <nu...@gmail.com> wrote:
> Andreas,
>
> Yes, I will. Hopefully when I have time, I would create some
> documentation for this tool.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Re: Axis 1.5.1 Issues
Posted by Nan Null <nu...@gmail.com>.
Andreas,
Yes, I will. Hopefully when I have time, I would create some
documentation for this tool.
Regards,
Vy
On Sun, Mar 14, 2010 at 7:49 AM, Andreas Veithen
<an...@gmail.com> wrote:
> Vy,
>
> This actually works, but the mappings need to be enclosed in brackets
> as in the following example:
>
> <java classname="org.apache.ws.java2wsdl.Java2WSDL"
> classpathref="maven.test.classpath" fork="true" failonerror="true">
> <arg value="-o"/>
> <arg value="${project.build.directory}/java2wsdl"/>
> <arg value="-of"/>
> <arg value="p2n.wsdl"/>
> <arg value="-cn"/>
> <arg value="org.apache.axis2.description.CalculatorService"/>
> <arg value="-p2n"/>
> <arg value="[org.apache.axis2.description,http://www.example.org/calculator]"/>
> <arg value="-stn"/>
> <arg value="http://www.example.org/calculator-service"/>
> </java>
>
> Obviously, java2wsdl should complain when the syntax is incorrect, but
> it fails to do so. Can you open a JIRA issue for that?
>
> Andreas
>
> On Sun, Mar 14, 2010 at 03:35, Nan Null <nu...@gmail.com> wrote:
>> Hi Andreas,
>>
>> Please see my comment below.
>>
>>
>>> Where does Axis2 use the incorrect namespace? In the output of
>>> Java2WSDL, in the WSDL exposed at runtime (through the "...?wsdl" URL)
>>> or in responses received from the service?
>>
>> This happens when I run Java2WSDL using ant java task (running the
>> main class). Basically, the main method is called with parameters
>> passing in almost like running it from a command line classical Java
>> application.
>>
>> Regards,
>>
>> Vy
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-user-help@axis.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Re: Axis 1.5.1 Issues
Posted by Andreas Veithen <an...@gmail.com>.
Vy,
This actually works, but the mappings need to be enclosed in brackets
as in the following example:
<java classname="org.apache.ws.java2wsdl.Java2WSDL"
classpathref="maven.test.classpath" fork="true" failonerror="true">
<arg value="-o"/>
<arg value="${project.build.directory}/java2wsdl"/>
<arg value="-of"/>
<arg value="p2n.wsdl"/>
<arg value="-cn"/>
<arg value="org.apache.axis2.description.CalculatorService"/>
<arg value="-p2n"/>
<arg value="[org.apache.axis2.description,http://www.example.org/calculator]"/>
<arg value="-stn"/>
<arg value="http://www.example.org/calculator-service"/>
</java>
Obviously, java2wsdl should complain when the syntax is incorrect, but
it fails to do so. Can you open a JIRA issue for that?
Andreas
On Sun, Mar 14, 2010 at 03:35, Nan Null <nu...@gmail.com> wrote:
> Hi Andreas,
>
> Please see my comment below.
>
>
>> Where does Axis2 use the incorrect namespace? In the output of
>> Java2WSDL, in the WSDL exposed at runtime (through the "...?wsdl" URL)
>> or in responses received from the service?
>
> This happens when I run Java2WSDL using ant java task (running the
> main class). Basically, the main method is called with parameters
> passing in almost like running it from a command line classical Java
> application.
>
> Regards,
>
> Vy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Re: Axis 1.5.1 Issues
Posted by Nan Null <nu...@gmail.com>.
Hi Andreas,
Please see my comment below.
> Where does Axis2 use the incorrect namespace? In the output of
> Java2WSDL, in the WSDL exposed at runtime (through the "...?wsdl" URL)
> or in responses received from the service?
This happens when I run Java2WSDL using ant java task (running the
main class). Basically, the main method is called with parameters
passing in almost like running it from a command line classical Java
application.
Regards,
Vy
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Re: Axis 1.5.1 Issues
Posted by Andreas Veithen <an...@gmail.com>.
On Thu, Mar 11, 2010 at 06:13, Nan Null <nu...@gmail.com> wrote:
> Hi,
>
> Please see comment below for #5
>
>>> 5) The Java2WSDL flag "-p2n" doesn't work. This is the Java
>>> executable, not the ant task. However, the ant task does work (using
>>> the mapping sub tag).
>
> Basically, running te Java2WSDL as an application, passing the
> parameter -p2n with the mapping of java package comma typedef name
> space.
> The code would run, but when I check the type def namespace, it is not
> the one from -p2n mapping.
Where does Axis2 use the incorrect namespace? In the output of
Java2WSDL, in the WSDL exposed at runtime (through the "...?wsdl" URL)
or in responses received from the service?
>
> On Mon, Mar 1, 2010 at 5:34 PM, Andreas Veithen
> <an...@gmail.com> wrote:
>> 1) Here java.net is to be blamed. They broke several projects by
>> moving their Maven repository. Apparently they did other bad things
>> like that in the past (such as replacing an already released artifact
>> by a different one), so that e.g. the CXF project has chosen to copy
>> the artifacts they need to another repository and to remove the
>> java.net repository from their POMs. Probably we will end up doing the
>> same. Unfortunately we cannot fix any already released Axis2 version.
>>
>> 2) The Axis projects have been moved out of Apache Web Services and
>> promoted to a top level project. The repository has already been moved
>> [1], but the site has not yet been updated.
>>
>> 3,4,6) See comments in the corresponding JIRA issues.
>>
>> 5) This requires more information.
>>
>> Andreas
>>
>> [1] https://svn.apache.org/repos/asf/axis/axis2/java/
>>
>> On Mon, Mar 1, 2010 at 20:14, Nan Null <nu...@gmail.com> wrote:
>>> I had a bad day with Axis. Usually, Apache projects are very high
>>> quality and I don't encounter issues like these. I hope that the
>>> developers listens and fix it accordingly.
>>>
>>> So, let's go to the issue.
>>>
>>> 1) Building version 1.5.1 doesn't work.
>>>
>>> It gave me some weird maven area about missing/invalid Java class.
>>>
>>> This turns out to be Axis's issue. The build (pom.xml) file points to
>>> a wrong/obsolete URL. There is a tracker for this. However, it
>>> wasn't easy to find it.
>>>
>>> https://issues.apache.org/jira/browse/AXIS2-4549
>>>
>>> I am not sure because of my familiarity, but I think it's due to
>>> Maven. I know Maven is great, but this kind of Internet dependency is
>>> really a limitation. For example, the site can be down, and you can't
>>> build. There are so many sites, so this definitely increases the
>>> possibility. It's not as easy as download, and build.
>>>
>>> Probably there should be a off line build download for Axis?
>>>
>>> 2) The svn repository doesn't exist.
>>>
>>> What's the point of open source, if the real time source is not
>>> available? At least the website doesn't point to the correct
>>> location:
>>>
>>> At the bottom of the page: http://ws.apache.org/axis2/, there is a link:
>>>
>>> http://svn.apache.org/viewvc/webservices/axis2/trunk/?root=Apache-SVN
>>>
>>> Going there, I don't see any source. Empty directory.
>>>
>>> 3) extraClasses flag for Java2WSDLTask is not working at all in ant
>>>
>>> 4) The above flag, even after fixing ant (that is ant would accept the
>>> attribute), it doesn't work at all for generating code.
>>>
>>> 5) The Java2WSDL flag "-p2n" doesn't work. This is the Java
>>> executable, not the ant task. However, the ant task does work (using
>>> the mapping sub tag).
>>>
>>> 6) The generated code has some weird code like this:
>>>
>>> if (value == null) {
>>> localValueTracker = true;
>>> } else {
>>> localValueTracker = true;
>>> }
>>>
>>> This happens to many field setters, not just one or two.
>>>
>>> For those saying design should be by contract, and Java2WSDL should be
>>> used. This is a different argument, but I would like to say that with
>>> annotation, web services goes from a method any way. Further more, if
>>> the WSDL are produced correctly, consistently, and in standard
>>> conformation way, it should not be any difference.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>>> For additional commands, e-mail: java-user-help@axis.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-user-help@axis.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Re: Axis 1.5.1 Issues
Posted by Nan Null <nu...@gmail.com>.
Hi,
Please see comment below for #5
>> 5) The Java2WSDL flag "-p2n" doesn't work. This is the Java
>> executable, not the ant task. However, the ant task does work (using
>> the mapping sub tag).
Basically, running te Java2WSDL as an application, passing the
parameter -p2n with the mapping of java package comma typedef name
space.
The code would run, but when I check the type def namespace, it is not
the one from -p2n mapping.
On Mon, Mar 1, 2010 at 5:34 PM, Andreas Veithen
<an...@gmail.com> wrote:
> 1) Here java.net is to be blamed. They broke several projects by
> moving their Maven repository. Apparently they did other bad things
> like that in the past (such as replacing an already released artifact
> by a different one), so that e.g. the CXF project has chosen to copy
> the artifacts they need to another repository and to remove the
> java.net repository from their POMs. Probably we will end up doing the
> same. Unfortunately we cannot fix any already released Axis2 version.
>
> 2) The Axis projects have been moved out of Apache Web Services and
> promoted to a top level project. The repository has already been moved
> [1], but the site has not yet been updated.
>
> 3,4,6) See comments in the corresponding JIRA issues.
>
> 5) This requires more information.
>
> Andreas
>
> [1] https://svn.apache.org/repos/asf/axis/axis2/java/
>
> On Mon, Mar 1, 2010 at 20:14, Nan Null <nu...@gmail.com> wrote:
>> I had a bad day with Axis. Usually, Apache projects are very high
>> quality and I don't encounter issues like these. I hope that the
>> developers listens and fix it accordingly.
>>
>> So, let's go to the issue.
>>
>> 1) Building version 1.5.1 doesn't work.
>>
>> It gave me some weird maven area about missing/invalid Java class.
>>
>> This turns out to be Axis's issue. The build (pom.xml) file points to
>> a wrong/obsolete URL. There is a tracker for this. However, it
>> wasn't easy to find it.
>>
>> https://issues.apache.org/jira/browse/AXIS2-4549
>>
>> I am not sure because of my familiarity, but I think it's due to
>> Maven. I know Maven is great, but this kind of Internet dependency is
>> really a limitation. For example, the site can be down, and you can't
>> build. There are so many sites, so this definitely increases the
>> possibility. It's not as easy as download, and build.
>>
>> Probably there should be a off line build download for Axis?
>>
>> 2) The svn repository doesn't exist.
>>
>> What's the point of open source, if the real time source is not
>> available? At least the website doesn't point to the correct
>> location:
>>
>> At the bottom of the page: http://ws.apache.org/axis2/, there is a link:
>>
>> http://svn.apache.org/viewvc/webservices/axis2/trunk/?root=Apache-SVN
>>
>> Going there, I don't see any source. Empty directory.
>>
>> 3) extraClasses flag for Java2WSDLTask is not working at all in ant
>>
>> 4) The above flag, even after fixing ant (that is ant would accept the
>> attribute), it doesn't work at all for generating code.
>>
>> 5) The Java2WSDL flag "-p2n" doesn't work. This is the Java
>> executable, not the ant task. However, the ant task does work (using
>> the mapping sub tag).
>>
>> 6) The generated code has some weird code like this:
>>
>> if (value == null) {
>> localValueTracker = true;
>> } else {
>> localValueTracker = true;
>> }
>>
>> This happens to many field setters, not just one or two.
>>
>> For those saying design should be by contract, and Java2WSDL should be
>> used. This is a different argument, but I would like to say that with
>> annotation, web services goes from a method any way. Further more, if
>> the WSDL are produced correctly, consistently, and in standard
>> conformation way, it should not be any difference.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
>> For additional commands, e-mail: java-user-help@axis.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Re: Axis 1.5.1 Issues
Posted by Andreas Veithen <an...@gmail.com>.
1) Here java.net is to be blamed. They broke several projects by
moving their Maven repository. Apparently they did other bad things
like that in the past (such as replacing an already released artifact
by a different one), so that e.g. the CXF project has chosen to copy
the artifacts they need to another repository and to remove the
java.net repository from their POMs. Probably we will end up doing the
same. Unfortunately we cannot fix any already released Axis2 version.
2) The Axis projects have been moved out of Apache Web Services and
promoted to a top level project. The repository has already been moved
[1], but the site has not yet been updated.
3,4,6) See comments in the corresponding JIRA issues.
5) This requires more information.
Andreas
[1] https://svn.apache.org/repos/asf/axis/axis2/java/
On Mon, Mar 1, 2010 at 20:14, Nan Null <nu...@gmail.com> wrote:
> I had a bad day with Axis. Usually, Apache projects are very high
> quality and I don't encounter issues like these. I hope that the
> developers listens and fix it accordingly.
>
> So, let's go to the issue.
>
> 1) Building version 1.5.1 doesn't work.
>
> It gave me some weird maven area about missing/invalid Java class.
>
> This turns out to be Axis's issue. The build (pom.xml) file points to
> a wrong/obsolete URL. There is a tracker for this. However, it
> wasn't easy to find it.
>
> https://issues.apache.org/jira/browse/AXIS2-4549
>
> I am not sure because of my familiarity, but I think it's due to
> Maven. I know Maven is great, but this kind of Internet dependency is
> really a limitation. For example, the site can be down, and you can't
> build. There are so many sites, so this definitely increases the
> possibility. It's not as easy as download, and build.
>
> Probably there should be a off line build download for Axis?
>
> 2) The svn repository doesn't exist.
>
> What's the point of open source, if the real time source is not
> available? At least the website doesn't point to the correct
> location:
>
> At the bottom of the page: http://ws.apache.org/axis2/, there is a link:
>
> http://svn.apache.org/viewvc/webservices/axis2/trunk/?root=Apache-SVN
>
> Going there, I don't see any source. Empty directory.
>
> 3) extraClasses flag for Java2WSDLTask is not working at all in ant
>
> 4) The above flag, even after fixing ant (that is ant would accept the
> attribute), it doesn't work at all for generating code.
>
> 5) The Java2WSDL flag "-p2n" doesn't work. This is the Java
> executable, not the ant task. However, the ant task does work (using
> the mapping sub tag).
>
> 6) The generated code has some weird code like this:
>
> if (value == null) {
> localValueTracker = true;
> } else {
> localValueTracker = true;
> }
>
> This happens to many field setters, not just one or two.
>
> For those saying design should be by contract, and Java2WSDL should be
> used. This is a different argument, but I would like to say that with
> annotation, web services goes from a method any way. Further more, if
> the WSDL are produced correctly, consistently, and in standard
> conformation way, it should not be any difference.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-user-help@axis.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org