[jira] Commented: (DIRMINA-586) Dynamic delimiter support for TextLineCodecFactory
[
https://issues.apache.org/jira/browse/DIRMINA-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658525#action_12658525
]
Ashish Paliwal commented on DIRMINA-586:
Not sure if this still an issue. A custom delimiter can be created using
following construct
new LineDelimiter("delimiter") ; and passed onto TextLineCodecFactory
To specify the same in TextLineCodecfactory, following constructors can be used
public TextLineCodecFactory(Charset charset, String encodingDelimiter, String
decodingDelimiter)
or
public TextLineCodecFactory(Charset charset, LineDelimiter encodingDelimiter,
LineDelimiter decodingDelimiter)
> Dynamic delimiter support for TextLineCodecFactory
> --
>
> Key: DIRMINA-586
> URL: https://issues.apache.org/jira/browse/DIRMINA-586
> Project: MINA
> Issue Type: Improvement
> Components: Filter
>Affects Versions: 2.0.0-M1
>Reporter: Trustin Lee
>Priority: Minor
> Fix For: 2.0.0-RC1
>
>
> TextLineCodecFactory supports static delimiters only. For some cases, users
> need to switch the delimiter dynamically depending on context. Related
> discussion is found here:
> http://markmail.org/message/loiqoej35evt2yvv
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (DIRMINA-586) Dynamic delimiter support for TextLineCodecFactory
[
https://issues.apache.org/jira/browse/DIRMINA-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658525#action_12658525
]
paliwalashish edited comment on DIRMINA-586 at 12/22/08 4:43 AM:
--
Not sure if this is still an issue. A custom delimiter can be created using
following construct
new LineDelimiter("delimiter") ; and passed onto TextLineCodecFactory
To specify the same in TextLineCodecfactory, following constructors can be used
public TextLineCodecFactory(Charset charset, String encodingDelimiter, String
decodingDelimiter)
or
public TextLineCodecFactory(Charset charset, LineDelimiter encodingDelimiter,
LineDelimiter decodingDelimiter)
was (Author: paliwalashish):
Not sure if this still an issue. A custom delimiter can be created using
following construct
new LineDelimiter("delimiter") ; and passed onto TextLineCodecFactory
To specify the same in TextLineCodecfactory, following constructors can be used
public TextLineCodecFactory(Charset charset, String encodingDelimiter, String
decodingDelimiter)
or
public TextLineCodecFactory(Charset charset, LineDelimiter encodingDelimiter,
LineDelimiter decodingDelimiter)
> Dynamic delimiter support for TextLineCodecFactory
> --
>
> Key: DIRMINA-586
> URL: https://issues.apache.org/jira/browse/DIRMINA-586
> Project: MINA
> Issue Type: Improvement
> Components: Filter
>Affects Versions: 2.0.0-M1
>Reporter: Trustin Lee
>Priority: Minor
> Fix For: 2.0.0-RC1
>
>
> TextLineCodecFactory supports static delimiters only. For some cases, users
> need to switch the delimiter dynamically depending on context. Related
> discussion is found here:
> http://markmail.org/message/loiqoej35evt2yvv
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-586) Dynamic delimiter support for TextLineCodecFactory
[ https://issues.apache.org/jira/browse/DIRMINA-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658768#action_12658768 ] Ashish Paliwal commented on DIRMINA-586: Hmm... I think I misinterpreted this. I am wondering do we need to have this functionality as part of TextLineCodecFactory. If we do, then how do we determine, when to switch context? Pardon my ignorance, but how many implementation shall need such a implementation? > Dynamic delimiter support for TextLineCodecFactory > -- > > Key: DIRMINA-586 > URL: https://issues.apache.org/jira/browse/DIRMINA-586 > Project: MINA > Issue Type: Improvement > Components: Filter >Affects Versions: 2.0.0-M1 >Reporter: Trustin Lee >Priority: Minor > Fix For: 2.0.0-RC1 > > > TextLineCodecFactory supports static delimiters only. For some cases, users > need to switch the delimiter dynamically depending on context. Related > discussion is found here: > http://markmail.org/message/loiqoej35evt2yvv -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-654) Google Protocol Buffers Codec
[ https://issues.apache.org/jira/browse/DIRMINA-654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663323#action_12663323 ] Ashish Paliwal commented on DIRMINA-654: How about creating the UDP example (Memory Monitor) we have, using Protocol Buffer's. Will be great to show how to achieve the same functionality using different Filters (over different protocols). A good example of how MINA promotes reuse :-) > Google Protocol Buffers Codec > - > > Key: DIRMINA-654 > URL: https://issues.apache.org/jira/browse/DIRMINA-654 > Project: MINA > Issue Type: New Feature > Components: Filter >Reporter: Tomasz Blachowicz > Attachments: protobuf.txt > > > Google Protocol Buffers (protobuf) are language-neutral, platform-neutral, > extensible mechanism for serializing structured data. Apache MINA already > provides several protocol codecs (decoders and encodes) that allows to deal > with different wire formats. The Protocol Buffer is the perfect candidate for > new codec available as separate and optional module within Apache MINA. > More details on Protocol Buffers can be found on the website: > http://code.google.com/apis/protocolbuffers -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRMINA-594) Javadoc & documentation for APR transport
[ https://issues.apache.org/jira/browse/DIRMINA-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal reassigned DIRMINA-594: -- Assignee: Ashish Paliwal > Javadoc & documentation for APR transport > - > > Key: DIRMINA-594 > URL: https://issues.apache.org/jira/browse/DIRMINA-594 > Project: MINA > Issue Type: Improvement > Components: Transport, Web Site / Documentation >Affects Versions: 2.0.0-M1 >Reporter: Julien Vermillard >Assignee: Ashish Paliwal > Fix For: 2.0.0-RC1 > > > The APR transport module is javadoc less and probably need a like > documentation in the wiki (instalation of APR & jni bindings) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-188) All-in-one JAR
[ https://issues.apache.org/jira/browse/DIRMINA-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664817#action_12664817 ] Ashish Paliwal commented on DIRMINA-188: Having an all jar is good. I loved the 2.0.0 M4 release structure. It had all the jars needed and it really helps that we don't have to go looking for all dependencies. > All-in-one JAR > -- > > Key: DIRMINA-188 > URL: https://issues.apache.org/jira/browse/DIRMINA-188 > Project: MINA > Issue Type: Task >Reporter: Trustin Lee >Priority: Minor > > We need two kinds of all-in-one JARs: > * A JAR file which contains all modules > * A JAR file which contains all modules and dependencies > Perhaps we could create two uberjar projects. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-56) Create a Benchmark Suite That Generates HTML Reports.
[ https://issues.apache.org/jira/browse/DIRMINA-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664818#action_12664818 ] Ashish Paliwal commented on DIRMINA-56: --- Its an interesting proposal. What most people like to see is Hardware configuration + MINA's processing/handling power. I could help out with MAC benchmark (if needed) > Create a Benchmark Suite That Generates HTML Reports. > - > > Key: DIRMINA-56 > URL: https://issues.apache.org/jira/browse/DIRMINA-56 > Project: MINA > Issue Type: Task >Reporter: Trustin Lee >Priority: Minor > Fix For: 3.0.0-M1 > > > We need benchmark suite before releasing 0.8 (stable stream) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-657) SSL Filter and IoHandler.
[ https://issues.apache.org/jira/browse/DIRMINA-657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12666443#action_12666443 ] Ashish Paliwal commented on DIRMINA-657: Can the issue be more elaborated, how it shall of help, if these API are added? As per javadoc, these notification can be turned off. > SSL Filter and IoHandler. > - > > Key: DIRMINA-657 > URL: https://issues.apache.org/jira/browse/DIRMINA-657 > Project: MINA > Issue Type: Improvement > Components: Filter, Handler >Affects Versions: 1.1.7 >Reporter: Sanjeev Sachdev >Priority: Minor > > When the session is secured or unsecured, SSLFilter notifies the IOHandler > about the same, by emitting a special message object with a > IoHandler.messageReceived(IoSession, Object) event. > Instead, IOHandler should have events like IoHandler.sessionSecured() and > IoHandler.sessionUnsecured(). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-593) Javadoc & documentation for org/apache/mina/filter/reqres
[ https://issues.apache.org/jira/browse/DIRMINA-593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667597#action_12667597 ] Ashish Paliwal commented on DIRMINA-593: Should we just concentrate on documentation for now and can create examples later on. > Javadoc & documentation for org/apache/mina/filter/reqres > - > > Key: DIRMINA-593 > URL: https://issues.apache.org/jira/browse/DIRMINA-593 > Project: MINA > Issue Type: Improvement > Components: Filter, Web Site / Documentation >Affects Versions: 2.0.0-M1 >Reporter: Julien Vermillard > Fix For: 2.0.0-RC1 > > > no javadoc nor doc on the request/response filter, it need some examples too -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-258) Example of an XML server and Client.
[ https://issues.apache.org/jira/browse/DIRMINA-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12679178#action_12679178 ] Ashish Paliwal commented on DIRMINA-258: Can we have something simpler, like a basic XML Server and Client. We can have two modes, one with a size header and the other is plain XML. There was discussion thread long back, based on which I created a sample and its there on my blog as well. I wold like to create it from scratch. Mark - Can I hijack this issue from you? > Example of an XML server and Client. > > > Key: DIRMINA-258 > URL: https://issues.apache.org/jira/browse/DIRMINA-258 > Project: MINA > Issue Type: New Feature >Reporter: Martin Helmhout >Assignee: Mark Webb >Priority: Minor > Attachments: MINA_XMLServer.zip, MINA_XMLServer.zip, XMLserver095.zip > > > The attachment contains an example of an XML Server + client and should help > start people building their server quickly. > Because an XML server was not in the examples, I created quickly something > for myself, but want others to also get the fruits and make them better if > possible. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRMINA-676) ObjectMBean throws NullPointerException when accessing non-existing attributes
[ https://issues.apache.org/jira/browse/DIRMINA-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal reassigned DIRMINA-676: -- Assignee: Ashish Paliwal > ObjectMBean throws NullPointerException when accessing non-existing attributes > -- > > Key: DIRMINA-676 > URL: https://issues.apache.org/jira/browse/DIRMINA-676 > Project: MINA > Issue Type: Bug > Components: Integration >Affects Versions: 2.0.0-M4 >Reporter: Steve Ulrich >Assignee: Ashish Paliwal >Priority: Trivial > > Currently when someone tries to access an attribute via JMX that doesn't > exist, the ObjectMBean throws a NullPointerException. > It would be better to precheck if the attribute exists and throw an > AttributeNotFoundException with a short info, like "Attribute doesn't > not exist". > Stacktrace: > java.lang.NullPointerException > at > org.apache.mina.integration.jmx.ObjectMBean.getAttribute(ObjectMBean.java:168) > at MyTestClass.main(MyTestClass.java:12) > Exception in thread "main" javax.management.MBeanException > at > org.apache.mina.integration.jmx.ObjectMBean.throwMBeanException(ObjectMBean.java:849) > at > org.apache.mina.integration.jmx.ObjectMBean.getAttribute(ObjectMBean.java:173) > at MyTestClass.main(MyTestClass.java:12) > Caused by: java.lang.NullPointerException > at > org.apache.mina.integration.jmx.ObjectMBean.getAttribute(ObjectMBean.java:168) > ... 1 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIRMINA-676) ObjectMBean throws NullPointerException when accessing non-existing attributes
[ https://issues.apache.org/jira/browse/DIRMINA-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal resolved DIRMINA-676. Resolution: Fixed Fix Version/s: 2.0.0-RC1 Added check for unknown attribute, to avoid null pointer exception. The code checks if the attribute exist, if not an exception is thrown. Files Modified org.apache.mina.integration.jmx.ObjectMBean.java > ObjectMBean throws NullPointerException when accessing non-existing attributes > -- > > Key: DIRMINA-676 > URL: https://issues.apache.org/jira/browse/DIRMINA-676 > Project: MINA > Issue Type: Bug > Components: Integration >Affects Versions: 2.0.0-M4 >Reporter: Steve Ulrich >Assignee: Ashish Paliwal >Priority: Trivial > Fix For: 2.0.0-RC1 > > Attachments: ObjectMBean.java.patch > > > Currently when someone tries to access an attribute via JMX that doesn't > exist, the ObjectMBean throws a NullPointerException. > It would be better to precheck if the attribute exists and throw an > AttributeNotFoundException with a short info, like "Attribute doesn't > not exist". > Stacktrace: > java.lang.NullPointerException > at > org.apache.mina.integration.jmx.ObjectMBean.getAttribute(ObjectMBean.java:168) > at MyTestClass.main(MyTestClass.java:12) > Exception in thread "main" javax.management.MBeanException > at > org.apache.mina.integration.jmx.ObjectMBean.throwMBeanException(ObjectMBean.java:849) > at > org.apache.mina.integration.jmx.ObjectMBean.getAttribute(ObjectMBean.java:173) > at MyTestClass.main(MyTestClass.java:12) > Caused by: java.lang.NullPointerException > at > org.apache.mina.integration.jmx.ObjectMBean.getAttribute(ObjectMBean.java:168) > ... 1 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-676) ObjectMBean throws NullPointerException when accessing non-existing attributes
[ https://issues.apache.org/jira/browse/DIRMINA-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682965#action_12682965 ] Ashish Paliwal commented on DIRMINA-676: Thanks for the patch Steve. Have added the error handling similar to setAttribute(), for consistency. > ObjectMBean throws NullPointerException when accessing non-existing attributes > -- > > Key: DIRMINA-676 > URL: https://issues.apache.org/jira/browse/DIRMINA-676 > Project: MINA > Issue Type: Bug > Components: Integration >Affects Versions: 2.0.0-M4 >Reporter: Steve Ulrich >Assignee: Ashish Paliwal >Priority: Trivial > Attachments: ObjectMBean.java.patch > > > Currently when someone tries to access an attribute via JMX that doesn't > exist, the ObjectMBean throws a NullPointerException. > It would be better to precheck if the attribute exists and throw an > AttributeNotFoundException with a short info, like "Attribute doesn't > not exist". > Stacktrace: > java.lang.NullPointerException > at > org.apache.mina.integration.jmx.ObjectMBean.getAttribute(ObjectMBean.java:168) > at MyTestClass.main(MyTestClass.java:12) > Exception in thread "main" javax.management.MBeanException > at > org.apache.mina.integration.jmx.ObjectMBean.throwMBeanException(ObjectMBean.java:849) > at > org.apache.mina.integration.jmx.ObjectMBean.getAttribute(ObjectMBean.java:173) > at MyTestClass.main(MyTestClass.java:12) > Caused by: java.lang.NullPointerException > at > org.apache.mina.integration.jmx.ObjectMBean.getAttribute(ObjectMBean.java:168) > ... 1 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-678) NioProcessor 100% CPU usage on Linux (epoll selector bug)
[ https://issues.apache.org/jira/browse/DIRMINA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683413#action_12683413 ] Ashish Paliwal commented on DIRMINA-678: JDK Fix may take a while. +1 for fixing it the Gizzly way and write another JIRA issue to keep track of JDK fix and roll back this fix once that is available > NioProcessor 100% CPU usage on Linux (epoll selector bug) > - > > Key: DIRMINA-678 > URL: https://issues.apache.org/jira/browse/DIRMINA-678 > Project: MINA > Issue Type: Bug > Components: Core >Affects Versions: 2.0.0-M4 > Environment: CentOS 5.x, 32/64-bit, 32/64-bit Sun JDK 1.6.0_12, also > _11/_10/_09 and Sun JDK 1.7.0 b50, Kernel 2.6.18-92.1.22.el5 and also older > versions, >Reporter: Serge Baranov > Attachments: snap973.png, snap974.png > > > It's the same bug as described at http://jira.codehaus.org/browse/JETTY-937 , > but affecting MINA in the very similar way. > NioProcessor threads start to eat 100% resources per CPU. After 10-30 minutes > of running depending on the load (sometimes after several hours) one of the > NioProcessor starts to consume all the available CPU resources probably > spinning in the epoll select loop. Later, more threads can be affected by the > same issue, thus 100% loading all the available CPU cores. > Sample trace: > NioProcessor-10 [RUNNABLE] CPU time: 5:15 > sun.nio.ch.EPollArrayWrapper.epollWait(long, int, long, int) > sun.nio.ch.EPollArrayWrapper.poll(long) > sun.nio.ch.EPollSelectorImpl.doSelect(long) > sun.nio.ch.SelectorImpl.lockAndDoSelect(long) > sun.nio.ch.SelectorImpl.select(long) > org.apache.mina.transport.socket.nio.NioProcessor.select(long) > org.apache.mina.core.polling.AbstractPollingIoProcessor$Processor.run() > org.apache.mina.util.NamePreservingRunnable.run() > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) > java.util.concurrent.ThreadPoolExecutor$Worker.run() > java.lang.Thread.run() > It seems to affect any NIO based Java server applications running in the > specified environment. > Some projects provide workarounds for similar JDK bugs, probably MINA can > also think about a workaround. > As far as I know, there are at least 3 users who experience this issue with > Jetty and all of them are running CentOS (some distribution default setting > is a trigger?). As for MINA, I'm not aware of similar reports yet. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIRMINA-594) Javadoc & documentation for APR transport
[ https://issues.apache.org/jira/browse/DIRMINA-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal resolved DIRMINA-594. Resolution: Fixed Credits to Julien for adding majority of Javadoc. Wiki page on APR Transport added at http://mina.apache.org/apr-transport.html > Javadoc & documentation for APR transport > - > > Key: DIRMINA-594 > URL: https://issues.apache.org/jira/browse/DIRMINA-594 > Project: MINA > Issue Type: Improvement > Components: Transport, Web Site / Documentation >Affects Versions: 2.0.0-M1 >Reporter: Julien Vermillard >Assignee: Ashish Paliwal > Fix For: 2.0.0-RC1 > > > The APR transport module is javadoc less and probably need a like > documentation in the wiki (instalation of APR & jni bindings) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRMINA-617) JMX - IoServiceMBean doesn't expose IoService statistics
[ https://issues.apache.org/jira/browse/DIRMINA-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal reassigned DIRMINA-617: -- Assignee: Ashish Paliwal > JMX - IoServiceMBean doesn't expose IoService statistics > > > Key: DIRMINA-617 > URL: https://issues.apache.org/jira/browse/DIRMINA-617 > Project: MINA > Issue Type: Bug > Components: Core >Affects Versions: 2.0.0-M3 >Reporter: simon trudeau >Assignee: Ashish Paliwal > Fix For: 3.0.0-M1 > > > As of Mina 2.0.0-M3 it is not possible to browse Mina's statistics using JMX > and IoServiceMBean. Only the object memory address is exposed and not its > attributes. > This should also be looked into for IoSession too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRMINA-237) Improve Spring integration
[ https://issues.apache.org/jira/browse/DIRMINA-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal reassigned DIRMINA-237: -- Assignee: Ashish Paliwal > Improve Spring integration > -- > > Key: DIRMINA-237 > URL: https://issues.apache.org/jira/browse/DIRMINA-237 > Project: MINA > Issue Type: Improvement >Affects Versions: 0.9.4 >Reporter: Niklas Therning >Assignee: Ashish Paliwal >Priority: Minor > Fix For: 3.0.0-M1 > > > The Spring integration module is in need of an overhaul. There are some > things that aren't that simple to configure like the default IoService > config. Also, Spring 2.0 is due to be released very soon. We should add > support for the custom XML configuration feature introduced with Spring 2.0. > That would let users write things like (just brainstorming here): > threadPoolMaxSize="20" threadPoolKeepAlive="3"> > > > > > > > Of course, we should still support and make life easier for people who don't > use Spring 2.0. > I'd like to know what people using the Spring integration think should be > made to make it easier to use. Please add your comments to this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-32) Revise JavaDoc, PPT, and Tutorial
[ https://issues.apache.org/jira/browse/DIRMINA-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694037#action_12694037 ] Ashish Paliwal commented on DIRMINA-32: --- Lets close this issue. We have new PPT, most of the documentation section is updated. Javadoc's are decent, and can be refined as we go forward. > Revise JavaDoc, PPT, and Tutorial > - > > Key: DIRMINA-32 > URL: https://issues.apache.org/jira/browse/DIRMINA-32 > Project: MINA > Issue Type: Task > Components: Web Site / Documentation >Affects Versions: 2.0.0-M3 >Reporter: Trustin Lee > Fix For: 2.0.0-RC1 > > > 0.9 will integrate I/O layer and Protocol layer. We need up-to-date > documentation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRMINA-695) Code: Adjust code to MINA conventions (headers etc.)
[ https://issues.apache.org/jira/browse/DIRMINA-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal reassigned DIRMINA-695: -- Assignee: Ashish Paliwal > Code: Adjust code to MINA conventions (headers etc.) > > > Key: DIRMINA-695 > URL: https://issues.apache.org/jira/browse/DIRMINA-695 > Project: MINA > Issue Type: Sub-task >Reporter: Bernd Fondermann >Assignee: Ashish Paliwal > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-695) Code: Adjust code to MINA conventions (headers etc.)
[ https://issues.apache.org/jira/browse/DIRMINA-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12701133#action_12701133 ] Ashish Paliwal commented on DIRMINA-695: All headers are in sync with MINA style. Though svn auto-props Revision is not working for my commits. Should I resolve this issue or keep it open to address more convention fixes? It can be taken care as we move along and refine the code. > Code: Adjust code to MINA conventions (headers etc.) > > > Key: DIRMINA-695 > URL: https://issues.apache.org/jira/browse/DIRMINA-695 > Project: MINA > Issue Type: Sub-task >Reporter: Bernd Fondermann >Assignee: Ashish Paliwal > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIRMINA-695) Code: Adjust code to MINA conventions (headers etc.)
[ https://issues.apache.org/jira/browse/DIRMINA-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal resolved DIRMINA-695. Resolution: Fixed Header's in place for all the files > Code: Adjust code to MINA conventions (headers etc.) > > > Key: DIRMINA-695 > URL: https://issues.apache.org/jira/browse/DIRMINA-695 > Project: MINA > Issue Type: Sub-task >Reporter: Bernd Fondermann >Assignee: Ashish Paliwal > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (VYSPER-154) Handle inbound Presence Probes correctly
[ https://issues.apache.org/jira/browse/VYSPER-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736450#action_12736450 ] Ashish Paliwal commented on VYSPER-154: --- Can we explore the possibility of using a 3rd party lib like ehcache for cache imlpementation? > Handle inbound Presence Probes correctly > > > Key: VYSPER-154 > URL: https://issues.apache.org/jira/browse/VYSPER-154 > Project: VYSPER > Issue Type: Bug > Components: core protocol >Reporter: Bernd Fondermann >Assignee: Bernd Fondermann > > If the contact-side of a presence probe is not available (offline), > everything works fine. > If the contact-side of a presence probe is available, two things happen: > 1. the probed entity is checked for a resource, which fails. This is wrong. > 2. the presence lookup fails, because of there is no resource on the probed > entity. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (VYSPER-154) Handle inbound Presence Probes correctly
[ https://issues.apache.org/jira/browse/VYSPER-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12736497#action_12736497 ] Ashish Paliwal commented on VYSPER-154: --- Yup, a little. Let me work on this and provide an implementation based on ehcache. Then you can help me integrate and test the same > Handle inbound Presence Probes correctly > > > Key: VYSPER-154 > URL: https://issues.apache.org/jira/browse/VYSPER-154 > Project: VYSPER > Issue Type: Bug > Components: core protocol >Reporter: Bernd Fondermann >Assignee: Bernd Fondermann > > If the contact-side of a presence probe is not available (offline), > everything works fine. > If the contact-side of a presence probe is available, two things happen: > 1. the probed entity is checked for a resource, which fails. This is wrong. > 2. the presence lookup fails, because of there is no resource on the probed > entity. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (VYSPER-164) Add EhCache based LatestPresenceCache
Add EhCache based LatestPresenceCache - Key: VYSPER-164 URL: https://issues.apache.org/jira/browse/VYSPER-164 Project: VYSPER Issue Type: Improvement Reporter: Ashish Paliwal Assignee: Ashish Paliwal Priority: Minor Add EhCache based LatestPresenceCache. EhCache is pure caching solution and its better to use cache library to use, instead of writing own cache implementation -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (VYSPER-164) Add EhCache based LatestPresenceCache
[ https://issues.apache.org/jira/browse/VYSPER-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737868#action_12737868 ] Ashish Paliwal commented on VYSPER-164: --- Add this to Maven Repository list for EhCache based implementation to compile http://oss.sonatype.org/content/repositories/sourceforge-releases > Add EhCache based LatestPresenceCache > - > > Key: VYSPER-164 > URL: https://issues.apache.org/jira/browse/VYSPER-164 > Project: VYSPER > Issue Type: Improvement >Reporter: Ashish Paliwal >Assignee: Ashish Paliwal >Priority: Minor > Original Estimate: 24h > Remaining Estimate: 24h > > Add EhCache based LatestPresenceCache. EhCache is pure caching solution and > its better to use cache library to use, instead of writing own cache > implementation -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (VYSPER-164) Add EhCache based LatestPresenceCache
[ https://issues.apache.org/jira/browse/VYSPER-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal resolved VYSPER-164. --- Resolution: Fixed EhCache based cache implementation added. Need to be integrated with core > Add EhCache based LatestPresenceCache > - > > Key: VYSPER-164 > URL: https://issues.apache.org/jira/browse/VYSPER-164 > Project: VYSPER > Issue Type: Improvement >Reporter: Ashish Paliwal >Assignee: Ashish Paliwal >Priority: Minor > Original Estimate: 24h > Remaining Estimate: 24h > > Add EhCache based LatestPresenceCache. EhCache is pure caching solution and > its better to use cache library to use, instead of writing own cache > implementation -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (VYSPER-39) Infra: Move Vysper cwiki pages
[ https://issues.apache.org/jira/browse/VYSPER-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal reassigned VYSPER-39: Assignee: Ashish Paliwal > Infra: Move Vysper cwiki pages > -- > > Key: VYSPER-39 > URL: https://issues.apache.org/jira/browse/VYSPER-39 > Project: VYSPER > Issue Type: Sub-task >Reporter: Bernd Fondermann >Assignee: Ashish Paliwal > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (VYSPER-39) Infra: Move Vysper cwiki pages
[ https://issues.apache.org/jira/browse/VYSPER-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737919#action_12737919 ] Ashish Paliwal commented on VYSPER-39: -- Wiki Content migrated. Formatting shall be updated once, the wiki layout is finalized > Infra: Move Vysper cwiki pages > -- > > Key: VYSPER-39 > URL: https://issues.apache.org/jira/browse/VYSPER-39 > Project: VYSPER > Issue Type: Sub-task >Reporter: Bernd Fondermann >Assignee: Ashish Paliwal > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (VYSPER-39) Infra: Move Vysper cwiki pages
[ https://issues.apache.org/jira/browse/VYSPER-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal resolved VYSPER-39. -- Resolution: Fixed Wiki Content migrated. Verify and re-open if something is missing > Infra: Move Vysper cwiki pages > -- > > Key: VYSPER-39 > URL: https://issues.apache.org/jira/browse/VYSPER-39 > Project: VYSPER > Issue Type: Sub-task >Reporter: Bernd Fondermann >Assignee: Ashish Paliwal > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (VYSPER-166) EhCache implementation to support configurable config file
EhCache implementation to support configurable config file -- Key: VYSPER-166 URL: https://issues.apache.org/jira/browse/VYSPER-166 Project: VYSPER Issue Type: Improvement Reporter: Ashish Paliwal Assignee: Ashish Paliwal Priority: Minor Add support for configuration of ehcache config file -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (VYSPER-166) EhCache implementation to support configurable config file
[ https://issues.apache.org/jira/browse/VYSPER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal resolved VYSPER-166. --- Resolution: Fixed Added support for configuring ehcache.xml Default shall be picked from classpath > EhCache implementation to support configurable config file > -- > > Key: VYSPER-166 > URL: https://issues.apache.org/jira/browse/VYSPER-166 > Project: VYSPER > Issue Type: Improvement >Reporter: Ashish Paliwal >Assignee: Ashish Paliwal >Priority: Minor > > Add support for configuration of ehcache config file -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-477) Update page about differences between 1.x and 2.x
[ https://issues.apache.org/jira/browse/DIRMINA-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741310#action_12741310 ] Ashish Paliwal commented on DIRMINA-477: Have added some basic details on JMX and Spring integration. Since the modules have been re-written, adding precise differences shall not help. Do we know of any other stuff that needs to be documented or we close this issue? > Update page about differences between 1.x and 2.x > - > > Key: DIRMINA-477 > URL: https://issues.apache.org/jira/browse/DIRMINA-477 > Project: MINA > Issue Type: Task > Components: Web Site / Documentation >Reporter: Trustin Lee >Assignee: Trustin Lee > Fix For: 2.0.0-RC1 > > > Our current web site doesn't describe what have been changed in 2.x comparing > to 1.x. We need to carefully put all changes together there so people can > migrate more easily. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRMINA-477) Update page about differences between 1.x and 2.x
[ https://issues.apache.org/jira/browse/DIRMINA-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal reassigned DIRMINA-477: -- Assignee: Ashish Paliwal (was: Trustin Lee) > Update page about differences between 1.x and 2.x > - > > Key: DIRMINA-477 > URL: https://issues.apache.org/jira/browse/DIRMINA-477 > Project: MINA > Issue Type: Task > Components: Web Site / Documentation >Reporter: Trustin Lee >Assignee: Ashish Paliwal > Fix For: 2.0.0-RC1 > > > Our current web site doesn't describe what have been changed in 2.x comparing > to 1.x. We need to carefully put all changes together there so people can > migrate more easily. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-575) Add the missing Javadoc, add some comments
[ https://issues.apache.org/jira/browse/DIRMINA-575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741312#action_12741312 ] Ashish Paliwal commented on DIRMINA-575: This JIRA issue is very generic and we may not be able to close it. We may choose to create specific JIRA issues for places where we want to add documentation and close this issue. wdyt? > Add the missing Javadoc, add some comments > -- > > Key: DIRMINA-575 > URL: https://issues.apache.org/jira/browse/DIRMINA-575 > Project: MINA > Issue Type: Task > Components: Web Site / Documentation >Reporter: Emmanuel Lecharny >Priority: Blocker > Fix For: 2.0.0-RC1 > > > If we except the interfaces, the code lacks of javadoc and comments, which > make it complicated for new committers to get into it. > We need to add those missing javadocs, and comments where it's necessary. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRMINA-593) Javadoc & documentation for org/apache/mina/filter/reqres
[ https://issues.apache.org/jira/browse/DIRMINA-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal reassigned DIRMINA-593: -- Assignee: Ashish Paliwal > Javadoc & documentation for org/apache/mina/filter/reqres > - > > Key: DIRMINA-593 > URL: https://issues.apache.org/jira/browse/DIRMINA-593 > Project: MINA > Issue Type: Improvement > Components: Filter, Web Site / Documentation >Affects Versions: 2.0.0-M1 >Reporter: Julien Vermillard >Assignee: Ashish Paliwal > Fix For: 2.0.0-RC1 > > > no javadoc nor doc on the request/response filter, it need some examples too -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (VYSPER-164) Add EhCache based LatestPresenceCache
[ https://issues.apache.org/jira/browse/VYSPER-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal closed VYSPER-164. - Fixed > Add EhCache based LatestPresenceCache > - > > Key: VYSPER-164 > URL: https://issues.apache.org/jira/browse/VYSPER-164 > Project: VYSPER > Issue Type: Improvement >Reporter: Ashish Paliwal >Assignee: Ashish Paliwal >Priority: Minor > Original Estimate: 24h > Remaining Estimate: 24h > > Add EhCache based LatestPresenceCache. EhCache is pure caching solution and > its better to use cache library to use, instead of writing own cache > implementation -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (VYSPER-166) EhCache implementation to support configurable config file
[ https://issues.apache.org/jira/browse/VYSPER-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal closed VYSPER-166. - > EhCache implementation to support configurable config file > -- > > Key: VYSPER-166 > URL: https://issues.apache.org/jira/browse/VYSPER-166 > Project: VYSPER > Issue Type: Improvement >Reporter: Ashish Paliwal >Assignee: Ashish Paliwal >Priority: Minor > > Add support for configuration of ehcache config file -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (ASYNCWEB-17) Project URL in JIRA is wrong
[ https://issues.apache.org/jira/browse/ASYNCWEB-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756457#action_12756457 ] Ashish Paliwal commented on ASYNCWEB-17: Seems this is working some how. Lets close this issue :-) > Project URL in JIRA is wrong > > > Key: ASYNCWEB-17 > URL: https://issues.apache.org/jira/browse/ASYNCWEB-17 > Project: Asyncweb > Issue Type: Bug >Reporter: Stepan Koltsov > > http://screencast.com/t/tMCqhf60 > link http://mina.apache.org/asyncweb from > https://issues.apache.org/jira/browse/ASYNCWEB is 404 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRMINA-258) 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 reassigned DIRMINA-258: -- Assignee: Ashish Paliwal (was: Mark Webb) > Example of an XML server and Client. > > > Key: DIRMINA-258 > URL: https://issues.apache.org/jira/browse/DIRMINA-258 > Project: MINA > Issue Type: New Feature >Reporter: Martin Helmhout >Assignee: Ashish Paliwal >Priority: Minor > Attachments: MINA_XMLServer.zip, MINA_XMLServer.zip, XMLserver095.zip > > > The attachment contains an example of an XML Server + client and should help > start people building their server quickly. > Because an XML server was not in the examples, I created quickly something > for myself, but want others to also get the fruits and make them better if > possible. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRMINA-258) 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 and Client. > > > Key: DIRMINA-258 > URL: https://issues.apache.org/jira/browse/DIRMINA-258 > Project: MINA > Issue Type: New Feature > Components: Example >Reporter: Martin Helmhout >Assignee: Ashish Paliwal >Priority: Minor > Fix For: 3.0.0-M1 > > Attachments: MINA_XMLServer.zip, MINA_XMLServer.zip, XMLserver095.zip > > > The attachment contains an example of an XML Server + client and should help > start people building their server quickly. > Because an XML server was not in the examples, I created quickly something > for myself, but want others to also get the fruits and make them better if > possible. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-758) APR code needs unit tests
[ https://issues.apache.org/jira/browse/DIRMINA-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12804065#action_12804065 ] Ashish Paliwal commented on DIRMINA-758: Which release do we fit this into? Seems like we can move this to 3.0 > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (DIRMINA-784) Error with MDCInjectionFilter on Windows
[ https://issues.apache.org/jira/browse/DIRMINA-784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal reassigned DIRMINA-784: -- Assignee: Ashish Paliwal > Error with MDCInjectionFilter on Windows > > > Key: DIRMINA-784 > URL: https://issues.apache.org/jira/browse/DIRMINA-784 > Project: MINA > Issue Type: Bug >Affects Versions: 2.0.0-RC1 >Reporter: Emmanuel Lecharny >Assignee: Ashish Paliwal > Fix For: 2.0.0 > > > One test is randomly failing on Windows only : > http://hudson.zones.apache.org/hudson/job/MINA-trunk-jdk1.6-windows/lastBuild/org.apache.mina$mina-core/testReport/org.apache.mina.filter.logging/MdcInjectionFilterTest/testOnlyRemoteAddress/ > It may be the test which is broken, or something we added since the last > version, as it was working in 2.0.0-RC1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-784) Error with MDCInjectionFilter on Windows
[ https://issues.apache.org/jira/browse/DIRMINA-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865675#action_12865675 ] Ashish Paliwal commented on DIRMINA-784: The problem is reproducible on my machine :) The timeout for the session is set to 1 sec, in the SimpleIoHandler. I increased it to 5 sec, and seems the error is gone for the time being. I am really not sure if this is the cause of the error. Will try to run the modified test atleast 20-25 time before committing the changes. The reason that lead me to the error was _Session closed_ event was fired. I hope we don't have a race condition hiding somewhere :) > Error with MDCInjectionFilter on Windows > > > Key: DIRMINA-784 > URL: https://issues.apache.org/jira/browse/DIRMINA-784 > Project: MINA > Issue Type: Bug >Affects Versions: 2.0.0-RC1 >Reporter: Emmanuel Lecharny >Assignee: Ashish Paliwal > Fix For: 2.0.0 > > > One test is randomly failing on Windows only : > http://hudson.zones.apache.org/hudson/job/MINA-trunk-jdk1.6-windows/lastBuild/org.apache.mina$mina-core/testReport/org.apache.mina.filter.logging/MdcInjectionFilterTest/testOnlyRemoteAddress/ > It may be the test which is broken, or something we added since the last > version, as it was working in 2.0.0-RC1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-784) Error with MDCInjectionFilter on Windows
[ https://issues.apache.org/jira/browse/DIRMINA-784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865689#action_12865689 ] Ashish Paliwal commented on DIRMINA-784: Cool :) I am glad you found the bug and I can't stop laughing at my solution :( Anyways, the final hurdle for the 2.0 release is about to be cleared. Will wait for the commit. > Error with MDCInjectionFilter on Windows > > > Key: DIRMINA-784 > URL: https://issues.apache.org/jira/browse/DIRMINA-784 > Project: MINA > Issue Type: Bug >Affects Versions: 2.0.0-RC1 >Reporter: Emmanuel Lecharny >Assignee: Ashish Paliwal > Fix For: 2.0.0 > > > One test is randomly failing on Windows only : > http://hudson.zones.apache.org/hudson/job/MINA-trunk-jdk1.6-windows/lastBuild/org.apache.mina$mina-core/testReport/org.apache.mina.filter.logging/MdcInjectionFilterTest/testOnlyRemoteAddress/ > It may be the test which is broken, or something we added since the last > version, as it was working in 2.0.0-RC1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-780) Writing null objects to the Session should raise an Exception
[
https://issues.apache.org/jira/browse/DIRMINA-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867124#action_12867124
]
Ashish Paliwal commented on DIRMINA-780:
Write API guards against null objects, here is the snippet from
AbstractIoSession from trunk
/**
* {...@inheritdoc}
*/
public WriteFuture write(Object message) {
return write(message, null);
}
/**
* {...@inheritdoc}
*/
public WriteFuture write(Object message, SocketAddress remoteAddress) {
if (message == null) {
throw new NullPointerException("message");
}
..
Am I looking at wrong place ?
> Writing null objects to the Session should raise an Exception
> -
>
> Key: DIRMINA-780
> URL: https://issues.apache.org/jira/browse/DIRMINA-780
> Project: MINA
> Issue Type: Improvement
> Components: Core
>Affects Versions: 2.0.0-RC1
>Reporter: Norman Maurer
> Fix For: 2.0.0
>
>
> When using MINA in JAMES we saw malformated packets when processing POP3.
> This was a cause of a bug in our code which wrote a "null" object to the
> session. Unfortunally MINA don't throw an exception in this case and just
> write garbage to the session. We only found the bug because we have a netty
> implementation too which throws a NullPointerException in this case.
> I think MINA should do something similar..
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-788) RequestResponseFilter - Javadoc and Examples
[ https://issues.apache.org/jira/browse/DIRMINA-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12875548#action_12875548 ] Ashish Paliwal commented on DIRMINA-788: There is already a JIRA for this https://issues.apache.org/jira/browse/DIRMINA-593 > RequestResponseFilter - Javadoc and Examples > > > Key: DIRMINA-788 > URL: https://issues.apache.org/jira/browse/DIRMINA-788 > Project: MINA > Issue Type: Wish > Components: Web Site / Documentation >Affects Versions: 2.0.0-RC1 > Environment: Windows XP, IDE Eclipse, JDK 1.6.0_16 >Reporter: Alan Amir >Priority: Trivial > Fix For: 2.0.0-RC1 > > > I have my doubts about MINA's RequestResponseFilter & I would like to know if > anyone have an idea when are going to post the javadoc from Mina's Filter > Request Response package?? > I also viewed the next 2 references but I still have some questions about its > operation. Kind regards and thanks for any help with this issue. > * https://issues.apache.org/jira/browse/DIRMINA-92#action_12488311 > * > http://svn.apache.org/viewvc/mina/trunk/core/src/main/java/org/apache/mina/filter/reqres/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DIRMINA-793) [3.0] Remove Log4j dependency from org.apache.mina.service.SelectorFactory
[3.0] Remove Log4j dependency from org.apache.mina.service.SelectorFactory -- Key: DIRMINA-793 URL: https://issues.apache.org/jira/browse/DIRMINA-793 Project: MINA Issue Type: Bug Components: Core Affects Versions: 3.0.0-M1 Reporter: Ashish Paliwal Assignee: Ashish Paliwal Priority: Minor Fix For: 3.0.0-M1 Remove direct dependency of log4j from org.apache.mina.service.SelectorFactory. Replace with slf4j usage -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIRMINA-793) [3.0] Remove Log4j dependency from org.apache.mina.service.SelectorFactory
[ https://issues.apache.org/jira/browse/DIRMINA-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal resolved DIRMINA-793. Resolution: Fixed Removed Lo4j dependency > [3.0] Remove Log4j dependency from org.apache.mina.service.SelectorFactory > -- > > Key: DIRMINA-793 > URL: https://issues.apache.org/jira/browse/DIRMINA-793 > Project: MINA > Issue Type: Bug > Components: Core >Affects Versions: 3.0.0-M1 >Reporter: Ashish Paliwal >Assignee: Ashish Paliwal >Priority: Minor > Fix For: 3.0.0-M1 > > > Remove direct dependency of log4j from > org.apache.mina.service.SelectorFactory. Replace with slf4j usage -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (DIRMINA-793) [3.0] Remove Log4j dependency from org.apache.mina.service.SelectorFactory
[ https://issues.apache.org/jira/browse/DIRMINA-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899491#action_12899491 ] Ashish Paliwal edited comment on DIRMINA-793 at 8/17/10 1:47 PM: - Removed Log4j dependency was (Author: paliwalashish): Removed Lo4j dependency > [3.0] Remove Log4j dependency from org.apache.mina.service.SelectorFactory > -- > > Key: DIRMINA-793 > URL: https://issues.apache.org/jira/browse/DIRMINA-793 > Project: MINA > Issue Type: Bug > Components: Core >Affects Versions: 3.0.0-M1 >Reporter: Ashish Paliwal >Assignee: Ashish Paliwal >Priority: Minor > Fix For: 3.0.0-M1 > > > Remove direct dependency of log4j from > org.apache.mina.service.SelectorFactory. Replace with slf4j usage -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRMINA-793) [3.0] Remove Log4j dependency from org.apache.mina.service.SelectorFactory
[ https://issues.apache.org/jira/browse/DIRMINA-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal closed DIRMINA-793. -- Resolved and Closed > [3.0] Remove Log4j dependency from org.apache.mina.service.SelectorFactory > -- > > Key: DIRMINA-793 > URL: https://issues.apache.org/jira/browse/DIRMINA-793 > Project: MINA > Issue Type: Bug > Components: Core >Affects Versions: 3.0.0-M1 >Reporter: Ashish Paliwal >Assignee: Ashish Paliwal >Priority: Minor > Fix For: 3.0.0-M1 > > > Remove direct dependency of log4j from > org.apache.mina.service.SelectorFactory. Replace with slf4j usage -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (VYSPER-40) Code: Adjust code to MINA conventions (headers etc.)
[ https://issues.apache.org/jira/browse/VYSPER-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902349#action_12902349 ] Ashish Paliwal commented on VYSPER-40: -- Is there any more work needed for this JIRA or we can resolve this? > Code: Adjust code to MINA conventions (headers etc.) > > > Key: VYSPER-40 > URL: https://issues.apache.org/jira/browse/VYSPER-40 > Project: VYSPER > Issue Type: Sub-task >Reporter: Bernd Fondermann > Attachments: vysper-license.patch > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (VYSPER-245) Update ehcache dependency to latest version
Update ehcache dependency to latest version --- Key: VYSPER-245 URL: https://issues.apache.org/jira/browse/VYSPER-245 Project: VYSPER Issue Type: Improvement Affects Versions: 0.6 Reporter: Ashish Paliwal Priority: Minor Fix For: 0.6 Update ehcache dependency from 1.6.0 to 2.2.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (VYSPER-245) Update ehcache dependency to latest version
[ https://issues.apache.org/jira/browse/VYSPER-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902393#action_12902393 ] Ashish Paliwal commented on VYSPER-245: --- Yes.. its all we need :) It depends on slf4j, which we already have. There are other features like unlocked reads etc that can be very useful, but as of now we are good. Can close this issue. > Update ehcache dependency to latest version > --- > > Key: VYSPER-245 > URL: https://issues.apache.org/jira/browse/VYSPER-245 > Project: VYSPER > Issue Type: Improvement >Affects Versions: 0.6 >Reporter: Ashish Paliwal >Priority: Minor > Fix For: 0.6 > > > Update ehcache dependency from 1.6.0 to 2.2.0 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (VYSPER-243) Bosh inactivity checking thread
[ https://issues.apache.org/jira/browse/VYSPER-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902402#action_12902402 ] Ashish Paliwal commented on VYSPER-243: --- I don't think this is correct, that Timer.schedule will create a thread for every session. Here is note from javadoc This class scales to large numbers of concurrently scheduled tasks (thousands should present no problem). Internally, it uses a binary heap to represent its task queue, so the cost to schedule a task is O(log n), where n is the number of concurrently scheduled tasks. However, moving to a more simple approach is better. > Bosh inactivity checking thread > --- > > Key: VYSPER-243 > URL: https://issues.apache.org/jira/browse/VYSPER-243 > Project: VYSPER > Issue Type: Improvement > Components: BOSH >Reporter: Bogdan Pistol >Priority: Minor > > There should be a single checking thread that will periodically check to see > if there are sessions that passed their inactivity time. > Right now this is done for every session with Timer.schedule that creates a > thread for every session, which is not scalable (the number of threads > increases linearly with the number of concurrent sessions). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-761) how to shutdown a mina application
[ https://issues.apache.org/jira/browse/DIRMINA-761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926949#action_12926949 ] Ashish Paliwal commented on DIRMINA-761: This is covered under FAQ at http://mina.apache.org/faq.html#FAQ-HowdoIclosemysessionsanddisposemyConnector%2526%252363%253B Do we need to move it to User Guide as well? > how to shutdown a mina application > -- > > Key: DIRMINA-761 > URL: https://issues.apache.org/jira/browse/DIRMINA-761 > Project: MINA > Issue Type: Improvement > Components: Web Site / Documentation >Affects Versions: 2.0.0-RC1 >Reporter: José Vilmar Estácio de Souza >Priority: Minor > Fix For: 2.0.2 > > > I'd like to know how to shutdown a mina application in an elegant way. > Actually I kill my applications pressing ctrl+c. > What I'd like: > a: Block incoming connections. > b: Close all open sessions gracefully. > C: Finish the application. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DIRMINA-788) RequestResponseFilter - Javadoc and Examples
[ https://issues.apache.org/jira/browse/DIRMINA-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal resolved DIRMINA-788. Resolution: Duplicate Duplicate of DIRMINA-593 > RequestResponseFilter - Javadoc and Examples > > > Key: DIRMINA-788 > URL: https://issues.apache.org/jira/browse/DIRMINA-788 > Project: MINA > Issue Type: Wish > Components: Web Site / Documentation >Affects Versions: 2.0.0-RC1 > Environment: Windows XP, IDE Eclipse, JDK 1.6.0_16 >Reporter: Alan Amir >Priority: Trivial > Fix For: 2.0.3 > > > I have my doubts about MINA's RequestResponseFilter & I would like to know if > anyone have an idea when are going to post the javadoc from Mina's Filter > Request Response package?? > I also viewed the next 2 references but I still have some questions about its > operation. Kind regards and thanks for any help with this issue. > * https://issues.apache.org/jira/browse/DIRMINA-92#action_12488311 > * > http://svn.apache.org/viewvc/mina/trunk/core/src/main/java/org/apache/mina/filter/reqres/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DIRMINA-617) JMX - IoServiceMBean doesn't expose IoService statistics
[ https://issues.apache.org/jira/browse/DIRMINA-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975972#action_12975972 ] Ashish Paliwal commented on DIRMINA-617: Just ran the Image Server example and was able to see Session details and other stuff via jconsole. Slightly confused here, as to what is expected. > JMX - IoServiceMBean doesn't expose IoService statistics > > > Key: DIRMINA-617 > URL: https://issues.apache.org/jira/browse/DIRMINA-617 > Project: MINA > Issue Type: Bug > Components: Core >Affects Versions: 2.0.0-M3 >Reporter: simon trudeau >Assignee: Ashish Paliwal > Fix For: 3.0.0-M1 > > > As of Mina 2.0.0-M3 it is not possible to browse Mina's statistics using JMX > and IoServiceMBean. Only the object memory address is exposed and not its > attributes. > This should also be looked into for IoSession too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] [Commented] (VYSPER-294) EhCachePresenceCacheImpl initialize CacheManager not use the configFile passed in
[
https://issues.apache.org/jira/browse/VYSPER-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107674#comment-13107674
]
Ashish Paliwal commented on VYSPER-294:
---
Good Catch. My bad, I missed this.
Shall push in the patch soon. Thanks !
> EhCachePresenceCacheImpl initialize CacheManager not use the configFile
> passed in
> -
>
> Key: VYSPER-294
> URL: https://issues.apache.org/jira/browse/VYSPER-294
> Project: VYSPER
> Issue Type: Bug
> Components: core protocol
>Affects Versions: 0.8
> Environment: no special environment
>Reporter: Zhang JinYan
> Labels: patch
> Attachments: xmpp.patch
>
>
> 1、The EhCachePresenceCacheImpl has a constructor arg, which specify the
> configFile used to initialize a EhCache CacheManager,but didn't use it at
> last.
> Code:
> protected void createCache(String configFile) {
> if (configFile == null) {
> configFile = DEFAULT_EHCACHE_CONFIG_FILE;
> }
> URL configFileURL = getClass().getResource(configFile);
> if (configFileURL == null) {
> throw new RuntimeException("ehcache configuration file
> ehcache.xml not found on classpath");
> }
> CacheManager.create(); //<== Here i am!
> presenceCache = CacheManager.getInstance().getCache(PRESENCE_CACHE);
> jidPresenceCache =
> CacheManager.getInstance().getCache(JID_PRESENCE_CACHE);
> }
> 2、dist/src/main/assembly/src.xml
> Didn't excludes .* file/folde in sub directory. If i use eclipse to import
> those projects, there will create .* files (eclipse project files,eg:
> .classpath)
>
> **/target/**
> .*
> .*/** //<== Here i am!
> **.bak
>
> I upload my patch.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (VYSPER-294) EhCachePresenceCacheImpl initialize CacheManager not use the configFile passed in
[
https://issues.apache.org/jira/browse/VYSPER-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Paliwal reassigned VYSPER-294:
-
Assignee: Ashish Paliwal
> EhCachePresenceCacheImpl initialize CacheManager not use the configFile
> passed in
> -
>
> Key: VYSPER-294
> URL: https://issues.apache.org/jira/browse/VYSPER-294
> Project: VYSPER
> Issue Type: Bug
> Components: core protocol
>Affects Versions: 0.8
> Environment: no special environment
>Reporter: Zhang JinYan
>Assignee: Ashish Paliwal
> Labels: patch
> Attachments: xmpp.patch
>
>
> 1、The EhCachePresenceCacheImpl has a constructor arg, which specify the
> configFile used to initialize a EhCache CacheManager,but didn't use it at
> last.
> Code:
> protected void createCache(String configFile) {
> if (configFile == null) {
> configFile = DEFAULT_EHCACHE_CONFIG_FILE;
> }
> URL configFileURL = getClass().getResource(configFile);
> if (configFileURL == null) {
> throw new RuntimeException("ehcache configuration file
> ehcache.xml not found on classpath");
> }
> CacheManager.create(); //<== Here i am!
> presenceCache = CacheManager.getInstance().getCache(PRESENCE_CACHE);
> jidPresenceCache =
> CacheManager.getInstance().getCache(JID_PRESENCE_CACHE);
> }
> 2、dist/src/main/assembly/src.xml
> Didn't excludes .* file/folde in sub directory. If i use eclipse to import
> those projects, there will create .* files (eclipse project files,eg:
> .classpath)
>
> **/target/**
> .*
> .*/** //<== Here i am!
> **.bak
>
> I upload my patch.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (VYSPER-294) EhCachePresenceCacheImpl initialize CacheManager not use the configFile passed in
[
https://issues.apache.org/jira/browse/VYSPER-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Paliwal resolved VYSPER-294.
---
Resolution: Fixed
Applied the patch, and added test case to test the same
> EhCachePresenceCacheImpl initialize CacheManager not use the configFile
> passed in
> -
>
> Key: VYSPER-294
> URL: https://issues.apache.org/jira/browse/VYSPER-294
> Project: VYSPER
> Issue Type: Bug
> Components: core protocol
>Affects Versions: 0.8
> Environment: no special environment
>Reporter: Zhang JinYan
>Assignee: Ashish Paliwal
> Labels: patch
> Attachments: xmpp.patch
>
>
> 1、The EhCachePresenceCacheImpl has a constructor arg, which specify the
> configFile used to initialize a EhCache CacheManager,but didn't use it at
> last.
> Code:
> protected void createCache(String configFile) {
> if (configFile == null) {
> configFile = DEFAULT_EHCACHE_CONFIG_FILE;
> }
> URL configFileURL = getClass().getResource(configFile);
> if (configFileURL == null) {
> throw new RuntimeException("ehcache configuration file
> ehcache.xml not found on classpath");
> }
> CacheManager.create(); //<== Here i am!
> presenceCache = CacheManager.getInstance().getCache(PRESENCE_CACHE);
> jidPresenceCache =
> CacheManager.getInstance().getCache(JID_PRESENCE_CACHE);
> }
> 2、dist/src/main/assembly/src.xml
> Didn't excludes .* file/folde in sub directory. If i use eclipse to import
> those projects, there will create .* files (eclipse project files,eg:
> .classpath)
>
> **/target/**
> .*
> .*/** //<== Here i am!
> **.bak
>
> I upload my patch.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (VYSPER-294) EhCachePresenceCacheImpl initialize CacheManager not use the configFile passed in
[
https://issues.apache.org/jira/browse/VYSPER-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13108352#comment-13108352
]
Ashish Paliwal commented on VYSPER-294:
---
Looking into it.
> EhCachePresenceCacheImpl initialize CacheManager not use the configFile
> passed in
> -
>
> Key: VYSPER-294
> URL: https://issues.apache.org/jira/browse/VYSPER-294
> Project: VYSPER
> Issue Type: Bug
> Components: core protocol
>Affects Versions: 0.8
> Environment: no special environment
>Reporter: Zhang JinYan
>Assignee: Ashish Paliwal
> Labels: patch
> Attachments: xmpp.patch
>
>
> 1、The EhCachePresenceCacheImpl has a constructor arg, which specify the
> configFile used to initialize a EhCache CacheManager,but didn't use it at
> last.
> Code:
> protected void createCache(String configFile) {
> if (configFile == null) {
> configFile = DEFAULT_EHCACHE_CONFIG_FILE;
> }
> URL configFileURL = getClass().getResource(configFile);
> if (configFileURL == null) {
> throw new RuntimeException("ehcache configuration file
> ehcache.xml not found on classpath");
> }
> CacheManager.create(); //<== Here i am!
> presenceCache = CacheManager.getInstance().getCache(PRESENCE_CACHE);
> jidPresenceCache =
> CacheManager.getInstance().getCache(JID_PRESENCE_CACHE);
> }
> 2、dist/src/main/assembly/src.xml
> Didn't excludes .* file/folde in sub directory. If i use eclipse to import
> those projects, there will create .* files (eclipse project files,eg:
> .classpath)
>
> **/target/**
> .*
> .*/** //<== Here i am!
> **.bak
>
> I upload my patch.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRMINA-906) Chapter 2 of user-guide appears to be missing some code in example
[ https://issues.apache.org/jira/browse/DIRMINA-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449481#comment-13449481 ] Ashish Paliwal commented on DIRMINA-906: IMHO, the statement implies the logical sequence to be followed, and that's what it does (not necessarily the next code snipper). We configure the handler class and thereafter at the end bind to the port. > Chapter 2 of user-guide appears to be missing some code in example > -- > > Key: DIRMINA-906 > URL: https://issues.apache.org/jira/browse/DIRMINA-906 > Project: MINA > Issue Type: Bug > Components: Web Site / Documentation >Reporter: Gus Heck > > On http://mina.apache.org/sample-tcp-server.html the text: > "With the NioSocketAcceptor class in place, we can go ahead and define the > handler class and bind the NioSocketAcceptor to a port." > is not followed by a matching code example. Subsequent example code lacks the > code for defining the socket port. In particular near the end of the page > there is text that says: > "As you see, there is a call to acceptor.setLocalAddress( new > InetSocketAddress(PORT) );. This method defines what host and port this > server will listen on. " > However, the example code immediately prior does not contain that code. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRMINA-92) Utility classes for asynchronous request-response protocols.
[ https://issues.apache.org/jira/browse/DIRMINA-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13532285#comment-13532285 ] Ashish Paliwal commented on DIRMINA-92: --- Based on our ML List discussion (http://mina.markmail.org/thread/rodcslkrhgjcpikn), we are to deleting reqres filter. Do we plan to do this? We can close https://issues.apache.org/jira/browse/DIRMINA-593 along with this as well > Utility classes for asynchronous request-response protocols. > > > Key: DIRMINA-92 > URL: https://issues.apache.org/jira/browse/DIRMINA-92 > Project: MINA > Issue Type: New Feature >Affects Versions: 0.7.0 >Reporter: Trustin Lee >Assignee: Trustin Lee > Fix For: 2.0.0-M1 > > Attachments: Protocol.zip, queryreply.zip, requestResponse.zip > > > There are so many existing asynchronous protocols whose messages have > request-response structure. A request message usually has a message ID, and > the corresponding response message, which makes a pair, contains the message > ID in the request message. > It would be great if we can provide a common interface and classes to help > users implement this type of protocols easily. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (DIRMINA-654) Google Protocol Buffers Codec
[ https://issues.apache.org/jira/browse/DIRMINA-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal reassigned DIRMINA-654: -- Assignee: Ashish Paliwal > Google Protocol Buffers Codec > - > > Key: DIRMINA-654 > URL: https://issues.apache.org/jira/browse/DIRMINA-654 > Project: MINA > Issue Type: New Feature > Components: Filter >Reporter: Tomasz Blachowicz >Assignee: Ashish Paliwal > Fix For: 2.0.8 > > Attachments: protobuf.txt > > > Google Protocol Buffers (protobuf) are language-neutral, platform-neutral, > extensible mechanism for serializing structured data. Apache MINA already > provides several protocol codecs (decoders and encodes) that allows to deal > with different wire formats. The Protocol Buffer is the perfect candidate for > new codec available as separate and optional module within Apache MINA. > More details on Protocol Buffers can be found on the website: > http://code.google.com/apis/protocolbuffers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (DIRMINA-593) Javadoc & documentation for org/apache/mina/filter/reqres
[ https://issues.apache.org/jira/browse/DIRMINA-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal closed DIRMINA-593. -- Filter removed and issue closed > Javadoc & documentation for org/apache/mina/filter/reqres > - > > Key: DIRMINA-593 > URL: https://issues.apache.org/jira/browse/DIRMINA-593 > Project: MINA > Issue Type: Improvement > Components: Filter, Web Site / Documentation >Affects Versions: 2.0.0-M1 >Reporter: Julien Vermillard >Assignee: Ashish Paliwal > Fix For: 2.0.8 > > > no javadoc nor doc on the request/response filter, it need some examples too -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DIRMINA-593) Javadoc & documentation for org/apache/mina/filter/reqres
[ https://issues.apache.org/jira/browse/DIRMINA-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal resolved DIRMINA-593. Resolution: Won't Fix Removed the filter as per discussion on ML (http://mina.markmail.org/thread/rodcslkrhgjcpikn) > Javadoc & documentation for org/apache/mina/filter/reqres > - > > Key: DIRMINA-593 > URL: https://issues.apache.org/jira/browse/DIRMINA-593 > Project: MINA > Issue Type: Improvement > Components: Filter, Web Site / Documentation >Affects Versions: 2.0.0-M1 >Reporter: Julien Vermillard >Assignee: Ashish Paliwal > Fix For: 2.0.8 > > > no javadoc nor doc on the request/response filter, it need some examples too -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DIRMINA-654) Google Protocol Buffers Codec
[ https://issues.apache.org/jira/browse/DIRMINA-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal resolved DIRMINA-654. Resolution: Fixed Fix Version/s: (was: 2.0.8) 3.0.0-M1 Protobug codec is available in 3.0 trunk now. It has not been back ported to 2.0.x release. > Google Protocol Buffers Codec > - > > Key: DIRMINA-654 > URL: https://issues.apache.org/jira/browse/DIRMINA-654 > Project: MINA > Issue Type: New Feature > Components: Filter >Reporter: Tomasz Blachowicz >Assignee: Ashish Paliwal > Fix For: 3.0.0-M1 > > Attachments: protobuf.txt > > > Google Protocol Buffers (protobuf) are language-neutral, platform-neutral, > extensible mechanism for serializing structured data. Apache MINA already > provides several protocol codecs (decoders and encodes) that allows to deal > with different wire formats. The Protocol Buffer is the perfect candidate for > new codec available as separate and optional module within Apache MINA. > More details on Protocol Buffers can be found on the website: > http://code.google.com/apis/protocolbuffers -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DIRMINA-951) Add Getting started Page for MINA 3.0
[ https://issues.apache.org/jira/browse/DIRMINA-951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal updated DIRMINA-951: --- Summary: Add Getting started Page for MINA 3.0 (was: Add Getting started for MINA 3.0) > Add Getting started Page for MINA 3.0 > - > > Key: DIRMINA-951 > URL: https://issues.apache.org/jira/browse/DIRMINA-951 > Project: MINA > Issue Type: Task > Components: Web Site / Documentation >Affects Versions: 3.0.0-M1 >Reporter: Ashish Paliwal >Assignee: Ashish Paliwal >Priority: Minor > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (DIRMINA-951) Add Getting started for MINA 3.0
Ashish Paliwal created DIRMINA-951: -- Summary: Add Getting started for MINA 3.0 Key: DIRMINA-951 URL: https://issues.apache.org/jira/browse/DIRMINA-951 Project: MINA Issue Type: Task Components: Web Site / Documentation Affects Versions: 3.0.0-M1 Reporter: Ashish Paliwal Assignee: Ashish Paliwal Priority: Minor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (DIRMINA-953) Add examples for Protobuf and Thrift
Ashish Paliwal created DIRMINA-953: -- Summary: Add examples for Protobuf and Thrift Key: DIRMINA-953 URL: https://issues.apache.org/jira/browse/DIRMINA-953 Project: MINA Issue Type: Improvement Components: Example Affects Versions: 3.0.0-M1 Reporter: Ashish Paliwal Add examples for usage of Protobuf and Thrift in example package. This would help users easily integrate these codecs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRMINA-855) http client codec filter
[ https://issues.apache.org/jira/browse/DIRMINA-855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719627#comment-13719627 ] Ashish Paliwal commented on DIRMINA-855: Does our http module covers this requirement? > http client codec filter > > > Key: DIRMINA-855 > URL: https://issues.apache.org/jira/browse/DIRMINA-855 > Project: MINA > Issue Type: Sub-task >Affects Versions: 3.0.0-trunk >Reporter: Julien Vermillard > Fix For: 3.0.0-M1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (DIRMINA-954) Add Avro codec support
Ashish Paliwal created DIRMINA-954: -- Summary: Add Avro codec support Key: DIRMINA-954 URL: https://issues.apache.org/jira/browse/DIRMINA-954 Project: MINA Issue Type: New Feature Affects Versions: 3.0.0-trunk Reporter: Ashish Paliwal Assignee: Ashish Paliwal Add support for Avro codecs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (DIRMINA-955) Add Monitoring support to MINA
Ashish Paliwal created DIRMINA-955: -- Summary: Add Monitoring support to MINA Key: DIRMINA-955 URL: https://issues.apache.org/jira/browse/DIRMINA-955 Project: MINA Issue Type: New Feature Components: Core Affects Versions: 3.0.0-trunk Reporter: Ashish Paliwal Assignee: Ashish Paliwal Add monitoring support MINA for monitoring bytes in/out Queue lengths Protocol Messages in/out # IO Listener Events Connect/Idle etc JVM stuff (http://metrics.codahale.com/manual/jvm/) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DIRMINA-956) Status code match bug in AbstractHttpLogicHandler
[
https://issues.apache.org/jira/browse/DIRMINA-956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Paliwal updated DIRMINA-956:
---
Affects Version/s: 2.0.7
> Status code match bug in AbstractHttpLogicHandler
> --
>
> Key: DIRMINA-956
> URL: https://issues.apache.org/jira/browse/DIRMINA-956
> Project: MINA
> Issue Type: Bug
>Affects Versions: 2.0.7
>Reporter: Kim
>
> I found following code in AbstractHttpLogicHandler:
> protected HttpProxyResponse decodeResponse(final String response) throws
> Exception {
> ...
> // Status code is 3 digits
> if (statusLine[1].matches("^\\d\\d\\d")) {
> throw new Exception("Invalid response code (" + statusLine[1] +
> "). Response: " + response);
> }
> ...
> }
> Is there "statusLine[1].matches("^\\d\\d\\d")" should be
> "!statusLine[1].matches("^\\d\\d\\d")"?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (DIRMINA-954) Add Avro codec support
[ https://issues.apache.org/jira/browse/DIRMINA-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on DIRMINA-954 started by Ashish Paliwal. > Add Avro codec support > -- > > Key: DIRMINA-954 > URL: https://issues.apache.org/jira/browse/DIRMINA-954 > Project: MINA > Issue Type: New Feature >Affects Versions: 3.0.0-trunk >Reporter: Ashish Paliwal >Assignee: Ashish Paliwal > > Add support for Avro codecs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRMINA-954) Add Avro codec support
[ https://issues.apache.org/jira/browse/DIRMINA-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13721770#comment-13721770 ] Ashish Paliwal commented on DIRMINA-954: Initial draft added, would need refinement and more test cases plus docs > Add Avro codec support > -- > > Key: DIRMINA-954 > URL: https://issues.apache.org/jira/browse/DIRMINA-954 > Project: MINA > Issue Type: New Feature >Affects Versions: 3.0.0-trunk >Reporter: Ashish Paliwal >Assignee: Ashish Paliwal > > Add support for Avro codecs -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (DIRMINA-959) Add SVN Doc path to Source
Ashish Paliwal created DIRMINA-959: -- Summary: Add SVN Doc path to Source Key: DIRMINA-959 URL: https://issues.apache.org/jira/browse/DIRMINA-959 Project: MINA Issue Type: Improvement Components: Web Site / Documentation Reporter: Ashish Paliwal Currently we don't have link to SVN root for documents that get published. Need to add it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (DIRMINA-959) Add SVN Doc path to Source
[ https://issues.apache.org/jira/browse/DIRMINA-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal reassigned DIRMINA-959: -- Assignee: Ashish Paliwal > Add SVN Doc path to Source > -- > > Key: DIRMINA-959 > URL: https://issues.apache.org/jira/browse/DIRMINA-959 > Project: MINA > Issue Type: Improvement > Components: Web Site / Documentation >Reporter: Ashish Paliwal >Assignee: Ashish Paliwal > > Currently we don't have link to SVN root for documents that get published. > Need to add it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DIRMINA-959) Add SVN Doc path to Source
[ https://issues.apache.org/jira/browse/DIRMINA-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal resolved DIRMINA-959. Resolution: Fixed Fix Version/s: 3.0.0-trunk Updated site docs to display documentation source location for MINA, SSHD, Vysper and FtpServer > Add SVN Doc path to Source > -- > > Key: DIRMINA-959 > URL: https://issues.apache.org/jira/browse/DIRMINA-959 > Project: MINA > Issue Type: Improvement > Components: Web Site / Documentation >Reporter: Ashish Paliwal >Assignee: Ashish Paliwal > Fix For: 3.0.0-trunk > > > Currently we don't have link to SVN root for documents that get published. > Need to add it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (DIRMINA-960) Create a Verifying a Release page
Ashish Paliwal created DIRMINA-960: -- Summary: Create a Verifying a Release page Key: DIRMINA-960 URL: https://issues.apache.org/jira/browse/DIRMINA-960 Project: MINA Issue Type: Improvement Components: Web Site / Documentation Affects Versions: 3.0.0-M1 Reporter: Ashish Paliwal Assignee: Ashish Paliwal Create a page describing steps on how to verify a release. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (SSHD-250) Fix random test failures
Ashish Paliwal created SSHD-250: --- Summary: Fix random test failures Key: SSHD-250 URL: https://issues.apache.org/jira/browse/SSHD-250 Project: MINA SSHD Issue Type: Bug Affects Versions: 0.9.0 Reporter: Ashish Paliwal Fix random test failure which are due to timing issue in test like in ScpTest. They failed during Release verification -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (SSHD-251) Fix random test failures
Ashish Paliwal created SSHD-251: --- Summary: Fix random test failures Key: SSHD-251 URL: https://issues.apache.org/jira/browse/SSHD-251 Project: MINA SSHD Issue Type: Bug Affects Versions: 0.9.0 Reporter: Ashish Paliwal Fix random test failure which are due to timing issue in test like in ScpTest. They failed during Release verification -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SSHD-251) Fix random test failures
[ https://issues.apache.org/jira/browse/SSHD-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Paliwal resolved SSHD-251. - Resolution: Duplicate Damn browser created two issues > Fix random test failures > > > Key: SSHD-251 > URL: https://issues.apache.org/jira/browse/SSHD-251 > Project: MINA SSHD > Issue Type: Bug >Affects Versions: 0.9.0 >Reporter: Ashish Paliwal > > Fix random test failure which are due to timing issue in test like in > ScpTest. They failed during Release verification -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRMINA-258) Example of an XML server and Client.
[ https://issues.apache.org/jira/browse/DIRMINA-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124464#comment-14124464 ] Ashish Paliwal commented on DIRMINA-258: True, let me find some time to explore Aalto XML parser and fit into our example. > Example of an XML server and Client. > > > Key: DIRMINA-258 > URL: https://issues.apache.org/jira/browse/DIRMINA-258 > Project: MINA > Issue Type: New Feature > Components: Example >Reporter: Martin Helmhout >Assignee: Ashish Paliwal >Priority: Minor > Fix For: 3.0.0-M3 > > Attachments: ASF.LICENSE.NOT.GRANTED--MINA_XMLServer.zip, > MINA_XMLServer.zip, XMLserver095.zip > > > The attachment contains an example of an XML Server + client and should help > start people building their server quickly. > Because an XML server was not in the examples, I created quickly something > for myself, but want others to also get the fruits and make them better if > possible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DIRMINA-985) Fix the various Javadoc issues
[
https://issues.apache.org/jira/browse/DIRMINA-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133843#comment-14133843
]
Ashish Paliwal commented on DIRMINA-985:
Intellij javadoc inspection is pointing few more error's like the one for using
@inheritedDoc - "This inspection reports any Javadoc comments which contain
only the {@inheritDoc} tag. Since Javadoc copies the super class' comment if no
comment is present, a comment containing only an {@inheritDoc} adds nothing."
or we just fix what maven is reporting?
> Fix the various Javadoc issues
> --
>
> Key: DIRMINA-985
> URL: https://issues.apache.org/jira/browse/DIRMINA-985
> Project: MINA
> Issue Type: Improvement
>Reporter: Emmanuel Lecharny
> Fix For: 2.0.9
>
> Attachments: mina-javadoc.txt
>
>
> We have numerous javadoc warnings that need to be fixed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
