On Tue, Apr 2, 2013 at 11:20 PM, Hasitha Hiranya <[email protected]> wrote:
> Hi, > > It is nice to have feed-backs. > > 1. As Ishara says, "tryit" feature will be available with "MB 2.1.0" > release. > 2. Message deletion will be nice to have. But JMS spec does not mention > about deleting messages. When you get messages from queue with "AUTO ACK" > mode messages will be auto deleted. BTW, Websphere MQ support that feature > (selective delete) by their implementation. We will consider on adding that > feature for MB 3.0.0. > +1 ActiveMQ also support message deletion through it's web console. Thanks ! > > Thanks. > > > > > On Tue, Apr 2, 2013 at 10:55 PM, Sagara Gunathunga <[email protected]>wrote: > >> >> >> >> On Tue, Apr 2, 2013 at 10:53 PM, Ishara Premadasa <[email protected]>wrote: >> >>> Hi Sagara, >>> >>> >>> >>> >>> On Tue, Apr 2, 2013 at 10:43 PM, Sagara Gunathunga <[email protected]>wrote: >>> >>>> >>>> Hi Ishara/Shammi, >>>> >>>> This is really cool addition ! As a MB user I also have list of feature >>>> requests for web console :) >>>> >>>> 1.) Practically I have felt many time if we could have web based sender >>>> ( or Try-It) feature with MB. This means there should be web interface to >>>> send messages to a destination without creating any JMS client, it just a >>>> filling a HTML page with required data. ActiveMQ provide such a web >>>> interface[1] and very useful too. As an example take a look at this post[2] >>>> how I used ActiveMQ console to test Axis2 JMS transport without writing any >>>> client side code. In my POV we need to have similar but better Try-It or >>>> sender feature for MB. >>>> >>> >>> >>> Thank you very much for these suggestions. Actually our next task is >>> adding a 'Test Message Sending' feature for MB admin console[1]. As exactly >>> you had mentioned, we hope to provide the ability to send a sample JMS >>> message with setting the necessary parameters like in ActiveMQ. Hope to >>> start this soon ASAP once we finalize the queue browser. >>> >> >> Great ! Nice to hear that. >> >> >>> >>>> 2.) I believe we can provide following details per topic, WDYT ? >>>> >>>> Name >>>> Number Of Consumers >>>> Messages Enqueued >>>> Messages Dequeued >>>> >>>> 3.) It's better to have some XML indention on "message content" view. >>>> >>> >>> >>> Yes, the current message content view doesn't show the XML indentions >>> properly when a user sends XML as content. I will try to fix this and get >>> the proper indentation view. >>> >>> Thanks! >>> >>> >>> [1] https://wso2.org/jira/browse/MB-139 >>> >>> >>> >>> >>>> [1] - >>>> http://1.bp.blogspot.com/-dEQzkDJKOiE/T5LBe5xgneI/AAAAAAAAAJ4/qX1nr58yWJk/s1600/1.png >>>> [2] - >>>> http://ssagara.blogspot.com/2012/04/axis2-jms-transport-and-activemq.html >>>> >>>> >>>> Thanks ! >>>> >>>> >>>> >>>> On Tue, Apr 2, 2013 at 3:31 PM, Ishara Premadasa <[email protected]>wrote: >>>> >>>>> Hi, >>>>> >>>>> This is an update on Feature#1207 [1], adding queue browsing ability >>>>> into MB. The following is the final outcome of the feature implementation >>>>> and this will be released with the upcoming MB 2.1.0 release. >>>>> >>>>> With queue browsing the user is capable of viewing the JMS Messages' >>>>> details inside particular queue, including message attributes, properties, >>>>> content type etc. and in addition the complete message body content can be >>>>> viewed for each message as shown in the screen shots attached below. >>>>> >>>>> Due to the performance concerns there will be a maximum message limit >>>>> of 200, that is displayed in the queue browser UI, even though the given >>>>> queue may have a larger amount of messages. At the moment this can be >>>>> configured in the qpid_config.xml if necessary (explained in the >>>>> documentation). >>>>> >>>>> However I would like to know that whether we should allow this is to >>>>> be configured into a higher amount as there is a possibility of crashing, >>>>> when loading a big amount of messages into memory. >>>>> >>>>> The MB 2.1.0 documentation is updated too [2]. >>>>> >>>>> Thanks! >>>>> Ishara >>>>> >>>>> [1] https://redmine.wso2.com/issues/1207 >>>>> [2] http://docs.wso2.org/wiki/display/MB210/Managing+Queues >>>>> >>>>> >>>>> -- >>>>> Ishara Premasada >>>>> Software Engineer, >>>>> Integration Technology Team, >>>>> WSO2 Inc. http://wso2.com/ >>>>> *Linked in : >>>>> http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 >>>>> Twitter : https://twitter.com/ishadil >>>>> Mobile : +94 714445832* >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Sagara Gunathunga >>>> >>>> Technical Lead; WSO2, Inc.; http://wso2.com >>>> V.P Apache Web Services; http://ws.apache.org/ >>>> Blog ; http://ssagara.blogspot.com >>>> Linkedin; http://www.linkedin.com/in/ssagara >>>> >>> >>> >>> >>> -- >>> Ishara Premasada >>> Software Engineer, >>> Integration Technology Team, >>> WSO2 Inc. http://wso2.com/ >>> *Linked in : http://www.linkedin.com/pub/ishara-premadasa/1a/630/609 >>> Twitter : https://twitter.com/ishadil >>> Mobile : +94 714445832* >>> >>> >>> >> >> >> -- >> Sagara Gunathunga >> >> Technical Lead; WSO2, Inc.; http://wso2.com >> V.P Apache Web Services; http://ws.apache.org/ >> Blog ; http://ssagara.blogspot.com >> Linkedin; http://www.linkedin.com/in/ssagara >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Hasitha Abeykoon* > Software Engineer; WSO2, Inc.; http://wso2.com > *cell:* *+94 719363063* > *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>* * > * > * > -- Sagara Gunathunga Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services; http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
