Right!
> Hello!
>
> I'm using EJB in combination to SOAP. I'm not able to import SOAP components
> in my EJB class, because:
> then I have to put soap.jar into the classpath of weblogic, otherwise a
> deployment of the EJB is impossible.
> Putting the soapr.jar in the weblogic classpath leads to errors in the
> soap-webapplication, because the soap.jar
> is not loaded by the same classloader than the web-inf/lib and
> web-inf/classes stuff...
>
> So that means, If I want to translate SOAPExceptions I have to create this
> thin service layer.
> Is that right?
>
> Michael
>
> > -----Original Message-----
> > From: Micael Ericsson (QIN) [SMTP:[EMAIL PROTECTED]]
> > Sent: Monday, September 10, 2001 12:45 PM
> > To: '[EMAIL PROTECTED]'
> > Subject: RE: Exception handling
> >
> > You could create SOAP service classes as front-ends to existing ones. In
> > your front-end classes you call existing logic, capture exceptions and
> > throws new SOAPException. IMO a service class should be as thin as
> > possible. All business core should definitely be in a separate layer -
> > think of the service as a UI.
> >
> > /Micael E.
> >
> > -----Original Message-----
> > From: Vikram Rajan [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, September 10, 2001 11:32 AM
> > To: '[EMAIL PROTECTED]'
> > Subject: RE: Exception handling
> >
> >
> > That would really hamper re-usability wouldnt it?
> >
> > what if i needed to web service enable existing components? it would mean
> > (atleast) re-writing all exception classes.
> >
> > there must be a better way ... if there isnt ... well ... then it should
> > be
> > added.
> >
> > - vikram rajan
> >
> > > ----------
> > > From: Micael Ericsson (QIN)
> > > Reply To: [EMAIL PROTECTED]
> > > Sent: Monday, September 10, 2001 2:52 PM
> > > To: '[EMAIL PROTECTED]'
> > > Subject: RE: Exception handling
> > >
> > > You should only throw SOAPException's from Java class representing a
> > SOAP
> > > service. SOAPExceptions are translated into SOAP Fault codes and text.
> > You
> > > can also incorporate your 'UnknownUserException' into a SOAPException.
> > >
> > > /Micael E.
> > >
> > > -----Original Message-----
> > > From: Vikram Rajan [mailto:[EMAIL PROTECTED]]
> > > Sent: Monday, September 10, 2001 11:14 AM
> > > To: '[EMAIL PROTECTED]'
> > > Subject: Exception handling
> > >
> > >
> > > Doesnt Apache SOAP toolkit handle application-level exceptions?
> > >
> > > i.e., if I have a method with the following signature:
> > >
> > > public User getUserDetails(String id) throws UnknownUserException
> > >
> > > and the UnknownUserException is thrown by the method, shouldn't this
> > > exception be wrapped into a Fault object and sent across to the client?
> > > ...
> > > doesnt seem to be happening. All I get is a "null".
> > >
> > > Am using Apache SOAP 2.1 with Weblogic.
> > >
> > > any ideas? am i missing something?
> > >
> > > - vikram rajan
> > >
> >
> >
> >
> ---------------------------------------------------------------------
> This message is intended for the addressee or its representative only. Any
> form of unauthorized use, publication, reproduction, copying or disclosure
> of the content of this e-mail is not permitted. If you are not the intended
> recipient of this e-mail message and its contents, please notify the sender
> immediately and delete this message and all its attachments subsequently.
--
Andreas Ullmann
[EMAIL PROTECTED]
MATHEMA AG
Nägelsbachstraße 25b
91052 Erlangen
Telefon 09131/8903-0
Telefax 09131/8903-55
www.mathema.de
