[
https://issues.apache.org/jira/browse/AXIS2C-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567642#action_12567642
]
senakafdo edited comment on AXIS2C-966 at 2/11/08 6:14 AM:
-----------------------------------------------------------------
Also, Bill,
I have used this approach to covey messages to/from client to transport, when I
was working with authentication.
1. If it is uni-directional, and if it is from client -> transport, the popular
choice is to set an option. I think we have many examples in options.c
2. If it is uni-directional, and if it is from transport -> client, set it to
the message context and use service client to extract the info from the message
context and expose it through another method.
3. If it is bi-directional, you can use the above two methods in combination.
4. There may be situations where setting something in the service client is
more efficient than setting an option and passing it to the service client.
This comes in handy especially when the conversation involves maintaining state.
I hope this may help you with informing Upper Layers about the character
encoding used.
Regards,
Senaka
was (Author: senakafdo):
Also, Bill,
I have used this approach to covey messages to from client to transport, when i
was working with authentication.
1. If it is uni-directional, and if it is from client -> transport, the popular
choice is to set an option. I think we have many examples in options.c
2. If it is uni-directional, and if it is from transport -> client, set it to
the message context and use service client to extract the info from the message
context and expose it through another method.
3. If it is bi-directional, you can use the above two methods in combination.
4. There may be situations where setting something in the service client is
more efficient than setting an option and passing it to the service client.
This comes in handy especially when the conversation involves maintaining state.
I hope this may help you with informing Upper Layers about the character
encoding used.
Regards,
Senaka
> Guththila has no support for XML declarations
> ---------------------------------------------
>
> Key: AXIS2C-966
> URL: https://issues.apache.org/jira/browse/AXIS2C-966
> Project: Axis2-C
> Issue Type: Bug
> Components: guththila
> Affects Versions: 1.3.0
> Reporter: Senaka Fernando
> Assignee: Senaka Fernando
> Fix For: 1.3.0
>
>
> Guththila has no support for XML declarations. Bill, pointed this out in an
> e-mail sent to the AXIS2C-dev list. It is required that Guththila understands
> the XML declaration elements and simply do not treat it as an error.
> Regards,
> Senaka
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
