Re: using faults w/ wsdl2c

2010-02-11 Thread Selvaratnam Uthaiyashankar
Hi Sam,

You can take the checkout from
https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/

Regards,
Shankar

On Fri, Feb 12, 2010 at 9:30 AM, Sam Carleton  wrote:
> Ok, I am trying to figure out to use faults with Axis2/C.  There was a
> thread back in December that said there is some new features in the "latest
> axis2 WSDL2C generator code".  Is my understanding that on this mailing list
> when folks refer to axis2, they mean axis2/java not axis2/c, correct?
> At this time are there binaries for the latest axis2 WSDL2C generator code
> or does one still need to go to the nightly build to get it?
> It looks to me like the nightly build can be found in the following SVN
> repository:
> http://svn.apache.org/viewvc/webservices/axis2/trunk/java/
> When I try to use TortoiseSVN 1.6.1 to check out the code, I get the
> following error:
> Repository moved permanently to '/viewvc/webservices/axis2/trunk/java/';
> please relocate
> Any thoughts on what the problem is?
> Sam
> On Tue, Dec 15, 2009 at 3:32 PM, Dimuthu Gamage  wrote:
>>
>>
>> On Sat, Dec 5, 2009 at 5:56 AM, Samisa Abeysinghe  wrote:
>>>
>>>
>>> On Fri, Dec 4, 2009 at 11:09 PM, Sam Carleton 
>>> wrote:

 Dimuthu,
 Where EXACTLY does one find the latest WSDL2C code?  Is it in an build
 or is it in the Axis2/Java SVN repository?
>>
>> Hi,
>>
>> In fact right now we are not maintaining an Axis2 nightly build. So you
>> have to do your own build of Axis2/Java to get the latest WSDL2C code.
>>
>> Thanks
>> Dimuthu
>>
>>>
>>> Axis2 svn.
>>> Samisa...
>>>

 Sam

 On Thu, Dec 3, 2009 at 10:57 PM, Dimuthu Gamage 
 wrote:
>
> Hi,
>
> If you use the latest axis2 WSDL2C generator code, you don't need to
> create soap fault message manually as the generated code provide lot of
> support in generating fault message.
>
> Please have a look at this for the improved API,
> http://www.dimuthu.org/blog/2009/02/09/code-generate-custom-soap-faults-for-axis2c/
>
>
> Thanks
> Dimuthu
>
>
> On Wed, Nov 18, 2009 at 3:49 AM, Doug Price 
> wrote:
>>
>> While I see that this approach allows the creation of user-defined
>> fault types, is it possible to also use it to specify the standard
>> SOAP-ENV:Fault?  I see a struct named axiom_soap_fault_t in the
>> distribution, but I can't seem to return it from the
>> axis2_svc_skel_*_on_fault() function because it requires a pointer to the
>> SOAP body to create one.  Is there some other way to return a standard 
>> SOAP
>> fault from a service?
>>
>>
>> --
>> Doug Price
>> Research Director | Presagis
>>
>> T. +1 972 943.2433  F. +1 469 467.4564  C. +1 469 867.8399
>>
>> DISCLAIMER: This e-mail message is for the sole use of the intended
>> recipient(s) and may contain confidential and/or proprietary 
>> information. Do
>> not read, copy, or disseminate this message unless you are the addressee.
>> Any unauthorized review, use, disclosure or distribution is strictly
>> prohibited. If you have received this message in error, please contact 
>> the
>> sender by reply e-mail and delete the original and any copies from your
>> system.
>>
>> -Original Message-
>>
>> From: Amir Mousavizadegan [mailto:amir.mousavizade...@cox.net]
>> Sent: Tuesday, November 17, 2009 10:29 AM
>> To: Apache AXIS C User List
>> Subject: Re: using faults w/ wsdl2c
>>
>> I did not write the sample codes  nor the document,  however  in order
>> to
>> get it working, you have to change the body of the generated  code, or
>> create a replacement function as I did.
>> thx
>> Amir
>> - Original Message -
>> From: "Doug Price" 
>> To: "Apache AXIS C User List" 
>> Sent: Tuesday, November 17, 2009 11:05 AM
>> Subject: RE: using faults w/ wsdl2c
>>
>>
>> Just what I was looking for.  Thanks so much.
>>
>> A quick follow up question on the code though.  Is there a reason that
>> axis2_svc_skel_Division_on_fault() doesn't use the adv_divFault api to
>> create the fault?
>>
>>
>> --
>> Doug Price
>> Research Director | Presagis
>>
>> T. +1 972 943.2433  F. +1 469 467.4564  C. +1 469 867.8399
>>
>> DISCLAIMER: This e-mail message is for the sole use of the intended
>> recipient(s) and may contain confidential and/or proprietary
>> information. Do
>> not read, copy, or disseminate this message unless you are the
>> addressee.
>> Any unauthorized review, use, disclosure or distribution is strictly
>> prohibited. If you have received this message in error, please contact
>> the
>> sender by reply e-mail and delete the original and any copies from
>> your
>> system.
>>
>> -Original Message-
>>
>> From: Amir Mousavizadegan [mailto:amir.mousavizad

Re: using faults w/ wsdl2c

2010-02-11 Thread Sam Carleton
Ok, I am trying to figure out to use faults with Axis2/C.  There was a
thread back in December that said there is some new features in the "latest
axis2 WSDL2C generator code".  Is my understanding that on this mailing list
when folks refer to axis2, they mean axis2/java not axis2/c, correct?

At this time are there binaries for the latest axis2 WSDL2C generator code
or does one still need to go to the nightly build to get it?

It looks to me like the nightly build can be found in the following SVN
repository:

http://svn.apache.org/viewvc/webservices/axis2/trunk/java/

When I try to use TortoiseSVN 1.6.1 to check out the code, I get the
following error:

Repository moved permanently to '/viewvc/webservices/axis2/trunk/java/';
please relocate

Any thoughts on what the problem is?

Sam

On Tue, Dec 15, 2009 at 3:32 PM, Dimuthu Gamage  wrote:

>
>
> On Sat, Dec 5, 2009 at 5:56 AM, Samisa Abeysinghe  wrote:
>
>>
>>
>> On Fri, Dec 4, 2009 at 11:09 PM, Sam Carleton wrote:
>>
>>> Dimuthu,
>>>
>>> Where EXACTLY does one find the latest WSDL2C code?  Is it in an build or
>>> is it in the Axis2/Java SVN repository?
>>>
>>
>> Hi,
>
> In fact right now we are not maintaining an Axis2 nightly build. So you
> have to do your own build of Axis2/Java to get the latest WSDL2C code.
>
> Thanks
> Dimuthu
>
>
>> Axis2 svn.
>>
>> Samisa...
>>
>>
>>>
>>> Sam
>>>
>>>
>>>  On Thu, Dec 3, 2009 at 10:57 PM, Dimuthu Gamage wrote:
>>>
 Hi,

 If you use the latest axis2 WSDL2C generator code, you don't need to
 create soap fault message manually as the generated code provide lot of
 support in generating fault message.

 Please have a look at this for the improved API,
 http://www.dimuthu.org/blog/2009/02/09/code-generate-custom-soap-faults-for-axis2c/


 Thanks
 Dimuthu



 On Wed, Nov 18, 2009 at 3:49 AM, Doug Price wrote:

> While I see that this approach allows the creation of user-defined
> fault types, is it possible to also use it to specify the standard
> SOAP-ENV:Fault?  I see a struct named axiom_soap_fault_t in the
> distribution, but I can't seem to return it from the
> axis2_svc_skel_*_on_fault() function because it requires a pointer to the
> SOAP body to create one.  Is there some other way to return a standard 
> SOAP
> fault from a service?
>
>
> --
> Doug Price
> Research Director | Presagis
>
> T. +1 972 943.2433  F. +1 469 467.4564  C. +1 469 867.8399
>
> DISCLAIMER: This e-mail message is for the sole use of the intended
> recipient(s) and may contain confidential and/or proprietary information. 
> Do
> not read, copy, or disseminate this message unless you are the addressee.
> Any unauthorized review, use, disclosure or distribution is strictly
> prohibited. If you have received this message in error, please contact the
> sender by reply e-mail and delete the original and any copies from your
> system.
>
> -Original Message-
>
> From: Amir Mousavizadegan [mailto:amir.mousavizade...@cox.net]
> Sent: Tuesday, November 17, 2009 10:29 AM
> To: Apache AXIS C User List
> Subject: Re: using faults w/ wsdl2c
>
> I did not write the sample codes  nor the document,  however  in order
> to
> get it working, you have to change the body of the generated  code, or
> create a replacement function as I did.
> thx
> Amir
> - Original Message -
> From: "Doug Price" 
> To: "Apache AXIS C User List" 
> Sent: Tuesday, November 17, 2009 11:05 AM
> Subject: RE: using faults w/ wsdl2c
>
>
> Just what I was looking for.  Thanks so much.
>
> A quick follow up question on the code though.  Is there a reason that
> axis2_svc_skel_Division_on_fault() doesn't use the adv_divFault api to
> create the fault?
>
>
> --
> Doug Price
> Research Director | Presagis
>
> T. +1 972 943.2433  F. +1 469 467.4564  C. +1 469 867.8399
>
> DISCLAIMER: This e-mail message is for the sole use of the intended
> recipient(s) and may contain confidential and/or proprietary
> information. Do
> not read, copy, or disseminate this message unless you are the
> addressee.
> Any unauthorized review, use, disclosure or distribution is strictly
> prohibited. If you have received this message in error, please contact
> the
> sender by reply e-mail and delete the original and any copies from your
> system.
>
> -Original Message-
>
> From: Amir Mousavizadegan [mailto:amir.mousavizade...@cox.net]
> Sent: Tuesday, November 17, 2009 7:52 AM
> To: Apache AXIS C User List
> Subject: Re: using faults w/ wsdl2c
>
> Please see attached document
> - Original Message -
> From: "Doug Price" 
> To: 
> Sent: Monday, November 16, 2009 4:47 PM
> Subject: using faults 

RE : Need suggestions on Axis/c client stub

2010-02-11 Thread Nadir Amra
Actually, C support is as complete as the C++ support.  But only on client 
side, and only for doc/literal.


>From an old post when I asked the question long ago:

AxisC++ is a very good, solid, 2nd generation Web Services stack written 
in C++. It supports being a client to UDDI, and certainly it would be 
possible to support WS-Sec under it. However standards like RM and 
WS-Addressing are hard to support. 

If you look at the iterations of development, the first iteration (e.g. 
ApacheSOAP) was just about getting the job done simply. The next iteration 
added better parsing and more flexible handler models, which successfully 
supports WSSecurity and simple extensions to SOAP. 

However, the big change has been WS-Addressing, which has made WS much 
more asynchronous and message based. Unfortunately a lot of WS stacks 
including Axis/Java 1.x and Axis/C++ 1.x were built with a very RPC-like 
model. 

Axis2 C is the start of the move of Axis in C/C++ to the Axis2 model. When 
we wrote Axis2/Java we started again. In building Axis2/C we also started 
again. 
===

So basically Axis2/C and Axis2/Java were created to support more of the 
standards and improve on what was learned in prior implementations.

Nadir Amra


Olivier Mengué  wrote on 02/11/2010 03:57:55 AM:

> [image removed] 
> 
> RE : Need suggestions on Axis/c client stub
> 
> Olivier Mengué 
> 
> to:
> 
> Apache AXIS C User List, Apache AXIS C User List
> 
> 02/11/2010 04:02 AM
> 
> Cc:
> 
> "Apache AXIS C User List"
> 
> Please respond to "Apache AXIS C User List"
> 
> 
> 

> De: Nadir Amra
> >Axis-C++ client-side is not broken or buggy.  It is perfectly 
functional
> >and in some cases much easier to use than axis2/C.
> 
> So why Axis2/C was created? I'm insterested in the history of the 
project.
> Is it because "C support is not complete." in Axis C++ ?
> (according to http://ws.apache.org/axis/cpp/index.html#Known_issues )
> 
> Olivier. 

REST: HTTP_PUT: Debugging

2010-02-11 Thread Satish Bvs
Hi,


  We started adopting Axis2C framework for our project recently.
  And thank you for the the platform work.

  Currently we are stuck with a roadblock and seek your help or guidance.

  Problem Statement,
  Unable to place an successful HTTP: PUT request for an REST 
enabled operation.
  But were able to place and POST operation and it went tru.
  
  Logs & System Files,
  services.xml (segmenet)

PUT
start


Post Request & Response (through curl)
curl http://localhost:9090/services/Concordat/start -T Temp
500 Internal Server ErrorInternal 
Server ErrorThe server encountered an unexpected condition which 
prevented it from fulfilling the request.

  logs/axis2.log
[Tue Feb  2 18:38:00 2010] [info]  Starting HTTP server thread
[Tue Feb  2 18:38:01 2010] [debug] http_worker.c(200) Client HTTP version 
HTTP/1.1
[Tue Feb  2 18:38:01 2010] [info]  Request served in 0.001 seconds

   Observations
  1. If the REST operation is not properly mapped, 
  The log statement would be,
[Tue Feb  2 18:39:44 2010] [debug] rest_disp.c(114) 
Checking for service using target endpoint address : 
http://127.0.0.1:9090/services/Concordat/start
[Tue Feb  2 18:39:44 2010] [debug] core_utils.c(772) Checking for operation 
using REST HTTP Location fragment : /start
[Tue Feb  2 18:39:44 2010] [error] core_utils.c(1081) REST maping structure is 
NULL for the accessed URL

  2. For the HTTP:PUT request there is no segment,
That is checking for even endpoint address,


  Any ideas will be very helpful.
  And I will happy to give any necessary details.

Thanks,
Satish.


  

RE : Need suggestions on Axis/c client stub

2010-02-11 Thread Olivier Mengué



De: Nadir Amra
>Axis-C++ client-side is not broken or buggy.  It is perfectly functional 
>and in some cases much easier to use than axis2/C.
 
So why Axis2/C was created? I'm insterested in the history of the project.
Is it because "C support is not complete." in Axis C++ ?
(according to http://ws.apache.org/axis/cpp/index.html#Known_issues )

Olivier.