Re: [Axis2] Isn't it time for us to move to Java 6?

If somebody asks that question, the correct answer is that we have automated builds that check every single commit against both Java versions and that our developers are using different Java versions from different vendors on different platforms. I know that some developers use 1.6 because it happe

Re: [Axis2] Isn't it time for us to move to Java 6?

What I'm saying is, if somebody asks has Axis2 been thoroughly tested on JDK/JRE 6, the best answer we could give is; 'Yes, everything should work fine, but we the developers have not rigorously tested it with JDK 6, nor do we regularly build it with JDK 6. So yeah, run in on JDK 6 on your own risk

Re: [Axis2] Isn't it time for us to move to Java 6?

What I've been observing is the world is gradually moving away from Java 5, most of the people who download a JDK download JDK 6. The JRE itself contains many improvements. Sticking to JDK5 means, Axis2 does not get tested of Java 6 on a regular basis by the developers, so we cannot give 100% assur

[jira] Commented: (AXIS2-4945) Axis2 client Unexpected subelement apple

[ https://issues.apache.org/jira/browse/AXIS2-4945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007347#comment-13007347 ] isidro lopes commented on AXIS2-4945: - I experienced the same problem and realized tha

Re: [Axis2] Isn't it time for us to move to Java 6?

On 03/16/2011 12:59 AM, Afkham Azeez wrote: > > > On Mon, Mar 14, 2011 at 4:01 PM, Dennis Sosnoski > wrote: > > Going from 1.4 to 1.5 gave access to many new features. Going from > 1.5 to 1.6 seems to me to add very little that's useful. > > What do you see as

Re: [VOTE] [AXIS2] Release Axis2-1.6.0

Hi, On Tue, Mar 15, 2011 at 7:51 PM, Amila Suriarachchi < [email protected]> wrote: > > > On Tue, Mar 15, 2011 at 3:43 PM, Andreas Veithen < > [email protected]> wrote: > >> To me this sounds like a configuration problem in your environment. >> Instead of using the default DOM p

[jira] Commented: (AXIS-2316) Connection reset when called again and again

[ https://issues.apache.org/jira/browse/AXIS-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007200#comment-13007200 ] Sanka Samaranayake commented on AXIS-2316: -- Anna, Are you facing something simil

Re: [VOTE] [AXIS2] Release Axis2-1.6.0

Hi, Guess many of these issues are already explained in the previous mail. Here's what I got anyway. 1) databinding sample: build fails with: Buildfile: /home/amila/apache/axis2-1.7.0-SNAPSHOT/samples/databinding/build.xml generate.service: [delete] Deleting directory /home/amila/apache/axis2-

Re: [VOTE] [AXIS2] Release Axis2-1.6.0

I tried for some other samples and found following issues. 1.) databinding sample a) databinding sample uses Caster as the binding framework it seems like xercesImpl is required dependency for Castor code generator because I'm getting "fatal error: unable to create SAX parser. " excep

[jira] Updated: (AXIS2-4003) Axis2 does not handle http.proxyUser and http.proxyPassword.

[ https://issues.apache.org/jira/browse/AXIS2-4003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Holster updated AXIS2-4003: Attachment: axis2-proxy-settings-order-patch.txt Hi Afkham, I'm not sure if the patch is still des

Re: [VOTE] [AXIS2] Release Axis2-1.6.0

On Tue, Mar 15, 2011 at 3:43 PM, Andreas Veithen wrote: > To me this sounds like a configuration problem in your environment. > Instead of using the default DOM parser from the JRE (which is > basically a version of Xerces relocated to a different package), it > specifically looks for > org.apache

[jira] Commented: (AXIS-2316) Connection reset when called again and again

[ https://issues.apache.org/jira/browse/AXIS-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006932#comment-13006932 ] Anna Mavroudi commented on AXIS-2316: - Hi guys (first time here), so...what is the sol

Re: [Axis2] Isn't it time for us to move to Java 6?

On Mon, Mar 14, 2011 at 4:01 PM, Dennis Sosnoski wrote: > Going from 1.4 to 1.5 gave access to many new features. Going from 1.5 to > 1.6 seems to me to add very little that's useful. > > What do you see as the big advantages of moving to 1.6/Java 6? > Perhaps you are in a better position to a

Jenkins build is back to normal : sandesha2-1.4 #59

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Jenkins build is back to normal : sandesha2-1.4 » Apache Sandesha #59

See - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

Re: [VOTE] [AXIS2] Release Axis2-1.6.0

To me this sounds like a configuration problem in your environment. Instead of using the default DOM parser from the JRE (which is basically a version of Xerces relocated to a different package), it specifically looks for org.apache.xerces.jaxp.DocumentBuilderFactoryImpl, probably because of a syst

Re: [VOTE] [AXIS2] Release Axis2-1.6.0

On Tue, Mar 15, 2011 at 3:15 AM, Andreas Veithen wrote: > I don't see any issues with the MTOM sample: > > orcus:mtom veithen$ ant > Buildfile: > /Users/veithen/dev/maven/axis/axis2-1.6/modules/distribution/target/axis2-1.6.1-SNAPSHOT/samples/mtom/build.xml > > generate.service: > [java] Retri

RE: SHA2 support

Hello, Is there anybody out there who has ever used the SHA256 algorithm / knows how to configure it? Can you please help us? It becomes a major issue as SHA1 is obsoleted. Thank you in advance Leos Od: Leos Literak [mailto:[email protected]] Odesláno: 11. března 2011 15:4