Re: What sucks about c:import!

2002-08-21 Thread Shawn Bayern
I think I agree with all of this. For JSTL 1.0, we opted to be a bit conservative since the need didn't yet strongly present itself. It wouldn't surprise me if a future version can add support for headers and HTTP POST; that might represent the knee in the curve, so to speak, between convenience

Re: What sucks about c:import!

2002-08-21 Thread peter lin
I'm not sure where it should reside to be honest. I can see argument for both sides. If I wanted to access data that resides on an IIS machine that has challenge/response turned on, it would be good to have cookie/auth support in jstl but one could easily argue it should be in a bean to provide

Re: What sucks about c:import!

2002-08-21 Thread Mark R. Diggory
Shawn Bayern wrote: >On Wed, 21 Aug 2002, peter lin wrote: > > > >>in the interest of discussion. I find it useful to have cookie, >>user-agent and other advanced capabilities in a web services context. >>As web services becomes more common place, supporting those features >>might become very

Re: What sucks about c:import!

2002-08-21 Thread Mark R. Diggory
The Jakarta Commons HttpClient has been usefull to me on a limited basis. All I really use it for is for building "Multipart File Posts". And to do that I even had to use a Class someone wrote which is not in the HttpClient package right now. The nice thing about the package is that I can buil

Re: What sucks about c:import!

2002-08-21 Thread Shawn Bayern
On Wed, 21 Aug 2002, Henri Yandell wrote: > I'm sure I could look this up myself, but it might be nice to have it > in the archives with this thread. > > Which jar is needed if I want to add EL to my taglib. Without having > to include the whole JSTL implementation? This is tricky and in flux.

Re: What sucks about c:import!

2002-08-21 Thread Shawn Bayern
On Wed, 21 Aug 2002, peter lin wrote: > in the interest of discussion. I find it useful to have cookie, > user-agent and other advanced capabilities in a web services context. > As web services becomes more common place, supporting those features > might become very important. But is it import

Re: What sucks about c:import!

2002-08-21 Thread Henri Yandell
I'm sure I could look this up myself, but it might be nice to have it in the archives with this thread. Which jar is needed if I want to add EL to my taglib. Without having to include the whole JSTL implementation? Hen On Wed, 21 Aug 2002, Shawn Bayern wrote: > On Wed, 21 Aug 2002, Mark R. Di

Re: What sucks about c:import!

2002-08-21 Thread Shawn Bayern
On Wed, 21 Aug 2002, Mark R. Diggory wrote: > On another note, I've been playing around with Taglibraries for some > time now. I'd like to integrate the EL Engine into my libraries, from > what I understand it is now going to be part of the JSP 2.0 spec as > well. How might I go about integrat

Re: What sucks about c:import!

2002-08-21 Thread peter lin
in the interest of discussion. I find it useful to have cookie, user-agent and other advanced capabilities in a web services context. As web services becomes more common place, supporting those features might become very important. peter lin Henri Yandell wrote: > > Isn't this the kind of th

Re: What sucks about c:import!

2002-08-21 Thread Mark R. Diggory
Thank you, I will post my comments there as well. On another note, I've been playing around with Taglibraries for some time now. I'd like to integrate the EL Engine into my libraries, from what I understand it is now going to be part of the JSP 2.0 spec as well. How might I go about integratin

Re: What sucks about c:import!

2002-08-21 Thread Shawn Bayern
Well, the Jakarta Taglibs "IO Taglib" is a pretty good offering. I think Mark was just hoping for a standard solution. -- Shawn Bayern "JSTL in Action" http://www.jstlbook.com On Wed, 21 Aug 2002, Henri Yandell wrote: > Isn't this the kind of thing that Jakarta Commons HttpClient specialise

Re: What sucks about c:import!

2002-08-21 Thread Henri Yandell
Isn't this the kind of thing that Jakarta Commons HttpClient specialises in? In which case a taglib for that would be a pretty nice affair... [I assume there's not one already..] Hen On Wed, 21 Aug 2002, Shawn Bayern wrote: > Indeed - JSTL 1.0 does not support advanced HTTP operations from wit

Re: What sucks about c:import!

2002-08-21 Thread Shawn Bayern
Indeed - JSTL 1.0 does not support advanced HTTP operations from within JSP pages using (e.g., basic authentication, free modification of headers), but a future version of JSTL could if there were enough perceived need. As Peter says, it's a good idea to inform the expert group if you'd like to

Re: What sucks about c:import!

2002-08-21 Thread peter lin
I'm assuming you want to get at things like cookies, user-agent and other http header data. you may want to make a request to the expert group, so that it is included in the next version of JSTL. I believe the current importsupport class just uses standard url & httpurlconnection classes. shawn

What sucks about c:import!

2002-08-21 Thread Mark R. Diggory
Now that I have your attention. We are continually working with managing headers in our URL object requests to get resources from different locations. Is there really any way I can set the request Header info on the URL object being created by c:import? Right now I have my own custom implement