[
https://issues.apache.org/jira/browse/DIRMINA-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802196#action_12802196
]
ncanis2 commented on DIRMINA-742:
-
I think this problem was fixed.
when I used below
[
https://issues.apache.org/jira/browse/DIRMINA-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny resolved DIRMINA-757.
---
Resolution: Fixed
Done
Add an entry in FAQ explaining how to correctly close a
[
https://issues.apache.org/jira/browse/DIRMINA-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny closed DIRMINA-757.
-
Add an entry in FAQ explaining how to correctly close a session and dispose
the
[
https://issues.apache.org/jira/browse/DIRMINA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Vermillard updated DIRMINA-484:
--
Affects Version/s: 3.0.0-M1
to do for 3.0 or post 2.0 if we keep APR
Datagram
[
https://issues.apache.org/jira/browse/DIRMINA-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Vermillard updated DIRMINA-301:
--
Fix Version/s: 3.0.0-M1
New Multi threaded SocketIOProcessor to improve fairness of
[
https://issues.apache.org/jira/browse/DIRMINA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Vermillard updated DIRMINA-484:
--
Affects Version/s: (was: 3.0.0-M1)
Fix Version/s: 3.0.0-M1
Datagram
[
https://issues.apache.org/jira/browse/DIRMINA-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Vermillard updated DIRMINA-723:
--
Fix Version/s: 3.0.0-M1
OrderedThreadPoolExecutor behavior: configurable queue size,
[
https://issues.apache.org/jira/browse/DIRMINA-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Vermillard resolved DIRMINA-355.
---
Resolution: Won't Fix
1.0 is very old now
Modified sumup client to act as a
[
https://issues.apache.org/jira/browse/DIRMINA-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Vermillard updated DIRMINA-509:
--
Fix Version/s: 3.0.0-M1
Yes creating a session for each UDP end-ponit is a big
[
https://issues.apache.org/jira/browse/DIRMINA-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Vermillard resolved DIRMINA-641.
---
Resolution: Won't Fix
the whole compression filter is a memory eater, avoid it if
[
https://issues.apache.org/jira/browse/DIRMINA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802257#action_12802257
]
Julien Vermillard commented on DIRMINA-379:
---
is it still a problem with 2.0.0
[
https://issues.apache.org/jira/browse/DIRMINA-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Vermillard resolved DIRMINA-715.
---
Resolution: Won't Fix
the API is frozen, you still can change the time out before
[
https://issues.apache.org/jira/browse/DIRMINA-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Vermillard updated DIRMINA-250:
--
Fix Version/s: 3.0.0-M1
Issue Type: Wish (was: Task)
Provide a test suite
[
https://issues.apache.org/jira/browse/DIRMINA-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802261#action_12802261
]
Julien Vermillard commented on DIRMINA-258:
---
any progress on this issue ?
I wanted to assign an issue to myself to work on it but was unable to.
Regards,
Alan
On Jan 19, 2010, at 4:12 AM, Emmanuel Lecharny wrote:
Hi guys,
some progress has been made last week. Here is the current status.
Here are he remaining issues : ([B] = Bug, [I] = Improvement, [T] =
task,
[
https://issues.apache.org/jira/browse/DIRMINA-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien Vermillard resolved DIRMINA-196.
---
Resolution: Won't Fix
based on a very old version
Connection shaper
Are you begging for jira karma ?
Be carefull because we can provide it and you will be trapped in :)
I'm going to take a look.
Julien
Le Tue, 19 Jan 2010 06:01:56 -0800,
Alan D. Cabrera l...@toolazydogs.com a écrit :
I wanted to assign an issue to myself to work on it but was unable to.
Ok I figured your user id.
Now you can assign you a ton of bugs :)
Le Tue, 19 Jan 2010 06:01:56 -0800,
Alan D. Cabrera l...@toolazydogs.com a écrit :
I wanted to assign an issue to myself to work on it but was unable to.
Regards,
Alan
On Jan 19, 2010, at 4:12 AM, Emmanuel Lecharny
[
https://issues.apache.org/jira/browse/DIRMINA-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Cabrera reassigned DIRMINA-707:
Assignee: Alan Cabrera
Add sendfile support to APR transport
Thanks!
Regards,
Alan
On Jan 19, 2010, at 6:14 AM, Julien Vermillard wrote:
Ok I figured your user id.
Now you can assign you a ton of bugs :)
Le Tue, 19 Jan 2010 06:01:56 -0800,
Alan D. Cabrera l...@toolazydogs.com a écrit :
I wanted to assign an issue to myself to work on it but was
try {
doSomeStuff();
} catch (RuntimeException e) {
throw e;
} catch (Error e) {
throw e;
} catch (Exception e) {
throw new RuntimeIoException(Failed to create a
pollset., e);
} finally {
Where did u pulled this out from ?
On Tue, Jan 19, 2010 at 8:11 PM, Alan D. Cabrera l...@toolazydogs.com wrote:
try {
doSomeStuff();
} catch (RuntimeException e) {
throw e;
} catch (Error e) {
throw e;
} catch (Exception e) {
APR code needs unit tests
-
Key: DIRMINA-758
URL: https://issues.apache.org/jira/browse/DIRMINA-758
Project: MINA
Issue Type: Improvement
Reporter: Alan Cabrera
The APR code should be unit tested.
--
[
https://issues.apache.org/jira/browse/DIRMINA-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802290#action_12802290
]
Alan Cabrera commented on DIRMINA-707:
--
On second thought. I think that
See http://hudson.zones.apache.org/hudson/job/MINA-trunk/205/changes
Changes:
[adc] DIRMINA-707 Add sendfile support to APR transport
--
Started by an SCM change
Building remotely on vesta.apache.org (Ubuntu)
Updating
[
https://issues.apache.org/jira/browse/DIRMINA-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802293#action_12802293
]
Julien Vermillard commented on DIRMINA-758:
---
the main problem is to automagicly
[
https://issues.apache.org/jira/browse/DIRMINA-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802296#action_12802296
]
Alan Cabrera commented on DIRMINA-758:
--
Hmmm, good point. How does Tomcat test?
I
[
https://issues.apache.org/jira/browse/DIRMINA-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Cabrera resolved DIRMINA-707.
--
Resolution: Fixed
Many thanks.
Add sendfile support to APR transport
org.apache.mina.transport.socket.apr.AprIoProcessor
Regards,
Alan
On Jan 19, 2010, at 6:44 AM, Ashish wrote:
Where did u pulled this out from ?
On Tue, Jan 19, 2010 at 8:11 PM, Alan D. Cabrera
l...@toolazydogs.com wrote:
try {
doSomeStuff();
} catch
[
https://issues.apache.org/jira/browse/DIRMINA-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802302#action_12802302
]
Julien Vermillard commented on DIRMINA-758:
---
I think if we want to do that, we
Well I think only Exception could be the only case needed. However,
catching generic Exception means any error, a specific Exception
caught is better,
BTW, the catch(Error e) {} stuff has been caught by IntelliJ Inspections.
Just one more thing that I noted in the class, there are no log
Shall give IRMINA-593 a try ASAP. I did some work earlier for
documenting the stuff, but lost the stuff when I changed my
organization :-(
Getting documentation around it shall be tricky. There is a SMPP
server example attached to the JIRA. If it works, will try to see the
execution details, as I
Had picked this form one the discussion threads and added to the MINA
3.0 design page, so that we don't loose this.
had some initial thoughts around this, like we can some kind of
visualization tool build around MINA, which can help us see/debug
the MINA based System. One can view number of
The point is to react differently in case of different exceptions
but exceptions must be sorted from specific exceptions to generic ones
it can also be done by catching exception and using instanceof statements
my 2 cents :)
Cordialement, Regards,
-Edouard De Oliveira-
Blog:
Le Tue, 19 Jan 2010 13:12:28 +0100,
Emmanuel Lecharny elecha...@apache.org a écrit :
Hi guys,
some progress has been made last week. Here is the current status.
Here are he remaining issues : ([B] = Bug, [I] = Improvement, [T] =
task, [F] = new Feature, [W] = wish)
MINA 2.0-RC2 roadmap
Ashish a écrit :
Where did u pulled this out from ?
NO ! Alan, please, no need to tell ;)
Seriously, it stinks ;)
--
Regards,
Cordialement,
Emmanuel Lécharny
www.nextury.com
In practice this is true. But in this instance we do nothing.
Regards,
Alan
On Jan 19, 2010, at 9:16 AM, Edouard De Oliveira wrote:
The point is to react differently in case of different exceptions
but exceptions must be sorted from specific exceptions to generic ones
it can also be done by
BTW how do you did your fancy txt export ?
keyboard and patience ...
--
Regards,
Cordialement,
Emmanuel Lécharny
www.nextury.com
Alan D. Cabrera a écrit :
Just one more thing that I noted in the class, there are no log
statements. Dom't we need them?
I'm against logging exceptions if we're re-throwing them unless we
print out some critical piece of information that cannot be discerned
by any other method. I say
On Jan 19, 2010, at 10:45 AM, Emmanuel Lcharny wrote:
Alan D. Cabrera a écrit :
Just one more thing that I noted in the class, there are no log
statements. Dom't we need them?
I'm against logging exceptions if we're re-throwing them unless we
print out some critical piece of
Alan D. Cabrera a écrit :
IMO, we should log :
- where we got the exception if we know that no log has already been
generated
I'm against this since you usually have no idea if someone else has
logged the error.
When you are writing a framework, you are the one responsible for
logging,
Alan D. Cabrera a écrit :
On Jan 19, 2010, at 7:31 AM, Ashish wrote:
Well I think only Exception could be the only case needed. However,
catching generic Exception means any error, a specific Exception
caught is better.
The other odd thing is that it catches the checked exception and wraps
Well I think only Exception could be the only case needed. However,
catching generic Exception means any error, a specific Exception
caught is better.
The other odd thing is that it catches the checked exception and wraps it in
a runtime exception. This strikes me as a poor practice.
On Jan 19, 2010, at 6:44 PM, Ashish wrote:
Well I think only Exception could be the only case needed. However,
catching generic Exception means any error, a specific Exception
caught is better.
The other odd thing is that it catches the checked exception and
wraps it in
a runtime
On Jan 19, 2010, at 3:15 PM, Emmanuel Lcharny wrote:
Alan D. Cabrera a écrit :
On Jan 19, 2010, at 7:31 AM, Ashish wrote:
Well I think only Exception could be the only case needed. However,
catching generic Exception means any error, a specific Exception
caught is better.
The other odd
[
https://issues.apache.org/jira/browse/DIRMINA-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12802665#action_12802665
]
Mark Webb commented on DIRMINA-258:
---
I think handing this off to Ashish might be a good
We can simply catch it and do whatever we want with it.
In this case, I think the constructor should be throwing an IOException.
Anyone mind if I remove the places where we removed the checked exceptions?
I am afraid, we have already freezed the API, so not sure if we should do this.
On Jan 19, 2010, at 8:58 PM, Ashish wrote:
We can simply catch it and do whatever we want with it.
In this case, I think the constructor should be throwing an
IOException.
Anyone mind if I remove the places where we removed the checked
exceptions?
I am afraid, we have already
[
https://issues.apache.org/jira/browse/DIRMINA-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Paliwal reassigned DIRMINA-258:
--
Assignee: Ashish Paliwal (was: Mark Webb)
Example of an XML server and Client.
[
https://issues.apache.org/jira/browse/DIRMINA-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Paliwal updated DIRMINA-258:
---
Component/s: Example
Fix Version/s: 3.0.0-M1
Moved to 3.0
Example of an XML server
50 matches
Mail list logo
