[jira] Closed: (DAEMON-189) Align windows service start with daemon start
[ https://issues.apache.org/jira/browse/DAEMON-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mladen Turk closed DAEMON-189. -- Resolution: Won't Fix There is no way that Daemon could know when the Tomcat is fully up and running and ready to accept the connections. There is also a question which connector when up would notify daemon it is ready. First one or all of them? > Align windows service start with daemon start > - > > Key: DAEMON-189 > URL: https://issues.apache.org/jira/browse/DAEMON-189 > Project: Commons Daemon > Issue Type: New Feature > Components: Procrun >Reporter: Mark Thomas > > Originally reported against Tomcat [1], this enhancement request is to have > the service start not exit until the daemon has started. As far as I can > tell, this will require changes to procrun for this to work with Tomcat - > hence this enhancement request. > [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=5329 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DAEMON-189) Align windows service start with daemon start
Align windows service start with daemon start - Key: DAEMON-189 URL: https://issues.apache.org/jira/browse/DAEMON-189 Project: Commons Daemon Issue Type: New Feature Components: Procrun Reporter: Mark Thomas Originally reported against Tomcat [1], this enhancement request is to have the service start not exit until the daemon has started. As far as I can tell, this will require changes to procrun for this to work with Tomcat - hence this enhancement request. [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=5329 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (VFS-325) Bad handling of hashs (#) in file names when walking a file tree using findFiles()
[
https://issues.apache.org/jira/browse/VFS-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970766#action_12970766
]
Joerg Schaible commented on VFS-325:
Sorry, this solution is wrong. A hash '#' has a special meaning in a URL. If a
filename contains such a character, the URL must contain it in the encoded form
"%23".
> Bad handling of hashs (#) in file names when walking a file tree using
> findFiles()
> --
>
> Key: VFS-325
> URL: https://issues.apache.org/jira/browse/VFS-325
> Project: Commons VFS
> Issue Type: Bug
>Affects Versions: 1.0, 1.1, 2.0
> Environment: Windows Seven, JDK 1.6 64 bit
>Reporter: Nicolas Guillaumin
> Attachments: PATCH-vfs-325.tar
>
>
> Consider a local directory tree containing files with hashs in their name,
> such as {{test-hash-#.txt}}.
> When walking the tree using FileObject.findFiles(), the file is correctly
> found and returned, but it's URL is truncated to the #: {{test-hash-}}
> * Calling file.getURL().toString() returns {{file://my/dir/test-hash-}}
> * Calling file.toString() returns the correct URL
> {{file://my/dir/test-hash-#.txt}}
> * For the sake of testing, calling new
> URL("http://my/file/with/hash-#.txt";).toString() returns
> {{http://my/file/with/hash-#.txt}} (It's not an java.net.URL problem)
> I think file.getURL().toString() should return {{test-hash-#.txt}}, otherwise
> caller have to rely on file.toString() to retrieve the URL of the file, which
> is probably bad.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COLLECTIONS-360) FilterListIterator#hasNext throws exception (associate with JUnit tests)
[
https://issues.apache.org/jira/browse/COLLECTIONS-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12970749#action_12970749
]
Igor Saprykin commented on COLLECTIONS-360:
---
As far as I understand expression "{{FilterListIterator(var9)}}" resolves into
{{FilterListIterator(Predicate predicate)}} constructor. Here's what
it's javadoc is saying:
{quote}{noformat}
Constructs a new FilterListIterator that will not function
until {...@link #setListIterator(ListIterator) setListIterator} is invoked.
@param predicate the predicate to use.{noformat}{quote}
So if a {{ListIterator}} isn't specified than
[NullPointerException|http://download.oracle.com/javase/6/docs/api/java/lang/NullPointerException.html](your
case) is thrown.
I think, you're partialy right - {{FilterListIterator}} implements {{Iterator}}
interface and
[Iterator.hasNext()|http://download.oracle.com/javase/6/docs/api/java/util/Iterator.html#hasNext()]
doesn't specify any exceptions to be thrown.
If it's really an issue maybe these two constructors -
{{FilterListIterator(Predicate predicate)}} and
{{FilterListIterator(ListIterator iterator )}} should be
deprecated?
> FilterListIterator#hasNext throws exception (associate with JUnit tests)
>
>
> Key: COLLECTIONS-360
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-360
> Project: Commons Collections
> Issue Type: Bug
>Affects Versions: 3.2
> Environment: ubuntu
>Reporter: Sai Zhang
>
> Hi,
> I found the some of the iterator classes does not fulfill the iterator
> specification of JDK.
> e.g. hasNext() should never throw exception.
> Here is an automatically generated junit test (I am now writing a tool)
> {code:java}
> public void test233() throws Throwable {
> java.lang.Integer var6 = new java.lang.Integer(0);
> org.apache.commons.collections.list.GrowthList var7 = new
> org.apache.commons.collections.list.GrowthList(var6);
> org.apache.commons.collections.Predicate var9 =
> org.apache.commons.collections.PredicateUtils.anyPredicate((java.util.Collection)var7);
> java.lang.Long var10 = new java.lang.Long(10L);
> org.apache.commons.collections.iterators.FilterListIterator var13 = new
> org.apache.commons.collections.iterators.FilterListIterator(var9);
> //this line throws exception!
> var13.hasNext();
> }
> {code}
> could you please check it to confirm whether it is bug or I misunderstand the
> specification of apache common collections?
> thanks,
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
