Can anyone tell me how to add a directive which will be available to dvsl?
I have created a directive named redirect, which serves the same
function
as the Xalan redirect extension. It will allow you to send the contents
of the
enclosed block to a specific file. This is useful when
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28660.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi Steve,
I don't know if the newly minted committer you're referring to is me - I
am unfortunately not quite minted yet, as I have been offsite for the last
week , so I haven't yet had a chance to fax the PMC the necessary doc. If I
was a committer today, however, I would of course be saying:
I'd say we're good to go.
On Wed, 28 Apr 2004 05:21:28 -0500, Steve Cohen [EMAIL PROTECTED] said:
Where do we stand on this? I have two +1s from known committers to
the project, another +1 from Mario, who I don't believe is a
committer on this project but may be one for some other commons
Thanks for giving that a work out !
-Original Message-
From: Matthias Wessendorf [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 27, 2004 09:39 PM
To: ''Jakarta Commons Developers List''
Subject: RE: [Validator] 1.1.3 Release
works fine with
nightly builds from struts
thanks!
Dear All,
I have started using the sandbox functors for my projects. It seems
that parts of the code may still need some streamlining.
I gave a shot at IsInstanceOf.
Please receive attached a patch which changes IsInstanceOf from a
UnaryPredicate to a BinaryPredicate (as the binary operator
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28486.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28660.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi all,
For [configuration] I am doing testing using a jar that hasn't been deployed
on ibiblio or any other Maven enabled repository. Has anyone thought about
hosting a repository on commons? Maybe
http://jakarta.apache.org/commons/repository? It would be nice to have a
spot where we can put
Has there been a release of naming yet? It doesn't look like it quite yet?
Eric
-Original Message-
From: Phil Steitz [mailto:[EMAIL PROTECTED]
Sent: Friday, April 09, 2004 12:30 AM
To: Jakarta Commons Developers List
Subject: Re: [configuration] Subsets and JNDIConfiguration
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28486.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
epugh 2004/04/28 15:58:58
Modified:configuration/src/java/org/apache/commons/configuration
JNDIConfiguration.java
Log:
Change from listBindings to list to work with getting keys.
Revision ChangesPath
1.11 +31 -27
Eric Pugh wrote:
For [configuration] I am doing testing using a jar that hasn't been deployed
on ibiblio or any other Maven enabled repository. Has anyone thought about
hosting a repository on commons? Maybe
http://jakarta.apache.org/commons/repository? It would be nice to have a
spot where we
Hi all,
I finally finished reworking the JNDIConfiguration to properly work with
SubsetConfiguration and CompositeConfiguration. Basically I was using
.listBindings instead of .list to retrieve a bunch of keys..
I have implemented the code using spice jndi as I found that easier the
In message [EMAIL PROTECTED], Steve Cohen writes:
Where do we stand on this?
Hey, you called the vote, you're supposed to know :)
I have two +1s from known committers to the project, another +1 from Mario,
who I don't believe is a committer on this project but may be one for some
other
Daniel, at the time I posted, Jeffrey had not voted on this list. I had seen
only your +1 and my my own and I wasn't sure if Mario had a vote here or not.
I don't know Davanum Srinivas at all and haven't see his vote.
I had no idea that people could vote on the PMC list and not here. I
Sorry about that Steve, it is confusing and my mail software put your
emails next to one another, I thought I replied to the commons-dev
one. I'll be more diligent and make sure I vote to the commons-dev
list.
( This is turning into the release from hell ;)
On Wed, 28 Apr 2004 19:18:57 -0500,
To whom it may engage...
This is an automated request, but not an unsolicited one. For help
understanding the request please visit
http://gump.apache.org/nagged.html,
and/or contact [EMAIL PROTECTED]
Project commons-jelly-tags-jsl has an issue affecting its community integration, and
To whom it may engage...
This is an automated request, but not an unsolicited one. For help
understanding the request please visit
http://gump.apache.org/nagged.html,
and/or contact [EMAIL PROTECTED]
Project commons-jelly-tags-jetty has an issue affecting its community integration,
To whom it may engage...
This is an automated request, but not an unsolicited one. For help
understanding the request please visit
http://gump.apache.org/nagged.html,
and/or contact [EMAIL PROTECTED]
Project commons-jelly-tags-define has an issue affecting its community integration,
Oleg Kalnichevski wrote:
Folks,
Any idea what to do with one? First of all, user name and password in
HTTP url is something completely new to me. Any idea what Sung-Gu had in
mind?
Oleg
We need to check what is the allowed character range that is supported
in the username/password part of a
Hi Oleg,
see RFC 2396, URI: Generic Syntax, section 3.2.2:
userinfo@host:port
Some URL schemes use the format user:password in the userinfo
field. This practice is NOT RECOMMENDED, because the passing of
authentication information in clear text (such as URI) has proven to
be a
Hi Oleg,
abstraction is good, abstraction layers are even better...
But seriously: no need for NDC support in HttpClient.
My application provides it's own logging framework, so
I can use the thread context to pass information from
my application to my logging framework, through and
without help
Roland Weber wrote:
Hi Oleg,
see RFC 2396, URI: Generic Syntax, section 3.2.2:
userinfo@host:port
Some URL schemes use the format user:password in the userinfo
field. This practice is NOT RECOMMENDED, because the passing of
authentication information in clear text (such as
Hi Ortwin,
the quote was not meant as an estimation.
Just a hint why that part of the URI spec
might be less well known as others.
BTW, the section also defines the valid characters:
userinfo = *( unreserved | escaped |
; | : | | = | + | $ | , )
cheers,
Roland Weber wrote:
Hi Ortwin,
the quote was not meant as an estimation.
Just a hint why that part of the URI spec
might be less well known as others.
Ok :-)
BTW, the section also defines the valid characters:
userinfo = *( unreserved | escaped |
; | : |
Hi Oleg:
Thanks for your reply. Two days ago I tried the FormLoginDemo, but after I saw your
e-mail I tried again and got the following response, with my Sun Developer Id and
password :
Hello Frank,
the problem with the Sun site is that HttpClient does not
support cross host redirects. See here for directions:
http://jakarta.apache.org/commons/httpclient/redirects.html
For Yahoo with it's HTTPS URL, you have to install or
enable SSL support. See here for directions:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28659.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Frank,
I just what to add one thing to what Roland has said: basically the authentication
with the developer.java.sun.com succeeded. You got the session cookie back. HttpClient
was simply unable to process the post-logon redirect, but this limitation is not
difficult to work around (see the
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28659.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
When will HttpClient 2.0 Final be signed -- PGP signatures MD5 checksum
available? Currently, it is listed as unsigned on the binary download
page. Thanks!
Chris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Folks,
It's been a week, there's no response, and I suspect there'll be none.
What else shall I do? Threaten them with a preventive nuclear strike?
I have an impression that Bugzilla is simply no longer supported, which
poses an important question why should we continue using it.
Shall I try
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28659.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Chris,
We already have a bug report pending for this:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27026
My (unofficial) plan was to take care of it for the next releases: 3.0-alpha1
(expected within a month) and 2.0.1 (has not been discussed yet, but certainly
imminent). If it is
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28664.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28659.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28659.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28659.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28664.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=17416.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
difficult to work around (see the redirect guide). I am sure it
should not be that difficult to form-based login with get
my.yahoo.com working. Give it another try
Yes, one wouldn't think so :) I took a look at this last night, and it
seems that yahoo does some weird stuff. In particular they
I was thinking we would do this for the next release as well. The MD5
part is quite easy, and could be added now if we want. The PGP part
shouldn't be too difficult either, but I haven't looked into Jakarta
standard procedures for this (i.e. what ID to sign with, etc.).
Mike
Kalnichevski,
I forget what we decided when this was last discussed, but I am all for
moving to Jira.
If we do stick with Bugzilla, I don't think we should bother
[EMAIL PROTECTED] about this one. This is something that the
infrastructure list is for. Let's give them a little more time. Perhaps
a quick
At this time, I don't have an immediate need for them. I just noticed that
they weren't there. Thanks!
Chris
Kalnichevski,
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=26070.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=28645.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://issues.apache.org/bugzilla/show_bug.cgi?id=26070.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
If my memory does not fail me, the general sentiment was to stick to
Bugzilla if HttpClient gets to be a top level project in the Bugzilla
database (in order for us to be able to define own releases and
milestones independently from Commons).
That sounds about right.
IMO Bugzilla has been
Hello,
The problem is the Verisign root certificate that ships with the Sun's
JREs expired in January. You will need to upgrade to a newer JRE to
fix this problem. In your case I think you will need something =
1.4.1_06.
Mike
On Apr 28, 2004, at 12:51 AM, bagas wrote:
Thank you for
Well, I've tried a variety of things, but I cannot successfully login
to yahoo. Attached is the code that I've been using. It includes two
methods, one to simulate logging in from a browser with JavaScript
turned off, and another to simulate with JS on. Perhaps someone else
can figure it
I've used HttpClient to log into several web sites that try to make it hard
to write programs that automatically log in (maybe Yahoo is trying to make
it hard). One invaluable tool I've found is the LiveHTTPHeaders mozilla
plugin (http://livehttpheaders.mozdev.org) with Mozilla 1.5 or later.
52 matches
Mail list logo
