Welcome!

Weblogic Authors: Yeshim Deniz, Elizabeth White, Michael Meiner, Michael Bushong, Avi Rosenthal

Related Topics: Weblogic

Weblogic: Article

Integrating an ASP.NET Application with J2EE PART 2

Platform interoperability

In Part 1 of this two-part article I discussed interoperability between .NET and Weblogic 8.1 and issues that arise when transferring data between Web serivces. In Part 2 I will cover some advanced issues: SOAP exception handling, uploading binary information via Web services, and application navigation and workflow.

SOAP Exception Handling
In non-Web Services environments, we're used to building a hierarchy of exceptions and throwing the appropriate exception to indicate the correct feedback to the client. For example, we can define an application exception called "UserNotLoggedInException" (that extends System.ApplicationException) to indicate to the caller that the application has failed because the user isn't logged into the application properly. When the calling method catches this exception, it's aware of the type of error that's occurred.

Exception handling in Web Services differs from the structured exception handling offered in Java or C#, where a developer puts code that can cause an exception in a try/catch clause. Exceptions are caught in the catch clause or bubble up to the calling method if not handled in one of the catch clauses. When an exception is thrown to a calling method, the method understands the data type of the exception and can deal with it accordingly.

With Web Services, exception handling gets a bit more complicated. All exceptions thrown in a Web Service are wrapped by .NET (or WebLogic) as a SoapException. A SoapException generates a SoapResponse that replaces the body of the SOAP message with a SoapFault element. A SoapFault is an XML element that contains elements with information indicating the SoapFault type, an error number, an error message, and an error source. The SoapFault also indicates a URI, which is usually the method that generated the exception. Table 1 displays the layout of a SoapFault. The SoapFault element provides information to the calling method about the exception that occurred.

.NET wraps native exceptions in a SoapException because the Web Service client doesn't understand the native type of the exceptions that occurred in the Web Service. In the last example, a client application calling a Web Service that threw a UserNotLoggedInException exception wouldn't understand this exception class and wouldn't know how to handle it properly. So a Web Service client will always need to handle a SoapException and may need to process the exception further to determine the root of the problem.

The faultcode element is usually set to either "client" or "server." The faultcode is the mechanism that a Web Service can use to indicate to the caller if the source of the error was a server error or a client error. For example, if the application wasn't able to connect to the database, the SoapFault should indicate a (namespace qualified) faultcode element of "server." It indicates that the server encountered an error and the error wasn't dependent on client input. In this case, you would log the error on the server, and return an incident number to the client. The client would display a generic user-friendly error page that indicates to the user that an error occurred and provide an incident number to contact the help desk. The help desk could then review the incident details and attempt to diagnose the problem.

When an error occurs that's dependant on client input, additional processing has to occur. An example of this occurs when the client attempts to access a resource when they are not logged in. In this case, it doesn't make sense to display a generic user-friendly error page; we'd like to let the user know the cause of the error so he can correct the situation. In this case, we would like to redirect the user to a login page so he can be authenticated. A similar (and more likely) scenario occurs when a user attempts to violate a foreign key relationship. For example, a user may try to delete a client who has orders. In this case, we'd like to notify the client via a message that the client can't be deleted because they have dependant data (orders). In both cases, we need to provide additional processing.

To provide additional information to the Web Services client, we generate and throw a SoapException and set the SOAP fault type to "client." This overrides the generation of a default SoapException by .NET (or WebLogic) and returns our custom SoapException. By setting the faultcode to "client," we notify the caller that the error was caused by client input or action.

The SOAP specification indicates that a SoapFault contains a "details" element. The contents of the details element are left open to the developer to define the error information they'd like to communicate to the client. The first step is to define an XML schema to declare the structure of the SoapFault detail element. This is the contract between the Web Service and client that indicates the data that will be passed when a custom SoapException is thrown.

When an exception occurs, we want to pass a message to display to the client. We also want to pass the server exception message and a stack trace to log for assistance in diagnosing the production problems. Listing 1 shows the XML schema we defined to pass this information via a custom SoapException. Listing 2 shows the SoapException XML generated.

In our sample application, we throw a custom SoapException from a WebLogic Web Service, catch, and process it in an ASP.NET application. The throwClientSoapException method throws a custom exception. The code for the throwClientSoapException method is shown in Listing 3.

The code calls the buildSoapFaultException method in the SOAPUtil class. This is a static helper method that builds the custom SoapException (see Listing 4).

The SOAP_NAMESPACE is defined as a Java constant:


public static final String SOAP_NAMESPACE =
"http://www.justwebsolutions.com/articles";
The ASP.NET client code catches the SoapException and then creates a DataSet, and uses the SoapExceptionDetail.xsd schema we defined to read the XML schema into the DataSet (via the ReadXmlSchema method).

//Get SoapExceptionDetail.xsd full path
string schemaRelativePath = "../schemas/SoapExceptionDetail.xsd";
string schemaFullPath =
HttpContext.Current.Server.MapPath(schemaRelativePath);

//Read the Schema into the DataSet
dsError.ReadXmlSchema(schemaFullPath);

More Stories By Blair Taylor

Blair Taylor is president of JustWebSolutions.com, a Canadian company specializing in the architecture and development of distributed systems. Blair has authored several publications covering client-server and distributed technologies and is certified in both Java and .NET technologies. Blair can be reached via e-mail at [email protected] or at www.justwebsolutions.com.

Comments (1) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
mo 06/28/05 03:43:02 AM EDT

Good article.
I completely support the article approach when dealing with simple text based services. Web services is a satisfying solution . Unfortunately , I believe that binary data shouldn't be handled using Web services. It's just not up to it and the writer have proved it when dealing with .NET exceptions. There are better solutions for such cases. I can think of at least one solution that converts .NET binary into pure Java binary: http://dev.mainsoft.com/ but I'm sure there are more.

IoT & Smart Cities Stories
Digital Transformation and Disruption, Amazon Style - What You Can Learn. Chris Kocher is a co-founder of Grey Heron, a management and strategic marketing consulting firm. He has 25+ years in both strategic and hands-on operating experience helping executives and investors build revenues and shareholder value. He has consulted with over 130 companies on innovating with new business models, product strategies and monetization. Chris has held management positions at HP and Symantec in addition to ...
DXWorldEXPO LLC announced today that Big Data Federation to Exhibit at the 22nd International CloudEXPO, colocated with DevOpsSUMMIT and DXWorldEXPO, November 12-13, 2018 in New York City. Big Data Federation, Inc. develops and applies artificial intelligence to predict financial and economic events that matter. The company uncovers patterns and precise drivers of performance and outcomes with the aid of machine-learning algorithms, big data, and fundamental analysis. Their products are deployed...
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
The challenges of aggregating data from consumer-oriented devices, such as wearable technologies and smart thermostats, are fairly well-understood. However, there are a new set of challenges for IoT devices that generate megabytes or gigabytes of data per second. Certainly, the infrastructure will have to change, as those volumes of data will likely overwhelm the available bandwidth for aggregating the data into a central repository. Ochandarena discusses a whole new way to think about your next...
CloudEXPO | DevOpsSUMMIT | DXWorldEXPO are the world's most influential, independent events where Cloud Computing was coined and where technology buyers and vendors meet to experience and discuss the big picture of Digital Transformation and all of the strategies, tactics, and tools they need to realize their goals. Sponsors of DXWorldEXPO | CloudEXPO benefit from unmatched branding, profile building and lead generation opportunities.
All in Mobile is a place where we continually maximize their impact by fostering understanding, empathy, insights, creativity and joy. They believe that a truly useful and desirable mobile app doesn't need the brightest idea or the most advanced technology. A great product begins with understanding people. It's easy to think that customers will love your app, but can you justify it? They make sure your final app is something that users truly want and need. The only way to do this is by ...
Cell networks have the advantage of long-range communications, reaching an estimated 90% of the world. But cell networks such as 2G, 3G and LTE consume lots of power and were designed for connecting people. They are not optimized for low- or battery-powered devices or for IoT applications with infrequently transmitted data. Cell IoT modules that support narrow-band IoT and 4G cell networks will enable cell connectivity, device management, and app enablement for low-power wide-area network IoT. B...
The hierarchical architecture that distributes "compute" within the network specially at the edge can enable new services by harnessing emerging technologies. But Edge-Compute comes at increased cost that needs to be managed and potentially augmented by creative architecture solutions as there will always a catching-up with the capacity demands. Processing power in smartphones has enhanced YoY and there is increasingly spare compute capacity that can be potentially pooled. Uber has successfully ...
SYS-CON Events announced today that CrowdReviews.com has been named “Media Sponsor” of SYS-CON's 22nd International Cloud Expo, which will take place on June 5–7, 2018, at the Javits Center in New York City, NY. CrowdReviews.com is a transparent online platform for determining which products and services are the best based on the opinion of the crowd. The crowd consists of Internet users that have experienced products and services first-hand and have an interest in letting other potential buye...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...