Hi,
I suggest that number of columns per line should be 100 instead of 80.
Specifically as Axis2/C happen to have long variable/function names
because namespace prefixes 80 columns width
is hardly enough to write readable code.
thoughts?
thanks
Damitha
Ruwan Janapriya wrote:
Hi All,
Yeah, agreed. 100 is better than 80, given that we have long
variable/function names.
so +1 for that.
regards,
Janapriya.
On Mon, May 5, 2008 at 11:43 AM, Damitha Kumarage [EMAIL PROTECTED]
wrote:
Hi,
I suggest that number of columns per line should be 100 instead of 80.
Specifically as
I tested the source zip on Windows.
Here's my +1.
Thanks,
Nandika
On Mon, May 5, 2008 at 9:53 AM, Kaushalye Kapuruge [EMAIL PROTECTED] wrote:
Tested on src + binary in Debian GNU.
Worked fine.
Also all the test cases were successful in Apache Rampart/C as well.
Here's my +1.
Cheers,
Hi,
Tested binary version on Ubuntu 8.04 and works fine.
Here's my +1 for the release.
Regs
lahiru
On Mon, May 5, 2008 at 12:19 PM, Nandika Jayawardana [EMAIL PROTECTED]
wrote:
I tested the source zip on Windows.
Here's my +1.
Thanks,
Nandika
On Mon, May 5, 2008 at 9:53 AM, Kaushalye
Here's my +1 for 100 as the number of columns for line. Most of the time we
need 100 columns or more with the current naming conventions.
Thanks
Milinda
On Mon, May 5, 2008 at 11:55 AM, Ruwan Janapriya [EMAIL PROTECTED] wrote:
Yeah, agreed. 100 is better than 80, given that we have long
+1 for 100.
-Manjula.
On Mon, 2008-05-05 at 13:54 +0530, Milinda Pathirage wrote:
Here's my +1 for 100 as the number of columns for line. Most of the
time we need 100 columns or more with the current naming conventions.
Thanks
Milinda
On Mon, May 5, 2008 at 11:55 AM, Ruwan Janapriya
Tested on Dabian 4.0
Here is my +1
thanks,
Damitha
Dinesh Premalal wrote:
Hi Devs,
I have packaged and uploaded the Apache Axis2/C 1.4.0 release artifacts at
[1]. The key used to sign the release artifacts can be found at [2].
Please test, review and vote on the release artifacts for
[
https://issues.apache.org/jira/browse/AXIS2-3776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594145#action_12594145
]
Rajat Bhushan commented on AXIS2-3776:
--
Michele,
In my case, I have some web
Interesting I think you'll run into more problems, but goog luck to you!
Given our existing axis2.xml, your suggestion sounds reasonable. I
assume that the existing MEPs wouldn't need to be specified in the
axis2.xml, but may be overridden by it?
David
On Sun, May 4, 2008 at 1:47 PM, Deepal
Hello
I am having a problem with a web service.
I have a web service deployed in a tomcat server. This web service make some
stuff and also calls another web service.
Here is the code used by my web service calling the other web service:
Options options = new Options();
EndpointReference
Interesting I think you'll run into more problems, but goog luck to you!
hehe;-)
Given our existing axis2.xml, your suggestion sounds reasonable. I
assume that the existing MEPs wouldn't need to be specified in the
axis2.xml, but may be overridden by it?
Yes we do not need to
Hi,
Great to see the latest Axis2 release. When will there be a matching
Rampart release?
Or is the RC1[1] ok?
Thanks in advance
Stefan
[1] http://people.apache.org/~nandana/rampart-1.4/RC1/
-
To unsubscribe, e-mail:
Hi,
found for myself:
http://mail-archives.apache.org/mod_mbox/ws-rampart-dev/200805.mbox/[EMAIL
PROTECTED]
sorry
Stefan
Stefan Lischke wrote:
Hi,
Great to see the latest Axis2 release. When will there be a matching
Rampart release?
Or is the RC1[1] ok?
Thanks in advance
Stefan
On the homepage http://ws.apache.org/axis2/ the link (under the 1.4
Released heading) to documents home
( http://ws.apache.org/axis2/1_4/index.html ) brings up page that has a
Table of Contents, but the body is blank.
Would be nicer if the link on the homepage pointed to this:
Hi all,
When I was removing annogen dependency I realized that importance of
moving JWS-API into the kernel. The reason is that those classes are
used many places in Axis2, so having them in the kernel is much easier
than adding one more dependency to JWS-API.
Thoughts ... ?
Thank you!
adb-codegen/pom.xml - missing dependency on commons-logging
---
Key: AXIS2-3779
URL: https://issues.apache.org/jira/browse/AXIS2-3779
Project: Axis 2.0 (Axis2)
Issue Type: Bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Deepal,
If you are talking about jws-api maven module...Please don't do that!. The
effort is to let Axis2 kernel work with the
version in the JDK if there's one. (Example new JDK 1.6 updates has these
classes built-in).
thanks,
dims
Deepal
Hi,
Please do the testing with Rampart RC2 which can be found here.
[1] -
http://people.apache.org/~nandana/rampart-1.4/RC2/http://people.apache.org/%7Enandana/rampart-1.4/RC2/
it depends on the Axis2 1.4 release.
thanks,
nandana
On Mon, May 5, 2008 at 4:27 PM, Stefan Lischke [EMAIL
[
https://issues.apache.org/jira/browse/AXIS2-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594253#action_12594253
]
Alex Savitsky commented on AXIS2-3766:
--
The fact that most of these are declared in
[
https://issues.apache.org/jira/browse/AXIS2-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594257#action_12594257
]
Andreas Veithen commented on AXIS2-3766:
If you assume that your project always
[
https://issues.apache.org/jira/browse/AXIS2-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594272#action_12594272
]
Alex Savitsky commented on AXIS2-3766:
--
Thanks for the suggestion, this did the trick
[
https://issues.apache.org/jira/browse/AXIS2-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594290#action_12594290
]
David Illsley commented on AXIS2-3766:
--
Alex, we use the geronimo jars at least in
[
https://issues.apache.org/jira/browse/AXIS2-3766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594304#action_12594304
]
Alex Savitsky commented on AXIS2-3766:
--
Now, I'm not up for a legal debate (though I
Add description object to represent port-specific information on a
DescriptionBuilderComposite
--
Key: AXIS2-3780
URL: https://issues.apache.org/jira/browse/AXIS2-3780
[
https://issues.apache.org/jira/browse/AXIS2-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dustin Amrhein resolved AXIS2-3780.
---
Resolution: Fixed
Add description object to represent port-specific information on a
[
https://issues.apache.org/jira/browse/AXIS-2442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594360#action_12594360
]
Zong-Wen Cheng commented on AXIS-2442:
--
I'm encountering the same issue. The version
[
https://issues.apache.org/jira/browse/AXIS2-3781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12594439#action_12594439
]
Davanum Srinivas commented on AXIS2-3781:
-
java version 1.5.0_15
Java(TM) 2 Runtime
ComplexDataTypesTest fails under IBM JDK16
--
Key: AXIS2-3782
URL: https://issues.apache.org/jira/browse/AXIS2-3782
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Reporter: Davanum Srinivas
Hi.
On returning simple data types from my Java WS, I retrieve data successfully
at the front end, wherein i call the WS. But I have some problem with
retrieving an object array from web service
say if i have
class Sample {
String s[];
int b;
//getters and setters
}
public
Hi Dims,
Deepal,
If you are talking about jws-api maven module...Please don't do that!.
The effort is to let Axis2 kernel work with the
version in the JDK if there's one. (Example new JDK 1.6 updates has
these classes built-in).
Oh , I understand. So in JDK 1.6 we do not need dependency to
30 matches
Mail list logo
