Re: How to get more detailed exception information from a Spring implementation?
Thanks for your remind. I will do that the next time.
And I still have a question on the exception handling. As you know, the
actural exception is wrapped in many wrapper exceptions. So the exception
process will have some problems to select the right exception handler.
Is the following the best practise for exception handling scenario:
try {
// sca method call
} catch (RMIException e) {
if (e.getCause().getCause() instanceof NotEnoughMoney) {
System.out.println(do not have enough money!);
} else {
System.out.println(other exception);
}
}
Or do we have any best practise for handling the wrapped application
exception?
Regards,
Yang Sun
2007/9/26, Jean-Sebastien Delfino [EMAIL PROTECTED]:
Sun Yang wrote:
Hi, Raymond:
Thanks for your confirmation. I will do that when I back to work
tomorrow.
Regards,
Yang Sun
If you want you can also submit a small patch in the JIRA, looks like
it's just a matter of changing the SpringInvocationException(String msg)
constructor to SpringInvocationException(Exception cause) and use that
new constructor in a few places in SpringInvoker :)
If you try that and it works for you it'll be easy to get that fix in.
--
Jean-Sebastien
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Reg: Big-Bank Demo
Hi, Can someone please clear my doubts? 1. In the bigbank-account demo the Account Component is refering to AccountData Component in the same Composite then why do we have two composite files(BigBank.composite AccountData.composite) can some one explain me? 2. If we are referring to a local component and sending the input as a String and the response is an Object then do we have to serialize the object? Thanks Regards, Ashwini Kumar
RE: Passing context from ws binding to a component implementation
The SOAP headers mapped to WSDL message parts are part of the contract and could be received in the component. The use case I was trying to provide was about the message parts that not specified in the abstract wsdl - much similar to the standard ones like wsse and wsa except the modules processing these 'custom' headers are not part of the infrastructure. As an example, a company defines a liceneseKey structure as a custom header, which is optionally expected in each message but it is not a part of the WSDL contract. This header will be specified differently for the binding used, e.g., SOAP binding will include it as a SOAP header, and JMS binding may provide it as an application property. This information needs to be propagated to the component providing the service or any outbound references. Generalization of this use case could be used to achieve transport bridging or protocol conversion. e.g., mapping SOAP 1.1 message to SOAP 1.2, mapping SOAP/HTTP message to SOAP/JMS etc. -Original Message- From: Jean-Sebastien Delfino [mailto:[EMAIL PROTECTED] Sent: Friday, September 28, 2007 5:25 PM To: tuscany-user@ws.apache.org Subject: Re: Passing context from ws binding to a component implementation One question: On 9/25/07, Dinesh Shahane [EMAIL PROTECTED] wrote: I want to process transport headers and custom soap headers in my component, what is the best way to propagate this information? There may be different options depending on SOAP headers you're interested in, so... Which SOAP headers are you interested in? :) addressing? security? anything else? what kind of custom headers? Do you need to just get some information out of incoming headers or do you need to produce headers as well? Do you need to propagate headers unchanged through your application in some kind of relay component? WSDL can map headers to message parts [1], making them actual parts of the business interface. You said earlier in this thread that you cannot alter the WSDL contract. How about adding that mapping to the WSDL without actually impacting the wire protocol at all. Is your WSDL really frozen? Thanks. [1] http://www.w3.org/TR/wsdl#_soap:header -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Passing context from ws binding to a component implementation
Jean Sebastian, This kind of functionality sounds in awful lot like some of the policy stuff we are talking about a couple of weeks ago... Jeff From: Dinesh Shahane [mailto:[EMAIL PROTECTED] Sent: Sat 2007-09-29 13:21 To: tuscany-user@ws.apache.org Subject: RE: Passing context from ws binding to a component implementation The SOAP headers mapped to WSDL message parts are part of the contract and could be received in the component. The use case I was trying to provide was about the message parts that not specified in the abstract wsdl - much similar to the standard ones like wsse and wsa except the modules processing these 'custom' headers are not part of the infrastructure. As an example, a company defines a liceneseKey structure as a custom header, which is optionally expected in each message but it is not a part of the WSDL contract. This header will be specified differently for the binding used, e.g., SOAP binding will include it as a SOAP header, and JMS binding may provide it as an application property. This information needs to be propagated to the component providing the service or any outbound references. Generalization of this use case could be used to achieve transport bridging or protocol conversion. e.g., mapping SOAP 1.1 message to SOAP 1.2, mapping SOAP/HTTP message to SOAP/JMS etc. -Original Message- From: Jean-Sebastien Delfino [mailto:[EMAIL PROTECTED] Sent: Friday, September 28, 2007 5:25 PM To: tuscany-user@ws.apache.org Subject: Re: Passing context from ws binding to a component implementation One question: On 9/25/07, Dinesh Shahane [EMAIL PROTECTED] wrote: I want to process transport headers and custom soap headers in my component, what is the best way to propagate this information? There may be different options depending on SOAP headers you're interested in, so... Which SOAP headers are you interested in? :) addressing? security? anything else? what kind of custom headers? Do you need to just get some information out of incoming headers or do you need to produce headers as well? Do you need to propagate headers unchanged through your application in some kind of relay component? WSDL can map headers to message parts [1], making them actual parts of the business interface. You said earlier in this thread that you cannot alter the WSDL contract. How about adding that mapping to the WSDL without actually impacting the wire protocol at all. Is your WSDL really frozen? Thanks. [1] http://www.w3.org/TR/wsdl#_soap:header -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - ** Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s), are confidential, and may be privileged. If you are not the intended recipient, you are hereby notified that any review, retransmission, conversion to hard copy, copying, circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, and delete this message and any attachments from your system. Thank you. Information confidentielle: Le présent message, ainsi que tout fichier qui y est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; il est de nature confidentielle et peut constituer une information privilégiée. Nous avertissons toute personne autre que le destinataire prévu que tout examen, réacheminement, impression, copie, distribution ou autre utilisation de ce message et de tout fichier qui y est joint est strictement interdit. Si vous n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur par retour de courriel et supprimer ce message et tout document joint de votre système. Merci. ** --===0383574376==-- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SDO CPP - Help with retrieving the new DataObject set on a Property
Hi, I need to do the following: I have a settingList of a modified dataObject, there is a setting on it that isSet=true or isNull=true, meaning that there was no previous DataObject set on that property, and I want to retrieve the new DataObject set on it. I can do it invoking dataObject-getDataObject(setting.getProperty()), but if the setting.getProperty() is many=true, I need to use dataObject-getList( setting.getProperty()), however a list of DataObject is returned and not only one, so how can I know which DataObject was inserted on this list? Adriano Crestani
