You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Senaka Fernando (JIRA)" <ji...@apache.org> on 2008/02/04 18:27:08 UTC
[jira] Created: (AXIS2C-964) Support for uint64_t, int64_t required
at codegen level
Support for uint64_t, int64_t required at codegen level
-------------------------------------------------------
Key: AXIS2C-964
URL: https://issues.apache.org/jira/browse/AXIS2C-964
Project: Axis2-C
Issue Type: Improvement
Components: code generation, wsdl2c tool
Reporter: Senaka Fernando
Fix For: 1.3.0
Support for uint64_t, int64_t required at codegen level. I have added support at util level and fixed AXIS2C-919. Hope we can add this to the codegen tool too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [AXIS2C] IIS module - cannot find the log file
Posted by Supun Kamburugamuva <su...@gmail.com>.
Hi Dave,
AFAIK we have not encountered a problem like this before. Maximum file
length of the log file can be 256 characters long. So I guess the
problem is not there.
Did you encounter this problem when you start the server or did it
vanish while the server was running?
Can you send the file path of the log file or a similar path so we can
try to reproduce the issue?
Regards,
Supun.
On Feb 7, 2008 6:25 PM, Dave Meier <DM...@serena.com> wrote:
> Hi All,
>
> I've been using the IIS module and getting a log file, but today I can
> no longer find the log file. I have everything set up as it should be
> with axis2c_home, log_file and log_level defined in the registry. My
> web service runs fine, but no log file. Yesterday I noticed my log file
> was missing the last 2 characters which was strange as the path was
> long, but only 130 characters. So instead of axis2iis.log I was getting
> axis2iis.l. And now today no log file at all.
>
> Does anyone know of a problem with the IIS module with respect to this
> or do you have any steps you recommend to figure out what it happening.
> I have not had much luck in the past with debugging IIS so I'm hoping
> not to have to do that.
>
> Thanks,
>
> -Dave.
>
> **********************************************************************
> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
> **********************************************************************
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [AXIS2C] IIS module - cannot find the log file
Posted by Senaka Fernando <se...@wso2.com>.
Hi Dave,
I just tried, yes, it is a bug. I do not know what has caused it, as it
doesn't seem to look like a side-effect of a fix. I will fix this today
evening.
Regards,
Senaka
> Hi Dave,
>
> I will take a look and correct this ASAP. Should be a result of a recent
> fix. Thanks for letting us know.
>
> Regards,
> Senaka
>
>> Hi All,
>>
>> I've been using the IIS module and getting a log file, but today I can
>> no longer find the log file. I have everything set up as it should be
>> with axis2c_home, log_file and log_level defined in the registry. My
>> web service runs fine, but no log file. Yesterday I noticed my log file
>> was missing the last 2 characters which was strange as the path was
>> long, but only 130 characters. So instead of axis2iis.log I was getting
>> axis2iis.l. And now today no log file at all.
>>
>> Does anyone know of a problem with the IIS module with respect to this
>> or do you have any steps you recommend to figure out what it happening.
>> I have not had much luck in the past with debugging IIS so I'm hoping
>> not to have to do that.
>>
>> Thanks,
>>
>> -Dave.
>>
>> **********************************************************************
>> This email and any files transmitted with it are confidential and
>> intended
>> solely for the use of the individual or entity to whom they are
>> addressed.
>> Any unauthorized review, use, disclosure or distribution is prohibited.
>> If
>> you are not the intended recipient, please contact the sender by reply
>> e-mail and destroy all copies of the original message.
>> **********************************************************************
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [AXIS2C] IIS module - cannot find the log file
Posted by Senaka Fernando <se...@wso2.com>.
Hi Dave,
I will take a look and correct this ASAP. Should be a result of a recent
fix. Thanks for letting us know.
Regards,
Senaka
> Hi All,
>
> I've been using the IIS module and getting a log file, but today I can
> no longer find the log file. I have everything set up as it should be
> with axis2c_home, log_file and log_level defined in the registry. My
> web service runs fine, but no log file. Yesterday I noticed my log file
> was missing the last 2 characters which was strange as the path was
> long, but only 130 characters. So instead of axis2iis.log I was getting
> axis2iis.l. And now today no log file at all.
>
> Does anyone know of a problem with the IIS module with respect to this
> or do you have any steps you recommend to figure out what it happening.
> I have not had much luck in the past with debugging IIS so I'm hoping
> not to have to do that.
>
> Thanks,
>
> -Dave.
>
> **********************************************************************
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> Any unauthorized review, use, disclosure or distribution is prohibited. If
> you are not the intended recipient, please contact the sender by reply
> e-mail and destroy all copies of the original message.
> **********************************************************************
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
RE: [AXIS2C] Questions about using REST
Posted by Dave Meier <DM...@SERENA.com>.
Thanks, Senaka. My GET test is now working!
-Dave.
-----Original Message-----
From: Senaka Fernando [mailto:senaka@wso2.com]
Sent: Saturday, February 09, 2008 12:13 PM
To: axis-c-dev@ws.apache.org
Subject: Re: [AXIS2C] Questions about using REST
Hi again Dave,
I did fix two bugs in the code, with respect to REST, one of which you
reported, and another that indirectly affects. I also tested your
scenario calling the endpoint,
http://localhost:9090/axis2/services/echo/echoString/Hello/ using
Mozilla Firefox, which returned,
<ns1:echoString>
<text>Hello</text>
</ns1:echoString>
Please do try now, I believe it should work for you.
Regards,
Senaka
> Hi Dave,
>
> Unless it is a bug somewhere in the code, that we could not track, you
> are capable of calling
> http://localhost:9090/axis2/services/aewebservices70/GetItem/111, and
> getting the request dispatched. I will check into this and get it
fixed.
>
> Also, I believe if you setup RESTLocation, as in the way you say
> below, your itemid will get added to your payload (the axiom_node that
you get).
> It may reside either at the top (before the query parameter info) or
> the bottom (after the query parameter info) of your payload, depending
> on the way it got dispatched. However, you can access that information
> in the very same way you access a query parameter. So, try to browse
> through your node.
>
> Also, as it is very hard to figure out a clear-cut specification on
> REST fot Web Services, other than of course the HTTP-Binding in the
> WSDL2.0 and WADL from which we got an insight, you are welcome to
> express your thoughts for additions and improvements to the REST logic
> in the Axis2/C engine.
>
> Regards,
> Senaka
>
>> Hi Senaka, Samisa and Others,
>>
>> I am now starting to implement REST style calls and have a couple
>> questions:
>>
>> 1. It seems that a GET REST call only works if a query string with
>> at least one value is specified in the URI. For example I want to do
>> "wsclient.exe -get
>> http://localhost:9090/axis2/services/aewebservices70/GetItem/111" to
>> get item "111" but that won't work. I have to do "wsclient.exe -get
>> http://localhost:9090/axis2/services/aewebservices70/GetItem/111?foo=
>> bar " and then the request does get dispatched to my code. Is there
>> a way around this?
>>
>> 2. I don't know how to get at the values in the URL, like the "111"
>> value above which I have mapped like "<parameter
>> name="RESTLocation">GetItem/{itemid}</parameter>". Do I look up
>> "itemid" somewhere in the message context? I haven't done much with
>> the context so any code samples would be awesome. If I want to get
>> query string values how do I do that?
>>
>> Thank you for your help!
>>
>> -Dave.
>>
>> *********************************************************************
>> * This email and any files transmitted with it are confidential and
>> intended solely for the use of the individual or entity to whom they
>> are addressed.
>> Any unauthorized review, use, disclosure or distribution is
prohibited.
>> If
>> you are not the intended recipient, please contact the sender by
>> reply e-mail and destroy all copies of the original message.
>> *********************************************************************
>> *
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [AXIS2C] Questions about using REST
Posted by Senaka Fernando <se...@wso2.com>.
Hi again Dave,
I did fix two bugs in the code, with respect to REST, one of which you
reported, and another that indirectly affects. I also tested your scenario
calling the endpoint,
http://localhost:9090/axis2/services/echo/echoString/Hello/ using Mozilla
Firefox, which returned,
<ns1:echoString>
<text>Hello</text>
</ns1:echoString>
Please do try now, I believe it should work for you.
Regards,
Senaka
> Hi Dave,
>
> Unless it is a bug somewhere in the code, that we could not track, you are
> capable of calling
> http://localhost:9090/axis2/services/aewebservices70/GetItem/111, and
> getting the request dispatched. I will check into this and get it fixed.
>
> Also, I believe if you setup RESTLocation, as in the way you say below,
> your itemid will get added to your payload (the axiom_node that you get).
> It may reside either at the top (before the query parameter info) or the
> bottom (after the query parameter info) of your payload, depending on the
> way it got dispatched. However, you can access that information in the
> very same way you access a query parameter. So, try to browse through your
> node.
>
> Also, as it is very hard to figure out a clear-cut specification on REST
> fot Web Services, other than of course the HTTP-Binding in the WSDL2.0 and
> WADL from which we got an insight, you are welcome to express your
> thoughts for additions and improvements to the REST logic in the Axis2/C
> engine.
>
> Regards,
> Senaka
>
>> Hi Senaka, Samisa and Others,
>>
>> I am now starting to implement REST style calls and have a couple
>> questions:
>>
>> 1. It seems that a GET REST call only works if a query string with at
>> least one value is specified in the URI. For example I want to do
>> "wsclient.exe -get
>> http://localhost:9090/axis2/services/aewebservices70/GetItem/111" to get
>> item "111" but that won't work. I have to do "wsclient.exe -get
>> http://localhost:9090/axis2/services/aewebservices70/GetItem/111?foo=bar
>> " and then the request does get dispatched to my code. Is there a way
>> around this?
>>
>> 2. I don't know how to get at the values in the URL, like the "111"
>> value above which I have mapped like "<parameter
>> name="RESTLocation">GetItem/{itemid}</parameter>". Do I look up
>> "itemid" somewhere in the message context? I haven't done much with the
>> context so any code samples would be awesome. If I want to get query
>> string values how do I do that?
>>
>> Thank you for your help!
>>
>> -Dave.
>>
>> **********************************************************************
>> This email and any files transmitted with it are confidential and
>> intended
>> solely for the use of the individual or entity to whom they are
>> addressed.
>> Any unauthorized review, use, disclosure or distribution is prohibited.
>> If
>> you are not the intended recipient, please contact the sender by reply
>> e-mail and destroy all copies of the original message.
>> **********************************************************************
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: [AXIS2C] Questions about using REST
Posted by Senaka Fernando <se...@wso2.com>.
Hi Dave,
Unless it is a bug somewhere in the code, that we could not track, you are
capable of calling
http://localhost:9090/axis2/services/aewebservices70/GetItem/111, and
getting the request dispatched. I will check into this and get it fixed.
Also, I believe if you setup RESTLocation, as in the way you say below,
your itemid will get added to your payload (the axiom_node that you get).
It may reside either at the top (before the query parameter info) or the
bottom (after the query parameter info) of your payload, depending on the
way it got dispatched. However, you can access that information in the
very same way you access a query parameter. So, try to browse through your
node.
Also, as it is very hard to figure out a clear-cut specification on REST
fot Web Services, other than of course the HTTP-Binding in the WSDL2.0 and
WADL from which we got an insight, you are welcome to express your
thoughts for additions and improvements to the REST logic in the Axis2/C
engine.
Regards,
Senaka
> Hi Senaka, Samisa and Others,
>
> I am now starting to implement REST style calls and have a couple
> questions:
>
> 1. It seems that a GET REST call only works if a query string with at
> least one value is specified in the URI. For example I want to do
> "wsclient.exe -get
> http://localhost:9090/axis2/services/aewebservices70/GetItem/111" to get
> item "111" but that won't work. I have to do "wsclient.exe -get
> http://localhost:9090/axis2/services/aewebservices70/GetItem/111?foo=bar
> " and then the request does get dispatched to my code. Is there a way
> around this?
>
> 2. I don't know how to get at the values in the URL, like the "111"
> value above which I have mapped like "<parameter
> name="RESTLocation">GetItem/{itemid}</parameter>". Do I look up
> "itemid" somewhere in the message context? I haven't done much with the
> context so any code samples would be awesome. If I want to get query
> string values how do I do that?
>
> Thank you for your help!
>
> -Dave.
>
> **********************************************************************
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> Any unauthorized review, use, disclosure or distribution is prohibited. If
> you are not the intended recipient, please contact the sender by reply
> e-mail and destroy all copies of the original message.
> **********************************************************************
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[AXIS2C] Questions about using REST
Posted by Dave Meier <DM...@SERENA.com>.
Hi Senaka, Samisa and Others,
I am now starting to implement REST style calls and have a couple
questions:
1. It seems that a GET REST call only works if a query string with at
least one value is specified in the URI. For example I want to do
"wsclient.exe -get
http://localhost:9090/axis2/services/aewebservices70/GetItem/111" to get
item "111" but that won't work. I have to do "wsclient.exe -get
http://localhost:9090/axis2/services/aewebservices70/GetItem/111?foo=bar
" and then the request does get dispatched to my code. Is there a way
around this?
2. I don't know how to get at the values in the URL, like the "111"
value above which I have mapped like "<parameter
name="RESTLocation">GetItem/{itemid}</parameter>". Do I look up
"itemid" somewhere in the message context? I haven't done much with the
context so any code samples would be awesome. If I want to get query
string values how do I do that?
Thank you for your help!
-Dave.
**********************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[AXIS2C] IIS module - cannot find the log file
Posted by Dave Meier <DM...@SERENA.com>.
Hi All,
I've been using the IIS module and getting a log file, but today I can
no longer find the log file. I have everything set up as it should be
with axis2c_home, log_file and log_level defined in the registry. My
web service runs fine, but no log file. Yesterday I noticed my log file
was missing the last 2 characters which was strange as the path was
long, but only 130 characters. So instead of axis2iis.log I was getting
axis2iis.l. And now today no log file at all.
Does anyone know of a problem with the IIS module with respect to this
or do you have any steps you recommend to figure out what it happening.
I have not had much luck in the past with debugging IIS so I'm hoping
not to have to do that.
Thanks,
-Dave.
**********************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Updated: (AXIS2C-964) Support for uint64_t, int64_t required
at codegen level
Posted by "Dimuthu Gamage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dimuthu Gamage updated AXIS2C-964:
----------------------------------
Attachment: case12.zip
I changed long to int64_t and unsigned long to uint64_t.
if the attached code is working in windows, then we can close the jira
> Support for uint64_t, int64_t required at codegen level
> -------------------------------------------------------
>
> Key: AXIS2C-964
> URL: https://issues.apache.org/jira/browse/AXIS2C-964
> Project: Axis2-C
> Issue Type: Improvement
> Components: code generation, wsdl2c tool
> Reporter: Senaka Fernando
> Fix For: 1.3.0
>
> Attachments: case12.zip
>
>
> Support for uint64_t, int64_t required at codegen level. I have added support at util level and fixed AXIS2C-919. Hope we can add this to the codegen tool too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Closed: (AXIS2C-964) Support for uint64_t, int64_t required
at codegen level
Posted by "Senaka Fernando (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Senaka Fernando closed AXIS2C-964.
----------------------------------
Closed Issue
> Support for uint64_t, int64_t required at codegen level
> -------------------------------------------------------
>
> Key: AXIS2C-964
> URL: https://issues.apache.org/jira/browse/AXIS2C-964
> Project: Axis2-C
> Issue Type: Improvement
> Components: code generation, wsdl2c tool
> Reporter: Senaka Fernando
> Assignee: Senaka Fernando
> Fix For: 1.3.0
>
> Attachments: case12.zip, case12.zip, case12_new.zip, win_screen_shot_1.jpg
>
>
> Support for uint64_t, int64_t required at codegen level. I have added support at util level and fixed AXIS2C-919. Hope we can add this to the codegen tool too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Updated: (AXIS2C-964) Support for uint64_t, int64_t required
at codegen level
Posted by "Dimuthu Gamage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dimuthu Gamage updated AXIS2C-964:
----------------------------------
Attachment: case12_new.zip
Hi, Now the test works in linux. I think it is not necessary to define constants for the function names, we can use the functions (axutil_strtoul, axutil_strtol) straight away.
> Support for uint64_t, int64_t required at codegen level
> -------------------------------------------------------
>
> Key: AXIS2C-964
> URL: https://issues.apache.org/jira/browse/AXIS2C-964
> Project: Axis2-C
> Issue Type: Improvement
> Components: code generation, wsdl2c tool
> Reporter: Senaka Fernando
> Fix For: 1.3.0
>
> Attachments: case12.zip, case12.zip, case12_new.zip, win_screen_shot_1.jpg
>
>
> Support for uint64_t, int64_t required at codegen level. I have added support at util level and fixed AXIS2C-919. Hope we can add this to the codegen tool too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Updated: (AXIS2C-964) Support for uint64_t, int64_t required
at codegen level
Posted by "Senaka Fernando (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Senaka Fernando updated AXIS2C-964:
-----------------------------------
Attachment: win_screen_shot_1.jpg
I'm affraid that it wont work. Seems that "atoll" is not found. Why not use strtoul?
Regards,
Senaka
> Support for uint64_t, int64_t required at codegen level
> -------------------------------------------------------
>
> Key: AXIS2C-964
> URL: https://issues.apache.org/jira/browse/AXIS2C-964
> Project: Axis2-C
> Issue Type: Improvement
> Components: code generation, wsdl2c tool
> Reporter: Senaka Fernando
> Fix For: 1.3.0
>
> Attachments: case12.zip, win_screen_shot_1.jpg
>
>
> Support for uint64_t, int64_t required at codegen level. I have added support at util level and fixed AXIS2C-919. Hope we can add this to the codegen tool too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXIS2C-964) Support for uint64_t, int64_t
required at codegen level
Posted by "Senaka Fernando (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567369#action_12567369 ]
Senaka Fernando commented on AXIS2C-964:
----------------------------------------
Hi Dimuthu,
You two functions which can be used.
1. AXIS2_STRTOUL
2. AXIS2_STRTOL
Please have a look and try to use them.
Regards,
Senaka
> Support for uint64_t, int64_t required at codegen level
> -------------------------------------------------------
>
> Key: AXIS2C-964
> URL: https://issues.apache.org/jira/browse/AXIS2C-964
> Project: Axis2-C
> Issue Type: Improvement
> Components: code generation, wsdl2c tool
> Reporter: Senaka Fernando
> Fix For: 1.3.0
>
> Attachments: case12.zip, case12.zip, win_screen_shot_1.jpg
>
>
> Support for uint64_t, int64_t required at codegen level. I have added support at util level and fixed AXIS2C-919. Hope we can add this to the codegen tool too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXIS2C-964) Support for uint64_t, int64_t
required at codegen level
Posted by "Senaka Fernando (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567426#action_12567426 ]
Senaka Fernando commented on AXIS2C-964:
----------------------------------------
Hi Dimuthu,
I tested the latest attachment and it works fine on Windows. However, you need to change just one thing. I recently discovered that we are defining some format specifiers in platforms/unix/axutil_unix.h, and thus, to preserve the consistency, I have renamed the constants to,
1. AXIS2_PRINTF_INT64_FORMAT_SPECIFIER
2. AXIS2_PRINTF_UINT64_FORMAT_SPECIFIER
3. AXIS2_PRINTF_INT32_FORMAT_SPECIFIER
4. AXIS2_PRINTF_UINT32_FORMAT_SPECIFIER
We need not test this specifically on windows, and therefore, after you correct this on the Java svn, we can close this issue.
Regards,
Senaka
> Support for uint64_t, int64_t required at codegen level
> -------------------------------------------------------
>
> Key: AXIS2C-964
> URL: https://issues.apache.org/jira/browse/AXIS2C-964
> Project: Axis2-C
> Issue Type: Improvement
> Components: code generation, wsdl2c tool
> Reporter: Senaka Fernando
> Fix For: 1.3.0
>
> Attachments: case12.zip, case12.zip, case12_new.zip, win_screen_shot_1.jpg
>
>
> Support for uint64_t, int64_t required at codegen level. I have added support at util level and fixed AXIS2C-919. Hope we can add this to the codegen tool too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXIS2C-964) Support for uint64_t, int64_t
required at codegen level
Posted by "Dimuthu Gamage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567360#action_12567360 ]
Dimuthu Gamage commented on AXIS2C-964:
---------------------------------------
I update the templates to use these constants. now the serialization happens correctly. But deserialization the problem still remains.
strtoul and strtol are not giving expected values, specially when deserializing values near to 2^63-1. Should check other ways to correct this.
Thanks
Dimuthu
> Support for uint64_t, int64_t required at codegen level
> -------------------------------------------------------
>
> Key: AXIS2C-964
> URL: https://issues.apache.org/jira/browse/AXIS2C-964
> Project: Axis2-C
> Issue Type: Improvement
> Components: code generation, wsdl2c tool
> Reporter: Senaka Fernando
> Fix For: 1.3.0
>
> Attachments: case12.zip, case12.zip, win_screen_shot_1.jpg
>
>
> Support for uint64_t, int64_t required at codegen level. I have added support at util level and fixed AXIS2C-919. Hope we can add this to the codegen tool too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXIS2C-964) Support for uint64_t, int64_t
required at codegen level
Posted by "Senaka Fernando (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567338#action_12567338 ]
Senaka Fernando commented on AXIS2C-964:
----------------------------------------
Hi Dimuthu,
I guess this is not solved yet. I think there is an issue when printing the number to a string.
I sent these numbers,
1. 9223372036854775808
2. 92233720368
3. 9223372036854775
4. 922337203
5. 92233720
And, these are what went in the payload
1. 0
2. 2039407152
3. 2783138807
4. 922337203
5. 92233720
I think we'll have to come with some new uint64 to string logic. I think we can support this at the util level. I will look into the possibility of doing that. Also I found this,
sprintf (text_value_1, "%lu", (int)_RetULong->property_inULong);
inside adb_RetULong. I bet this leads to some nasty havoc.
Regards,
Senaka
> Support for uint64_t, int64_t required at codegen level
> -------------------------------------------------------
>
> Key: AXIS2C-964
> URL: https://issues.apache.org/jira/browse/AXIS2C-964
> Project: Axis2-C
> Issue Type: Improvement
> Components: code generation, wsdl2c tool
> Reporter: Senaka Fernando
> Fix For: 1.3.0
>
> Attachments: case12.zip, case12.zip, win_screen_shot_1.jpg
>
>
> Support for uint64_t, int64_t required at codegen level. I have added support at util level and fixed AXIS2C-919. Hope we can add this to the codegen tool too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXIS2C-964) Support for uint64_t, int64_t
required at codegen level
Posted by "Senaka Fernando (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567334#action_12567334 ]
Senaka Fernando commented on AXIS2C-964:
----------------------------------------
Hi Dimuthu,
Both skeleton and stub, built without any problem. Once I ran the demo, I got,
Returned Long: 1
Returned Long: 3
These are the payloads exchanged
Request 1:
POST /axis2/services/BaseDataTypesDocLitWService HTTP/1.1
User-Agent: Axis2/C
SOAPAction: "http://tempuri.org/IBaseDataTypesDocLitW/RetLong"
Content-Length: 502
Content-Type: text/xml;charset=UTF-8
Host: 127.0.0.1:8080
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:To>http://localhost:8080/axis2/services/BaseDataTypesDocLitWService</wsa:To>
<wsa:Action>http://tempuri.org/IBaseDataTypesDocLitW/RetLong</wsa:Action>
<wsa:MessageID>fa0e7a7b-a51f-448e-ab2c-7e27db10a618</wsa:MessageID>
</soapenv:Header>
<soapenv:Body>
<n:RetLong xmlns:n="http://tempuri.org/">
<n:inLong>0</n:inLong>
</n:RetLong>
</soapenv:Body></soapenv:Envelope>
Response 1:
HTTP/1.1 200 OK
Content-Type: text/xml;charset=UTF-8
Content-Length: 696
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:Action>http://tempuri.org/IBaseDataTypesDocLitW/RetLong</wsa:Action>
<wsa:From>
<wsa:Address>http://localhost:8080/axis2/services/BaseDataTypesDocLitWService</wsa:Address>
</wsa:From>
<wsa:MessageID>c1f7de5d-07b9-418f-aeec-158f8b889da2</wsa:MessageID>
<wsa:RelatesTo wsa:RelationshipType="http://www.w3.org/2005/08/addressing/reply">fa0e7a7b-a51f-448e-ab2c-7e27db10a618</wsa:RelatesTo>
</soapenv:Header>
<soapenv:Body>
<n:RetLongResponse xmlns:n="http://tempuri.org/">
<n:RetLongResult>1</n:RetLongResult>
</n:RetLongResponse>
</soapenv:Body></soapenv:Envelope>
Request 2:
POST /axis2/services/BaseDataTypesDocLitWService HTTP/1.1
User-Agent: Axis2/C
SOAPAction: "http://tempuri.org/IBaseDataTypesDocLitW/RetULong"
Content-Length: 507
Content-Type: text/xml;charset=UTF-8
Host: 127.0.0.1:8080
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:To>http://localhost:8080/axis2/services/BaseDataTypesDocLitWService</wsa:To>
<wsa:Action>http://tempuri.org/IBaseDataTypesDocLitW/RetULong</wsa:Action>
<wsa:MessageID>1fc1a399-21c1-4b69-91ad-fc7d2c1cfbb7</wsa:MessageID>
</soapenv:Header>
<soapenv:Body>
<n:RetULong xmlns:n="http://tempuri.org/">
<n:inULong>2</n:inULong>
</n:RetULong>
</soapenv:Body></soapenv:Envelope>
Response2:
HTTP/1.1 200 OK
Content-Type: text/xml;charset=UTF-8
Content-Length: 701
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">
<wsa:Action>http://tempuri.org/IBaseDataTypesDocLitW/RetULong</wsa:Action>
<wsa:From>
<wsa:Address>http://localhost:8080/axis2/services/BaseDataTypesDocLitWService</wsa:Address>
</wsa:From>
<wsa:MessageID>b0cee22e-73f4-470a-8eb0-dc7ad0d03b02</wsa:MessageID>
<wsa:RelatesTo wsa:RelationshipType="http://www.w3.org/2005/08/addressing/reply">1fc1a399-21c1-4b69-91ad-fc7d2c1cfbb7</wsa:RelatesTo>
</soapenv:Header>
<soapenv:Body>
<n:RetULongResponse xmlns:n="http://tempuri.org/">
<n:RetULongResult>3</n:RetULongResult>
</n:RetULongResponse>
</soapenv:Body></soapenv:Envelope>
Hope this is correct and that we can close this JIRA.
Regards,
Senaka
> Support for uint64_t, int64_t required at codegen level
> -------------------------------------------------------
>
> Key: AXIS2C-964
> URL: https://issues.apache.org/jira/browse/AXIS2C-964
> Project: Axis2-C
> Issue Type: Improvement
> Components: code generation, wsdl2c tool
> Reporter: Senaka Fernando
> Fix For: 1.3.0
>
> Attachments: case12.zip, case12.zip, win_screen_shot_1.jpg
>
>
> Support for uint64_t, int64_t required at codegen level. I have added support at util level and fixed AXIS2C-919. Hope we can add this to the codegen tool too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Updated: (AXIS2C-964) Support for uint64_t, int64_t required
at codegen level
Posted by "Dimuthu Gamage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dimuthu Gamage updated AXIS2C-964:
----------------------------------
Attachment: case12.zip
Please check now, I did the change, int64_t use strtol and uint64_t use strtoul
> Support for uint64_t, int64_t required at codegen level
> -------------------------------------------------------
>
> Key: AXIS2C-964
> URL: https://issues.apache.org/jira/browse/AXIS2C-964
> Project: Axis2-C
> Issue Type: Improvement
> Components: code generation, wsdl2c tool
> Reporter: Senaka Fernando
> Fix For: 1.3.0
>
> Attachments: case12.zip, case12.zip, win_screen_shot_1.jpg
>
>
> Support for uint64_t, int64_t required at codegen level. I have added support at util level and fixed AXIS2C-919. Hope we can add this to the codegen tool too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXIS2C-964) Support for uint64_t, int64_t
required at codegen level
Posted by "Dimuthu Gamage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567340#action_12567340 ]
Dimuthu Gamage commented on AXIS2C-964:
---------------------------------------
+1 for the new define
Yea the int cast was a terrible mistake, I corrected it in the svn.
> Support for uint64_t, int64_t required at codegen level
> -------------------------------------------------------
>
> Key: AXIS2C-964
> URL: https://issues.apache.org/jira/browse/AXIS2C-964
> Project: Axis2-C
> Issue Type: Improvement
> Components: code generation, wsdl2c tool
> Reporter: Senaka Fernando
> Fix For: 1.3.0
>
> Attachments: case12.zip, case12.zip, win_screen_shot_1.jpg
>
>
> Support for uint64_t, int64_t required at codegen level. I have added support at util level and fixed AXIS2C-919. Hope we can add this to the codegen tool too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXIS2C-964) Support for uint64_t, int64_t
required at codegen level
Posted by "Senaka Fernando (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567345#action_12567345 ]
Senaka Fernando commented on AXIS2C-964:
----------------------------------------
Hi Dimuthu,
I have added four new constants, to the util layer. Hope you can make use of these.
1. AXIS2_PRINTF_FORMAT_INT64
2. AXIS2_PRINTF_FORMAT_UINT64
3. AXIS2_PRINTF_FORMAT_INT32
4. AXIS2_PRINTF_FORMAT_UINT32
Regards,
Senaka
> Support for uint64_t, int64_t required at codegen level
> -------------------------------------------------------
>
> Key: AXIS2C-964
> URL: https://issues.apache.org/jira/browse/AXIS2C-964
> Project: Axis2-C
> Issue Type: Improvement
> Components: code generation, wsdl2c tool
> Reporter: Senaka Fernando
> Fix For: 1.3.0
>
> Attachments: case12.zip, case12.zip, win_screen_shot_1.jpg
>
>
> Support for uint64_t, int64_t required at codegen level. I have added support at util level and fixed AXIS2C-919. Hope we can add this to the codegen tool too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Issue Comment Edited: (AXIS2C-964) Support for uint64_t,
int64_t required at codegen level
Posted by "Senaka Fernando (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567339#action_12567339 ]
senakafdo edited comment on AXIS2C-964 at 2/9/08 10:18 AM:
-----------------------------------------------------------------
Hi Dimuthu,
I just figured out the tweak in printing these types. I think we'll need a new constant rather than a function in the util layer as it is,
1. %I64u for windows
2. %llu for Linux
for uint64_t. Similarly we'll have to use the types,
1. %I64d for windows
2. %lld for Linux
for int64_t.
I will have this ready by tonight, under the names AXIS2_PRINTF_FORMAT_INT64 and AXIS2_PRINTF_FORMAT_UINT64
Also please remove that (int) cast.
Regards,
Senaka
was (Author: senakafdo):
Hi Dimuthu,
I just figured out the tweak in printing these types. I think we'll need a new constant rather than a function in the util layer as it is,
1. %I64u for windows
2. %llu for Linux
for uint64_t. Similarly we'll have to use the types,
1. %I64d for windows
2. %lld for Linux
for int64_t.
I will have this ready by tonight, under the names AXIS2_PRINTF_FORMAT_INT64 and AXIS2_PRINTF_FORMAT_UINT64
Regards,
Senaka
> Support for uint64_t, int64_t required at codegen level
> -------------------------------------------------------
>
> Key: AXIS2C-964
> URL: https://issues.apache.org/jira/browse/AXIS2C-964
> Project: Axis2-C
> Issue Type: Improvement
> Components: code generation, wsdl2c tool
> Reporter: Senaka Fernando
> Fix For: 1.3.0
>
> Attachments: case12.zip, case12.zip, win_screen_shot_1.jpg
>
>
> Support for uint64_t, int64_t required at codegen level. I have added support at util level and fixed AXIS2C-919. Hope we can add this to the codegen tool too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXIS2C-964) Support for uint64_t, int64_t
required at codegen level
Posted by "Senaka Fernando (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567339#action_12567339 ]
Senaka Fernando commented on AXIS2C-964:
----------------------------------------
Hi Dimuthu,
I just figured out the tweak in printing these types. I think we'll need a new constant rather than a function in the util layer as it is,
1. %I64u for windows
2. %llu for Linux
for uint64_t. Similarly we'll have to use the types,
1. %I64d for windows
2. %lld for Linux
for int64_t.
I will have this ready by tonight, under the names AXIS2_PRINTF_FORMAT_INT64 and AXIS2_PRINTF_FORMAT_UINT64
Regards,
Senaka
> Support for uint64_t, int64_t required at codegen level
> -------------------------------------------------------
>
> Key: AXIS2C-964
> URL: https://issues.apache.org/jira/browse/AXIS2C-964
> Project: Axis2-C
> Issue Type: Improvement
> Components: code generation, wsdl2c tool
> Reporter: Senaka Fernando
> Fix For: 1.3.0
>
> Attachments: case12.zip, case12.zip, win_screen_shot_1.jpg
>
>
> Support for uint64_t, int64_t required at codegen level. I have added support at util level and fixed AXIS2C-919. Hope we can add this to the codegen tool too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Resolved: (AXIS2C-964) Support for uint64_t, int64_t
required at codegen level
Posted by "Senaka Fernando (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Senaka Fernando resolved AXIS2C-964.
------------------------------------
Resolution: Fixed
Assignee: Senaka Fernando
Resolving Issue as it is fixed.
> Support for uint64_t, int64_t required at codegen level
> -------------------------------------------------------
>
> Key: AXIS2C-964
> URL: https://issues.apache.org/jira/browse/AXIS2C-964
> Project: Axis2-C
> Issue Type: Improvement
> Components: code generation, wsdl2c tool
> Reporter: Senaka Fernando
> Assignee: Senaka Fernando
> Fix For: 1.3.0
>
> Attachments: case12.zip, case12.zip, case12_new.zip, win_screen_shot_1.jpg
>
>
> Support for uint64_t, int64_t required at codegen level. I have added support at util level and fixed AXIS2C-919. Hope we can add this to the codegen tool too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXIS2C-964) Support for uint64_t, int64_t
required at codegen level
Posted by "Senaka Fernando (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567403#action_12567403 ]
Senaka Fernando commented on AXIS2C-964:
----------------------------------------
Hi Dimuthu,
I just followed the convention used by AXIS2_ATOI(), well you are free to use either of the two, either the all caps version or the other. So I believe it is better to have both.
I will test this on windows and let you know soon.
Regards,
Senaka
> Support for uint64_t, int64_t required at codegen level
> -------------------------------------------------------
>
> Key: AXIS2C-964
> URL: https://issues.apache.org/jira/browse/AXIS2C-964
> Project: Axis2-C
> Issue Type: Improvement
> Components: code generation, wsdl2c tool
> Reporter: Senaka Fernando
> Fix For: 1.3.0
>
> Attachments: case12.zip, case12.zip, case12_new.zip, win_screen_shot_1.jpg
>
>
> Support for uint64_t, int64_t required at codegen level. I have added support at util level and fixed AXIS2C-919. Hope we can add this to the codegen tool too.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org