[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Why ServerSessionImpl::doHandleCreateQueue is not callin
by clebert.suconic@jboss.com
Ok.. I see on inconsistence then between two different methods for creating Queues. On JMSServerManagerImpl.createQueue and ServerSessionImpl.doHandleCreateQueue.
JMSServerManagerImpl is creating a destination when Queues are created:
public boolean createQueue(final String queueName, final String jndiBinding) throws Exception
| {
| JBossQueue jBossQueue = new JBossQueue(queueName);
| postOffice.addDestination(jBossQueue.getSimpleAddress(), true);
| messagingServer.createQueue(jBossQueue.getAddress(), jBossQueue.getAddress());
|
While ServerSessionImpl::doHandleCreateQueue is only creating the binding.
|
| public void doHandleCreateQueue(final SessionCreateQueueMessage packet)
| {
| SimpleString address = packet.getAddress();
|
| SimpleString queueName = packet.getQueueName();
|
| SimpleString filterString = packet.getFilterString();
|
| boolean temporary = packet.isTemporary();
|
| boolean durable = packet.isDurable();
|
| boolean fanout = packet.isFanout();
|
| Packet response = null;
|
| try
| {
| // make sure the user has privileges to create this queue
| if (!postOffice.containsDestination(address))
| {
| securityStore.check(address, CheckType.CREATE, this);
| }
|
| Binding binding = postOffice.getBinding(queueName);
|
| if (binding != null)
| {
| throw new MessagingException(MessagingException.QUEUE_EXISTS);
| }
|
| Filter filter = null;
|
| if (filterString != null)
| {
| filter = new FilterImpl(filterString);
| }
|
| binding = postOffice.addBinding(address, queueName, filter, durable, temporary, fanout);
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189441#4189441
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189441
17 years, 4 months
[Design of JBoss ESB] - JBoss ESB 4.5 GA release schedule
by Kevin.Conner@jboss.com
The team are starting to look at the next project release of the ESB 4.x stream and will shortly begin development in earnest.
The proposed schedule is as follows
Requirements and new functionality
now - 28th November
Discuss requirements and select development tasks that are to be included in the next project release. This will primarily focus on feature requests and improvements to current capabilities.
Development
1st December - 30th January
Main development tasks will progress, except for holiday period and f2f meeting. During this phase we will accept additional bug fix requests but most feature requests will be postponed to the next release.
Testing
February 2nd - February 13th
Testing of the codebase with critical bug fixes being accepted.
Release
February 13th.
If you have any suggestions for new functionality, or enhancements to the current codebase, then please let us know about them by creating a JIRA request and setting the 'fix version' to '4.5 feature requests'.
Thanks,
ESB team
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4189363#4189363
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4189363
17 years, 4 months