RE: Bugs with [RAMPART] and [AXIS2] 1.6.2

I have reverted back to 1.5.6 because Rampart was still checking the username and password even though I hadn't turned it on. How do you stop this behaviour anyway? I want my username and password to only be authenticated by a third party. James From: James Annesley [mailto:james.

Bugs with [RAMPART] and [AXIS2] 1.6.2

erformed a find replace on and to and respectively [2]. [1] http://stackoverflow.com/questions/8364193/illegalargumentexception-protecti ontoken-is-not-a-wsppolicy-element [2] http://markmail.org/thread/6hhk72zzgtba5y3v What are the benefits of 1.6.2 over 1.5.6 for a client?

RE: [Axis2] how to unlock and delete temporary files

>From what I gather from my experience is that it may have something to do with >Rampart. The other thing to watch is whether or not a new context, i.e., >ConfigurationContext, is created every time you make a call, e.g. create a >context, then create a stub and make a SOAP call. HTH -Ori

RE: [Axis2] how to unlock and delete temporary files

e. In that status temp files and folders are locked, so it's impossible to delete them. I want to try a 1.7.0 release candidate, how can I install it on my application using maven? thanks Il 16/07/2012 10:47, James Annesley ha scritto: Hi, I have the same problem - I wrote a message to

RE: [Axis2] how to unlock and delete temporary files

Hi, I have the same problem - I wrote a message to this forum on this subject earlier this year. Unfortunately the problem is hard to reproduce. I have found this entry on the web which may help: http://amilachinthaka.blogspot.co.uk/2010/03/axis2-temp-files.html It is fairly serious bec

RE: critical bugs in axis2 1.6

Hi, I feel some sympathy with this thread. Why are so many critical bugs being released? There are some serious problems which seem to have escaped testing. I wonder when the last really stable release of AXIS2 was? I only use it as a client and feel that I escape the majority of bugs. I realis

RE: Issue with AXis2 client code connection

Hi, "Connection refused: connect at org.apache.axis2." just means it can't access the SOAP endpoint. Make sure the SOAP server is running and available and that the client is pointing to it. The parameters when creating a stub are where you define the endpoint location. As far as the server goe

RE: [Rampart] 1.6.2

I have found the Rampart 1.6.2 distribution here: https://repository.apache.org/content/repositories/releases/org/apache/rampa rt/rampart-dist/1.6.2/. The links on the rampart web page are broken. Please fix. James From: James Annesley [mailto:james.annes...@infoshare-is.com] Sent: 30

[Rampart] 1.6.2

Hi, When is Rampart 1.6.2 released? I see Axis2 1.6.2 is released. I tried it will Rampart 1.6.3-snapshot but received an error. Rampart 1.6.1 doesn't work - see my earliest message. James Infoshare Ltd Millennium House 21 Eden Street Kingston upon Thames Surrey KT1 1BL United Kingdom Ph

RE: Any advice in order to properly set a axis2 client classpath

Hi, Why is this a problem? I just copy the whole of the AXIS2 libraries. I had some trouble with log4j compatibility but solved it with log4j-over-slf4j and logback. James -Original Message- From: COURTAULT Francois [mailto:francois.courta...@gemalto.com] Sent: 15 March 2012 12:49 To: j

RE: [Rampart]

trying to explode the .mar files as a workaround. I have tried this but don't know where to put them. Any suggested solution should also cater for multiple mar archives where the contents of the meta-inf folder names are the same across each. Cheers, From: James Annesley [mailto:james.

RE: [Rampart]

definitely not be occurring and it is a bug. I now point the finger at Rampart as it seems to be depending upon this folder. James From: James Annesley [mailto:james.annes...@infoshare-is.com] Sent: 15 February 2012 17:01 To: java-user@axis.apache.org Subject: [Rampart] Hi, On

[Rampart]

Hi, On undeploying my web app in Tomcat I got the following message: 5-Feb-2012 16:50:51 org.apache.catalina.startup.ExpandWar deleteDir SEVERE: [C:\Program Files\Apache Software Foundation\apache-tomcat-7.0.25\webapps\xxx\WEB-INF\lib] could not be completely deleted. The presence of the rema

[Axis2] [Rampart] two questions

Hi, Two questions: Introduction: I use Rampart 1.5.0 and Axis2 1.5.1. The SOAP server is WCF and it works ok. The policy is embedded in the SOAP and the AXIS2 client works after engaging Rampart without specifying a policy file. The authentication is done on the SOAP server. For each c

RE: Memory leak in Tomcat

Just saw this: https://issues.apache.org/jira/browse/AXIOM-390 From: James Annesley [mailto:james.annes...@infoshare-is.com] Sent: 02 February 2012 12:05 To: java-user@axis.apache.org Subject: RE: Memory leak in Tomcat Thanks for this - very interesting. I have analysed a memory dump and

RE: Memory leak in Tomcat

gic in it to try and clean this up (which is what generated the log message below), but it is a best effort basis. See Frank Kieviet's blog[1] discussing classloader memory leaks. [1] - http://blogs.oracle.com/fkieviet/entry/how_to_fix_the_dreaded From: James Annesley [mailto:james.annes...@infoshare-is.c

RE: Memory leak in Tomcat

For this type of error you must tuning your apache tomcat for example like this: > -server -Xms2048m -Xmx2048m -XX:PermSize=128m -XX:MaxPermSize=256m in > Environment Variable JAVA_OPTS into catalina.sh or catalina.bat Eh? Why will increasing the memory fix a ThreadLocal cleanup problem? &g

RE: Memory leak in Tomcat

Alberto Lindo Gutarra [mailto:mli...@gmail.com] Sent: 01 February 2012 16:31 To: java-user@axis.apache.org Subject: Re: Memory leak in Tomcat can you tell us your tomcat memory configuration and harware ram, cpu, type (32 or 64 bits) characteristics??? 2012/2/1 James Annesley > > Hi, > >

RE: Completly lost

Hi Francois, I noticed you don't need the server policy file at all on the client side. I do this: client.engageModule("rampart"); options.setProperty(RampartMessageData.KEY_RAMPART_POLICY, null); where client is the ServiceClient. HTH James From: COURTAULT Francois [ma

RE: Policy not supported: is it a bug ?

Hi, I finally tested axis2 1.6.2-snapshot with Rampart 1.6.2-snapshot and can confirm that now it works. Previously, I hadn't tested it correctly. James From: Sagara Gunathunga [mailto:sagara.gunathu...@gmail.com] Sent: 30 January 2012 09:56 To: java-user@axis.apache.org Subject: Re: P

Upgrading to 1.6.0 and beyond

Hi, 1.6.0 works ok for me but I noticed all the exceptions were replaced with a single ExceptionFault.java class. Previously I had a separate exception for each the request. I would have assumed this is an improvement except that I noticed in 1.6.1 and in 1.6.2-snapshot they have reappeared. Pl

RE: blocking exception

e.org Subject: Re: blocking exception Can you test this with Axis2 and Rampart 1.6.2-SNAPSHOT? Andreas On Thu, Jan 26, 2012 at 20:25, James Annesley wrote: > > Hi, > > > > I have a working system using Axis2 1.5.1 and Rampart 1.5. > > > > I am trying to upgrade to 1.6.

blocking exception

Hi, I have a working system using Axis2 1.5.1 and Rampart 1.5. I am trying to upgrade to 1.6. I have installed the new libraries, built a new stub. When trying to instantiate a new stub I get the following error: "java.lang.IllegalArgumentException: {http://schemas.xmlsoap.org/ws/2005/07/s