0
Masyado kc mahaba ung codes ska prone to error kung i enumerate nmin every exception type.
Anyway, why dont you try posting to www.csharp-station.com? doon sasagutin ka talaga ni joe mayo. He's the best pare!
eto pa ung iba:
www.gotdotnet.com
www.dotnetforums.com
www.dotnetforums.net
www.csharphelp.com
try ko ung ipinost mong thread.
Regards,
Chris
0 Hi Chris,
Walang anuman.
But I still don't get it, why do all the trouble of instantiating the actor exception when you just need use that property from the soapexception?
Anyway its your code so probably you know better.
Actually palagi ako www.c-sharpcorner.com, ngayon ngayon lang ako napadpad dito sa forum, me mga tanong ako wala naman sumasagot so I end up doing the experiments myself.
Sure thing, I would gladly exchange any info I can, its a lot faster to learn that way.
Hanggang sa muli,
Tikbalang
PS check mo yon post ko dun sa thread at security baka my idea kayo thanks.
0 Hi Tikbalang,
Nakuha namin!!!
We have just made a new soap exception handler!
From SoapException Message String, we concatenated the type of assemblyname.
Then we load all the assembly by using this code from AppDomain:
assemblyArray = AppDomain.CurrentDomain.GetAssemblies();
and then we created a nested loop comparing the type of each assembly fullname to the concatenated string(which is also the type of exception).
Then we created an instance of that exception then throw it as exception!!!
Thank U for the support! It truly helps!!
Minsan Email mo ko para share ng new knowledges ok!
Regards,
Chris
chrisaldi20@yahoo.com
0 Hi chris,
Nope, wala kaming lahi ng aswang, the name just stuck with me ever since I was in college.
Well for one thing, is your project devoted entirely to building a generic exception handler for all your applcations? If so then you may really need to consider the soap exception handlers you've read.
But if the routine you've posted above is for debugging or general-purpose error handling then I suggest you break-up the code that is between your try catch block before you even call the createInstance block.
Some additional stuff:
- are you calling a web service method via SOAP?
- is the XML returned formatted correctly?
- what's the need to instantiate the fouling objects?
- if you are only concerned about who caused the error have you tried using the actor, code and details property of the soapexcetion?
Unfortunately the code above does not tell much because it does not tell what objects fouled.
Hope that helps,
Tikbalang
0 Actually, I am trapping for unexpected errors from UI. Like for example TimeOut Expired...
because it returns to UI as a SoapException Error. I want it to be catch in general. One solution I made is here:
In here I created an Instance of an object which comes from concatenated Assembly name from error message. I want to retrieved the real exception error and not the soapexception error. But it has a problem, it returns an error "HRESULT has been returned from a call to a COM Component!"
==========================================================
catch(Exception err)
{
throw (Exception)CreateObjectInstance(err);
}
private object CreateObjectInstance(Exception err)
{
Object obj;
Assembly[] assemblyArray;
string str = err.Message.Substring(err.Message.IndexOf("---> ") + 5,
err.Message.IndexOf(" (") - err.Message.IndexOf("---> ") - 5);
assemblyArray = new Assembly[AppDomain.CurrentDomain.GetAssemblies().Length];
assemblyArray = AppDomain.CurrentDomain.GetAssemblies();
foreach(Assembly assembly in assemblyArray)
{
Type[] mytypes = assembly.GetTypes();
foreach(Type t in mytypes)
{
if(t.FullName == str)
{
obj = Activator.CreateInstance(t)
return obj;
}
}
}
return null;
}
===============================================
I have read documents about handling soapexception errors but it is requires a lot of program codes.
Hope u help me here....
Regards,
Chris
PS.
May lahi ba kayong aswang?
la lang...
0 Tabalits pogi,
For one thing your description is a bit vague. What I could suggest is your breakdown your project into smaller chunks.
1. Start with the UI. Make sure all your validations are correct. If you need any data hard code them first.
2. Once your sure that the client side validations are correct check the webservice. Maybe the web service requires some SOAP authentication check with the web service publisher.
3. Can u post a sample code that we can look at?
Hanggang sa muli,
Tikbalang