You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Tom Jordahl <to...@macromedia.com> on 2002/09/07 00:42:29 UTC
RE: Handlers and SOAP message re-writing
Rob,
Great work tracking this down. If you send code to axis-dev
I am sure one of us will pick it up and submit it!
--
Tom Jordahl
-----Original Message-----
From: Allegar Robert [mailto:allegar_robert@bah.com]
Sent: Friday, September 06, 2002 2:48 PM
To: axis-user@xml.apache.org
Subject: RE: Handlers and SOAP message re-writing
Ricky,
That helped quite a bit -- thanks. I tracked down the problem. First, the
reason I wasn't able to see the .addHeader method on the SOAPEnvelope object
is because the class I'm in (a holdover) imported
javax.xml.soap.SOAPEnvelope. So when I made a call to
SOAPEnvelope envelope = msgContext.getRequestMessage().getSOAPEnvelope();
It was really returning a javax.xml.soap.SOAPEnvelope object not an
org.apache.axis.message.SOAPEnvelope. I didn't have to cast it, nor did I
get compile time errors because the Axis IMPL is a subclass of the Sun
interface. As a result the method addHeader() wasn't found.
So since I couldn't use addHeader(), the road I was going down was to call
addChildElement on the returned SOAPEnvelope object -- which in this case
was javax.xml.soap.SOAPEnvelope -- but the implementation is actually in the
parent class of org.apache.axis.message.SOAPEnvelope:
org.apache.axis.message.MessageElement.
Now, I've looked through the source code for both the axis MessageElement
object and the SOAPEnvelope object, and it seems like the code for
addChildElement is stubbed out. However, if I use the addChildElement() call
instead of the addHeader() call, the element is not appended and my
modification doesn't take -- no error is thrown but the SOAP request isn't
changed.
The bug here is that both the org.apache.axis.message.SOAPHeader class and
the org.apache.axis.message.SOAPBody class don't override the
addChildElement of their parent. If you look at the code for both of these
classes, you'll see that they have a addHeaderElement() and addBodyElement()
respectively. SOAPEvenlope has a similar behavior. But none of the 3
sub-classes override the parent class's method so the header, envelope or
body is never really changed.
The solution to this (bug?) is for the SOAPHeader, SOAPBody and SOAPEnvelope
classes to override the addChildElement of the parent so that the element
doesn't go in the generic "children" ArrayList in the MessageElement parent
class but get added to the nested "bodyElements" Vector (in SOAPBody) and
"headers" Vector (in SOAPHeader). I'd be happy to help the Axis developers
with this change if necessary.
Regards,
Rob
-----Original Message-----
From: Ricky Ho [mailto:riho@cisco.com]
Sent: Friday, September 06, 2002 10:54 AM
To: axis-user@xml.apache.org
Subject: RE: Handlers and SOAP message re-writing
Following is my exact code based on AXIS beta 2
import org.apache.axis.*;
import org.apache.axis.handlers.*;
import org.apache.axis.message.*;
public class PutHeaderHandler extends BasicHandler {
public void invoke(MessageContext msgContext) throws AxisFault
{
try {
System.out.println(" -- PutHeaderHandler starts --");
System.out.println("Options are : " + getOptions());
SOAPEnvelope envelope =
msgContext.getRequestMessage().getSOAPEnvelope();
System.out.println("Request message is : " + envelope);
envelope.addHeader(new SOAPHeaderElement("TestNameSpace",
"isAuthenticated", new Boolean(true)));
System.out.println("Add header");
} catch (Exception e) {
throw AxisFault.makeFault(e);
}
}
}
Rgds, Ricky
Re: Handlers and SOAP message re-writing
Posted by Jean-Marc Taillant <ta...@bst.bsf.alcatel.fr>.
Hi Robert,
Do you know if there is any update?
Will the addHeader() method be implemented ?
when do you think that it will be available ( in a nightly build version?)
Best regards,
Jean Marc Taillant
----- Original Message -----
From: "Allegar Robert" <al...@bah.com>
To: <ax...@xml.apache.org>
Sent: Monday, September 09, 2002 5:01 PM
Subject: RE: Handlers and SOAP message re-writing
> Thanks for the fix -- It looks like that would do the trick. I would have
> made the change myself but I'm not sure how to bootstrap the process of
> sending changes to the committers. Do I just post them to axis-dev as
> attachments or is there a linux kernel-like 'patch' notation I should use?
>
> Rob
>
> -----Original Message-----
> From: Davanum Srinivas [mailto:dims@yahoo.com]
> Sent: Saturday, September 07, 2002 9:00 PM
> To: axis-dev@xml.apache.org; 'axis-user@xml.apache.org'
> Cc: 'axis-dev@xml.apache.org'; allegar_robert@bah.com
> Subject: RE: Handlers and SOAP message re-writing
>
>
> Rob,
>
> As part of fix for Bug #12357 i checked in a modified SOAPHeader
> file...Please check it out and
> let us know if this works for you, you can use a similar approach for the
> other files at need to
> be fixed and submit a patch...
>
> Thanks,
> dims
>
> --- Tom Jordahl <to...@macromedia.com> wrote:
> >
> > Rob,
> >
> > Great work tracking this down. If you send code to axis-dev
> > I am sure one of us will pick it up and submit it!
> >
> > --
> > Tom Jordahl
> >
> >
> > -----Original Message-----
> > From: Allegar Robert [mailto:allegar_robert@bah.com]
> > Sent: Friday, September 06, 2002 2:48 PM
> > To: axis-user@xml.apache.org
> > Subject: RE: Handlers and SOAP message re-writing
> >
> >
> > Ricky,
> > That helped quite a bit -- thanks. I tracked down the problem. First,
the
> > reason I wasn't able to see the .addHeader method on the SOAPEnvelope
> object
> > is because the class I'm in (a holdover) imported
> > javax.xml.soap.SOAPEnvelope. So when I made a call to
> > SOAPEnvelope envelope =
> msgContext.getRequestMessage().getSOAPEnvelope();
> >
> > It was really returning a javax.xml.soap.SOAPEnvelope object not an
> > org.apache.axis.message.SOAPEnvelope. I didn't have to cast it, nor did
I
> > get compile time errors because the Axis IMPL is a subclass of the Sun
> > interface. As a result the method addHeader() wasn't found.
> >
> > So since I couldn't use addHeader(), the road I was going down was to
call
> > addChildElement on the returned SOAPEnvelope object -- which in this
case
> > was javax.xml.soap.SOAPEnvelope -- but the implementation is actually in
> the
> > parent class of org.apache.axis.message.SOAPEnvelope:
> > org.apache.axis.message.MessageElement.
> >
> > Now, I've looked through the source code for both the axis
MessageElement
> > object and the SOAPEnvelope object, and it seems like the code for
> > addChildElement is stubbed out. However, if I use the addChildElement()
> call
> > instead of the addHeader() call, the element is not appended and my
> > modification doesn't take -- no error is thrown but the SOAP request
isn't
> > changed.
> >
> > The bug here is that both the org.apache.axis.message.SOAPHeader class
and
> > the org.apache.axis.message.SOAPBody class don't override the
> > addChildElement of their parent. If you look at the code for both of
these
> > classes, you'll see that they have a addHeaderElement() and
> addBodyElement()
> > respectively. SOAPEvenlope has a similar behavior. But none of the 3
> > sub-classes override the parent class's method so the header, envelope
or
> > body is never really changed.
> >
> > The solution to this (bug?) is for the SOAPHeader, SOAPBody and
> SOAPEnvelope
> > classes to override the addChildElement of the parent so that the
element
> > doesn't go in the generic "children" ArrayList in the MessageElement
> parent
> > class but get added to the nested "bodyElements" Vector (in SOAPBody)
and
> > "headers" Vector (in SOAPHeader). I'd be happy to help the Axis
developers
> > with this change if necessary.
> >
> > Regards,
> > Rob
> >
> >
> >
> >
> > -----Original Message-----
> > From: Ricky Ho [mailto:riho@cisco.com]
> > Sent: Friday, September 06, 2002 10:54 AM
> > To: axis-user@xml.apache.org
> > Subject: RE: Handlers and SOAP message re-writing
> >
> >
> > Following is my exact code based on AXIS beta 2
> >
> > import org.apache.axis.*;
> > import org.apache.axis.handlers.*;
> > import org.apache.axis.message.*;
> >
> > public class PutHeaderHandler extends BasicHandler {
> > public void invoke(MessageContext msgContext) throws AxisFault
> > {
> > try {
> > System.out.println(" -- PutHeaderHandler starts --");
> > System.out.println("Options are : " + getOptions());
> >
> > SOAPEnvelope envelope =
> > msgContext.getRequestMessage().getSOAPEnvelope();
> > System.out.println("Request message is : " + envelope);
> > envelope.addHeader(new
SOAPHeaderElement("TestNameSpace",
> > "isAuthenticated", new Boolean(true)));
> >
> > System.out.println("Add header");
> > } catch (Exception e) {
> > throw AxisFault.makeFault(e);
> > }
> > }
> > }
> >
> > Rgds, Ricky
>
>
> =====
> Davanum Srinivas - http://xml.apache.org/~dims/
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Finance - Get real-time stock quotes
> http://finance.yahoo.com
>
Re: Handlers and SOAP message re-writing
Posted by Steve Loughran <st...@iseran.com>.
----- Original Message -----
From: "Davanum Srinivas" <di...@yahoo.com>
To: <ax...@xml.apache.org>; <al...@bah.com>
Sent: Monday, September 09, 2002 7:58 AM
Subject: RE: Handlers and SOAP message re-writing
> Rob,
>
> 1. Post a bug at nagoya.apache.org/bugzilla.
> 2. Get latest cvs code.
> 3. Make changes necessary, make sure you run "build clean all-tests"
3a make the changes consistent in style, java version &c.
> 4. Run "cvs diff -u" from xml-axis/java directory.
> 5. Zipup output from step #4 and any other additional files.
> 6. Add Zip as attachment to bugzilla.
7. Add any unit test and doc patches to go alongside. Tests go a long way.
8. remind people again and again till the patch is committed.
RE: Handlers and SOAP message re-writing
Posted by Davanum Srinivas <di...@yahoo.com>.
Rob,
1. Post a bug at nagoya.apache.org/bugzilla.
2. Get latest cvs code.
3. Make changes necessary, make sure you run "build clean all-tests"
4. Run "cvs diff -u" from xml-axis/java directory.
5. Zipup output from step #4 and any other additional files.
6. Add Zip as attachment to bugzilla.
Thanks,
dims
--- Allegar Robert <al...@bah.com> wrote:
> Thanks for the fix -- It looks like that would do the trick. I would have
> made the change myself but I'm not sure how to bootstrap the process of
> sending changes to the committers. Do I just post them to axis-dev as
> attachments or is there a linux kernel-like 'patch' notation I should use?
>
> Rob
>
> -----Original Message-----
> From: Davanum Srinivas [mailto:dims@yahoo.com]
> Sent: Saturday, September 07, 2002 9:00 PM
> To: axis-dev@xml.apache.org; 'axis-user@xml.apache.org'
> Cc: 'axis-dev@xml.apache.org'; allegar_robert@bah.com
> Subject: RE: Handlers and SOAP message re-writing
>
>
> Rob,
>
> As part of fix for Bug #12357 i checked in a modified SOAPHeader
> file...Please check it out and
> let us know if this works for you, you can use a similar approach for the
> other files at need to
> be fixed and submit a patch...
>
> Thanks,
> dims
>
> --- Tom Jordahl <to...@macromedia.com> wrote:
> >
> > Rob,
> >
> > Great work tracking this down. If you send code to axis-dev
> > I am sure one of us will pick it up and submit it!
> >
> > --
> > Tom Jordahl
> >
> >
> > -----Original Message-----
> > From: Allegar Robert [mailto:allegar_robert@bah.com]
> > Sent: Friday, September 06, 2002 2:48 PM
> > To: axis-user@xml.apache.org
> > Subject: RE: Handlers and SOAP message re-writing
> >
> >
> > Ricky,
> > That helped quite a bit -- thanks. I tracked down the problem. First, the
> > reason I wasn't able to see the .addHeader method on the SOAPEnvelope
> object
> > is because the class I'm in (a holdover) imported
> > javax.xml.soap.SOAPEnvelope. So when I made a call to
> > SOAPEnvelope envelope =
> msgContext.getRequestMessage().getSOAPEnvelope();
> >
> > It was really returning a javax.xml.soap.SOAPEnvelope object not an
> > org.apache.axis.message.SOAPEnvelope. I didn't have to cast it, nor did I
> > get compile time errors because the Axis IMPL is a subclass of the Sun
> > interface. As a result the method addHeader() wasn't found.
> >
> > So since I couldn't use addHeader(), the road I was going down was to call
> > addChildElement on the returned SOAPEnvelope object -- which in this case
> > was javax.xml.soap.SOAPEnvelope -- but the implementation is actually in
> the
> > parent class of org.apache.axis.message.SOAPEnvelope:
> > org.apache.axis.message.MessageElement.
> >
> > Now, I've looked through the source code for both the axis MessageElement
> > object and the SOAPEnvelope object, and it seems like the code for
> > addChildElement is stubbed out. However, if I use the addChildElement()
> call
> > instead of the addHeader() call, the element is not appended and my
> > modification doesn't take -- no error is thrown but the SOAP request isn't
> > changed.
> >
> > The bug here is that both the org.apache.axis.message.SOAPHeader class and
> > the org.apache.axis.message.SOAPBody class don't override the
> > addChildElement of their parent. If you look at the code for both of these
> > classes, you'll see that they have a addHeaderElement() and
> addBodyElement()
> > respectively. SOAPEvenlope has a similar behavior. But none of the 3
> > sub-classes override the parent class's method so the header, envelope or
> > body is never really changed.
> >
> > The solution to this (bug?) is for the SOAPHeader, SOAPBody and
> SOAPEnvelope
> > classes to override the addChildElement of the parent so that the element
> > doesn't go in the generic "children" ArrayList in the MessageElement
> parent
> > class but get added to the nested "bodyElements" Vector (in SOAPBody) and
> > "headers" Vector (in SOAPHeader). I'd be happy to help the Axis developers
> > with this change if necessary.
> >
> > Regards,
> > Rob
> >
> >
> >
> >
> > -----Original Message-----
> > From: Ricky Ho [mailto:riho@cisco.com]
> > Sent: Friday, September 06, 2002 10:54 AM
> > To: axis-user@xml.apache.org
> > Subject: RE: Handlers and SOAP message re-writing
> >
> >
> > Following is my exact code based on AXIS beta 2
> >
> > import org.apache.axis.*;
> > import org.apache.axis.handlers.*;
> > import org.apache.axis.message.*;
> >
> > public class PutHeaderHandler extends BasicHandler {
> > public void invoke(MessageContext msgContext) throws AxisFault
> > {
> > try {
> > System.out.println(" -- PutHeaderHandler starts --");
> > System.out.println("Options are : " + getOptions());
> >
> > SOAPEnvelope envelope =
> > msgContext.getRequestMessage().getSOAPEnvelope();
> > System.out.println("Request message is : " + envelope);
> > envelope.addHeader(new SOAPHeaderElement("TestNameSpace",
> > "isAuthenticated", new Boolean(true)));
> >
> > System.out.println("Add header");
> > } catch (Exception e) {
> > throw AxisFault.makeFault(e);
> > }
> > }
> > }
> >
> > Rgds, Ricky
>
>
> =====
> Davanum Srinivas - http://xml.apache.org/~dims/
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Finance - Get real-time stock quotes
> http://finance.yahoo.com
>
=====
Davanum Srinivas - http://xml.apache.org/~dims/
__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com
RE: Handlers and SOAP message re-writing
Posted by Allegar Robert <al...@bah.com>.
Thanks for the fix -- It looks like that would do the trick. I would have
made the change myself but I'm not sure how to bootstrap the process of
sending changes to the committers. Do I just post them to axis-dev as
attachments or is there a linux kernel-like 'patch' notation I should use?
Rob
-----Original Message-----
From: Davanum Srinivas [mailto:dims@yahoo.com]
Sent: Saturday, September 07, 2002 9:00 PM
To: axis-dev@xml.apache.org; 'axis-user@xml.apache.org'
Cc: 'axis-dev@xml.apache.org'; allegar_robert@bah.com
Subject: RE: Handlers and SOAP message re-writing
Rob,
As part of fix for Bug #12357 i checked in a modified SOAPHeader
file...Please check it out and
let us know if this works for you, you can use a similar approach for the
other files at need to
be fixed and submit a patch...
Thanks,
dims
--- Tom Jordahl <to...@macromedia.com> wrote:
>
> Rob,
>
> Great work tracking this down. If you send code to axis-dev
> I am sure one of us will pick it up and submit it!
>
> --
> Tom Jordahl
>
>
> -----Original Message-----
> From: Allegar Robert [mailto:allegar_robert@bah.com]
> Sent: Friday, September 06, 2002 2:48 PM
> To: axis-user@xml.apache.org
> Subject: RE: Handlers and SOAP message re-writing
>
>
> Ricky,
> That helped quite a bit -- thanks. I tracked down the problem. First, the
> reason I wasn't able to see the .addHeader method on the SOAPEnvelope
object
> is because the class I'm in (a holdover) imported
> javax.xml.soap.SOAPEnvelope. So when I made a call to
> SOAPEnvelope envelope =
msgContext.getRequestMessage().getSOAPEnvelope();
>
> It was really returning a javax.xml.soap.SOAPEnvelope object not an
> org.apache.axis.message.SOAPEnvelope. I didn't have to cast it, nor did I
> get compile time errors because the Axis IMPL is a subclass of the Sun
> interface. As a result the method addHeader() wasn't found.
>
> So since I couldn't use addHeader(), the road I was going down was to call
> addChildElement on the returned SOAPEnvelope object -- which in this case
> was javax.xml.soap.SOAPEnvelope -- but the implementation is actually in
the
> parent class of org.apache.axis.message.SOAPEnvelope:
> org.apache.axis.message.MessageElement.
>
> Now, I've looked through the source code for both the axis MessageElement
> object and the SOAPEnvelope object, and it seems like the code for
> addChildElement is stubbed out. However, if I use the addChildElement()
call
> instead of the addHeader() call, the element is not appended and my
> modification doesn't take -- no error is thrown but the SOAP request isn't
> changed.
>
> The bug here is that both the org.apache.axis.message.SOAPHeader class and
> the org.apache.axis.message.SOAPBody class don't override the
> addChildElement of their parent. If you look at the code for both of these
> classes, you'll see that they have a addHeaderElement() and
addBodyElement()
> respectively. SOAPEvenlope has a similar behavior. But none of the 3
> sub-classes override the parent class's method so the header, envelope or
> body is never really changed.
>
> The solution to this (bug?) is for the SOAPHeader, SOAPBody and
SOAPEnvelope
> classes to override the addChildElement of the parent so that the element
> doesn't go in the generic "children" ArrayList in the MessageElement
parent
> class but get added to the nested "bodyElements" Vector (in SOAPBody) and
> "headers" Vector (in SOAPHeader). I'd be happy to help the Axis developers
> with this change if necessary.
>
> Regards,
> Rob
>
>
>
>
> -----Original Message-----
> From: Ricky Ho [mailto:riho@cisco.com]
> Sent: Friday, September 06, 2002 10:54 AM
> To: axis-user@xml.apache.org
> Subject: RE: Handlers and SOAP message re-writing
>
>
> Following is my exact code based on AXIS beta 2
>
> import org.apache.axis.*;
> import org.apache.axis.handlers.*;
> import org.apache.axis.message.*;
>
> public class PutHeaderHandler extends BasicHandler {
> public void invoke(MessageContext msgContext) throws AxisFault
> {
> try {
> System.out.println(" -- PutHeaderHandler starts --");
> System.out.println("Options are : " + getOptions());
>
> SOAPEnvelope envelope =
> msgContext.getRequestMessage().getSOAPEnvelope();
> System.out.println("Request message is : " + envelope);
> envelope.addHeader(new SOAPHeaderElement("TestNameSpace",
> "isAuthenticated", new Boolean(true)));
>
> System.out.println("Add header");
> } catch (Exception e) {
> throw AxisFault.makeFault(e);
> }
> }
> }
>
> Rgds, Ricky
=====
Davanum Srinivas - http://xml.apache.org/~dims/
__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com
RE: Handlers and SOAP message re-writing
Posted by Davanum Srinivas <di...@yahoo.com>.
Rob,
As part of fix for Bug #12357 i checked in a modified SOAPHeader file...Please check it out and
let us know if this works for you, you can use a similar approach for the other files at need to
be fixed and submit a patch...
Thanks,
dims
--- Tom Jordahl <to...@macromedia.com> wrote:
>
> Rob,
>
> Great work tracking this down. If you send code to axis-dev
> I am sure one of us will pick it up and submit it!
>
> --
> Tom Jordahl
>
>
> -----Original Message-----
> From: Allegar Robert [mailto:allegar_robert@bah.com]
> Sent: Friday, September 06, 2002 2:48 PM
> To: axis-user@xml.apache.org
> Subject: RE: Handlers and SOAP message re-writing
>
>
> Ricky,
> That helped quite a bit -- thanks. I tracked down the problem. First, the
> reason I wasn't able to see the .addHeader method on the SOAPEnvelope object
> is because the class I'm in (a holdover) imported
> javax.xml.soap.SOAPEnvelope. So when I made a call to
> SOAPEnvelope envelope = msgContext.getRequestMessage().getSOAPEnvelope();
>
> It was really returning a javax.xml.soap.SOAPEnvelope object not an
> org.apache.axis.message.SOAPEnvelope. I didn't have to cast it, nor did I
> get compile time errors because the Axis IMPL is a subclass of the Sun
> interface. As a result the method addHeader() wasn't found.
>
> So since I couldn't use addHeader(), the road I was going down was to call
> addChildElement on the returned SOAPEnvelope object -- which in this case
> was javax.xml.soap.SOAPEnvelope -- but the implementation is actually in the
> parent class of org.apache.axis.message.SOAPEnvelope:
> org.apache.axis.message.MessageElement.
>
> Now, I've looked through the source code for both the axis MessageElement
> object and the SOAPEnvelope object, and it seems like the code for
> addChildElement is stubbed out. However, if I use the addChildElement() call
> instead of the addHeader() call, the element is not appended and my
> modification doesn't take -- no error is thrown but the SOAP request isn't
> changed.
>
> The bug here is that both the org.apache.axis.message.SOAPHeader class and
> the org.apache.axis.message.SOAPBody class don't override the
> addChildElement of their parent. If you look at the code for both of these
> classes, you'll see that they have a addHeaderElement() and addBodyElement()
> respectively. SOAPEvenlope has a similar behavior. But none of the 3
> sub-classes override the parent class's method so the header, envelope or
> body is never really changed.
>
> The solution to this (bug?) is for the SOAPHeader, SOAPBody and SOAPEnvelope
> classes to override the addChildElement of the parent so that the element
> doesn't go in the generic "children" ArrayList in the MessageElement parent
> class but get added to the nested "bodyElements" Vector (in SOAPBody) and
> "headers" Vector (in SOAPHeader). I'd be happy to help the Axis developers
> with this change if necessary.
>
> Regards,
> Rob
>
>
>
>
> -----Original Message-----
> From: Ricky Ho [mailto:riho@cisco.com]
> Sent: Friday, September 06, 2002 10:54 AM
> To: axis-user@xml.apache.org
> Subject: RE: Handlers and SOAP message re-writing
>
>
> Following is my exact code based on AXIS beta 2
>
> import org.apache.axis.*;
> import org.apache.axis.handlers.*;
> import org.apache.axis.message.*;
>
> public class PutHeaderHandler extends BasicHandler {
> public void invoke(MessageContext msgContext) throws AxisFault
> {
> try {
> System.out.println(" -- PutHeaderHandler starts --");
> System.out.println("Options are : " + getOptions());
>
> SOAPEnvelope envelope =
> msgContext.getRequestMessage().getSOAPEnvelope();
> System.out.println("Request message is : " + envelope);
> envelope.addHeader(new SOAPHeaderElement("TestNameSpace",
> "isAuthenticated", new Boolean(true)));
>
> System.out.println("Add header");
> } catch (Exception e) {
> throw AxisFault.makeFault(e);
> }
> }
> }
>
> Rgds, Ricky
=====
Davanum Srinivas - http://xml.apache.org/~dims/
__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com