Re: Some of the tests are Client Compilation - FAILED

We are making a lot of memory model changes in order to get over some difficult issues. These issues start with axiscpp-149. They then expand to take in simple typees and complex types. The gist of the problem is this - Firstly, this appears to be a windows problem but might well affect all

Axis2 versus C++

Hello, I am slightly confused about the possibility of generating C/C++ Code with Axis2. Is C/C++ code generation possible - using command line similar to Axis1 - only via Eclipse plugin - not possible at all ??? I am using version 0.92. Thanks in advance Franz Dr. Franz Fehringer (Dipl.

Re: Axis2 versus C++

FranzThere is an existing Axis*1* in C++ http://ws.apache.org/axis/cpp/index.htmlWe have only just started on building Axis*2* in C. At the moment there is some C# support in Axis2/Java which requires you to run Axis2/Java in IKVM under .NET. PaulOn 11/4/05, Franz Fehringer [EMAIL PROTECTED]

Re: Axis2 versus C++

Hi Paul, When do you think you'll have C++ going? Are you targeting C or C++ first? what kind of test suite do you have. I'd be interested if we could see the whole of the axisCPP *1* suite running against it - perhaps we could share test suites? It would save you guys a lot of effort. cheers,

Re: Axis2 versus C++

Hi JohnWe are targeting a pure C runtime with C++ wrappers. Its early days. We are just getting the object model and coding style right.As regards test suites sounds like a great idea.Paul On 11/4/05, John Hawkins [EMAIL PROTECTED] wrote: Hi Paul, When do you think you'll have C++ going? Are

[jira] Updated: (AXISCPP-865) XSD_NMTOKEN test is using the following incorrect message string, This is a message!.

[ http://issues.apache.org/jira/browse/AXISCPP-865?page=all ] Fred Preston updated AXISCPP-865: - Description: In XSD_NMTOKEN the token message is set to This is a message!. The server always replies with a fault. Under further investigation, a

test.exclusion.list

Folks, if, when running tests, you find that you don't want to run them all for whatever reason, you can now create a property file with all the excluded tests in it. You can pass this file in as the test.exclude.list property on the cmdline and any tests declared in that list will be ignored

[jira] Created: (AXIS-2285) Deserializing objects on client side with unknown data members from server side causes exception, makes server code harder to maintain

Deserializing objects on client side with unknown data members from server side causes exception, makes server code harder to maintain -- Key: AXIS-2285

[jira] Created: (AXIS-2286) Client side does not handle null values for primitive types, causes NullPointerException

Client side does not handle null values for primitive types, causes NullPointerException Key: AXIS-2286 URL: http://issues.apache.org/jira/browse/AXIS-2286 Project: Apache Axis

Re: [Axis2] Some one has removed my code changes

yes , I will do that. Thanks, Deepal ~Future is Open~ - Original Message - From: Davanum Srinivas [EMAIL PROTECTED] To: axis-dev@ws.apache.org Sent: Friday, November 04, 2005 10:59 AM Subject: Re: [Axis2] Some one has

Re: [Axis2] Qnames

Sanjiva Weerawarana wrote: On Thu, 2005-11-03 at 12:59 +, Steve Loughran wrote: IIRC, there are different interpretations for different usages/specs (XPath, XQuery, Schema, etc.), but it might be that this has been cleaned up by now and is more consistent. We needed the option for Axis

[jira] Commented: (AXIS-2285) Deserializing objects on client side with unknown data members from server side causes exception, makes server code harder to maintain

[ http://issues.apache.org/jira/browse/AXIS-2285?page=comments#action_12356768 ] Geir Egil Hansen commented on AXIS-2285: It does need what it does not know about. Mystery sentence with no meaning. Here is a new try: I think it is wrong to throw an

[jira] Created: (AXIS-2287) Alternative approach for stub generation

Alternative approach for stub generation Key: AXIS-2287 URL: http://issues.apache.org/jira/browse/AXIS-2287 Project: Apache Axis Type: New Feature Versions: future (enh) Reporter: Guy Rixon Priority: Minor

[jira] Commented: (AXIS-2287) Alternative approach for stub generation

[ http://issues.apache.org/jira/browse/AXIS-2287?page=comments#action_12356771 ] Davanum Srinivas commented on AXIS-2287: - The Java interface definine the API for the stubs is done using Java2WSDL. So the recommendation is to start with

Re: [Axis2] Qnames

Steve Loughran wrote: Sanjiva Weerawarana wrote: On Thu, 2005-11-03 at 12:59 +, Steve Loughran wrote: IIRC, there are different interpretations for different usages/specs (XPath, XQuery, Schema, etc.), but it might be that this has been cleaned up by now and is more consistent. We

Re: [Axis2] Qnames

#1: maven jar:install #2: add a project.properties in root and add one line as follows optional.includes= #3: just maven from root should work w/o network connection. maven all-tests needs connection thanks, dims On 11/4/05, Steve Loughran [EMAIL PROTECTED] wrote: Steve Loughran wrote:

[jira] Created: (AXIS-2288) Bad document style request processing

Bad document style request processing -- Key: AXIS-2288 URL: http://issues.apache.org/jira/browse/AXIS-2288 Project: Apache Axis Type: Bug Components: WSDL processing Versions: 1.3 Environment: Windows XP, Jakarta

[Axis2]New Feature - Sending same message to more than One Recepcient

Hi All; Shall we add a support to users to send same message to more than one recipients? Motivate for the doing this is if we need to send same message to 20 recipients, (e.g. Publish Subscribe) . If user create 20 Calls it will be very expensive and if we do the thingy inside Axis2 we can set

Re: [Axis2]New Feature - Sending same message to more than One Recepcient

Srinath Perera schrieb: Hi All; Shall we add a support to users to send same message to more than one recipients? Motivate for the doing this is if we need to send same message to 20 recipients, (e.g. Publish Subscribe) . If user create 20 Calls it will be very expensive and if we do the

Re: [Axis2]New Feature - Sending same message to more than One Recepcient

Hi Christoph; If you can tell us what was your experiance and something about what is exactly you look for. e.g. the Ideal API you want to see. It will be very helpful :) e.g 1) Do you need to send differnat addressing headers 2) do you need differant aspects (WS-Secuirty .. RM ) for each

[jira] Commented: (AXIS-2284) thread hangs on org.apache.axis.utils.JavaUtils.isEnumClass

[ http://issues.apache.org/jira/browse/AXIS-2284?page=comments#action_12356807 ] Davanum Srinivas commented on AXIS-2284: Frank, looking at isEnumClass(), could you please try to switch the key of the hashmap to the full package + class name

[jira] Commented: (AXIS-2285) Deserializing objects on client side with unknown data members from server side causes exception, makes server code harder to maintain

[ http://issues.apache.org/jira/browse/AXIS-2285?page=comments#action_12356810 ] Tom Jordahl commented on AXIS-2285: --- What you are talking about here is changing the contract (the Schema in the WSDL) and versioning the service. This is a very hard

[jira] Commented: (AXIS-2288) Bad document style request processing

[ http://issues.apache.org/jira/browse/AXIS-2288?page=comments#action_12356811 ] Tom Jordahl commented on AXIS-2288: --- You are correct, the dispatching of the operations is based on the child element of the SOAP body. How would you expect this to work?

[jira] Updated: (AXIS-2232) Mappings in TypeDesc can't be GC'ed

[ http://issues.apache.org/jira/browse/AXIS-2232?page=all ] Kevan Miller updated AXIS-2232: --- Attachment: SingleWeakHashMap.patch Implementation of 1) that I described in an earlier comment. There are pathological cases where the javaClass may have been

Re: [Axis2] Road Map for next release

Hi all, I know this will light the flames again... How about finalising the AxisFault issues for the next release... Support for SOAP 1.2 fualts.. Also ws-Addressing testing. Specially the final version.. My two cents... Thanks, ~Thilina On 11/4/05, Tom Jordahl [EMAIL PROTECTED] wrote: I

Re: [Axis2]New Feature - Sending same message to more than One Recepcient

Hi Srinath, can't wedo this by changing the toEPR in the Call api and invoke the method ? Sorry if I understood this wrong. for example; call.setTo(eprOne) call.ivokeBlocking(.); call.setTo(eprTwo) call.invokeBlocking(...) Srinath Perera wrote: Hi All; Shall we add a support to users

Re: [Axis2] Road Map for next release

Thilina, This is the not last release in Axis2. What I propose is to release whatever we have so far after the last release. We don't have a nightly build mechanism also. I saw a mail in the user list saying he likes a release after several bug fixes. and that guy knows that the bug is fixed

Re: [Axis2] Road Map for next release

Hi, No probs... I thought we all r heading for 1.0 release Yes Pls PLS have a nightly build mechanism and make snapshots available in a repository. We need it badly for projects like Kandula Sandesha... Our users find it really hard to get Kandula2 up and running. For that they need to

Re: [Axis2]New Feature - Sending same message to more than One Recepcient

Actually i am trying to implement this kind of transport multiplexing thing for some other project and one further problem that i faced was how to handle the addressing stuff. So IMO multiplexing should start at the addressing out handler because the addressing headers are different for the out