March 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss ESB] - Re: Advanced MessageStore implementation

by mark.little＠jboss.com

BTW, I believe current implementations are JDBC and Hibernate. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031413#4031413 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031413

17 years, 3 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Advanced MessageStore implementation

by mark.little＠jboss.com

Daniel was driving this, but if JMS has one then we should be able to plug that in as one of the possible backend implementations. As long as it can cope with arbitrary data. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031412#4031412 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031412

17 years, 3 months

1
0
0 / 0

[Design of Kosmos] - Re: SVN portlet timeout error

by aron.gombas

You should increase the timeout period more. Plz note that even if the request transaction is cancelled by the appserver, it just kills only the HTTP request-response cycle. The background thread that collects the info will not stop, so as soon as it completes the job, you can just do a "Reload' in your browser and voila! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031411#4031411 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031411

17 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: vfs issue?

by scott.stark＠jboss.org

You would have to use the org.jboss.vfs.VFS/VirtualFile aps. You can't just use the java.net.URL and handler apis because they don't have support for directory structures. A deployer (which is a very isolated/minimal entity in jboss5) may be the better choice to avoid needing to link core seam code to the vfs, although its a standalone piece that has no dependencies on other mc code. It does depend on the jboss common/logging jars. I'd have to know more about what the scan is trying to accomplish and how this relates to jbossas vs another app server to say which is better. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031410#4031410 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031410

17 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: vfs issue?

by gavin.king＠jboss.com

So is there a "quick fix", Scott, or do we need do write a whole Seam deployer? What is the safe way to scan archives in an EAR in JBoss 5? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031407#4031407 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031407

17 years, 3 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Advanced MessageStore implementation

by bill.burke＠jboss.com

What advantage does implementing a message store for ESB have over just using our JMS implementation? Why is esb implementing what JMS already has? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031399#4031399 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031399

17 years, 3 months

1
0
0 / 0

[Design of JBossCache] - InvocationContext in JBCMethodCall?

by bstansberry＠jboss.com

Minor food for thought... While responding to a user forum question (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=104915) it occurred to me that other interceptor-based architectures I see include call-context metadata as an internal field of the Invocation object that gets passed through the interceptor chain on the stack. In JBC we are separating it out into the InvocationContext ThreadLocal. Since JBC is now using its own MethodCall subclass, including the InvocationContext metadata in the invocation object itself is possible. There are downsides to this, and it might break things I haven't thought of. If we ever move away from using JBCMethodCall as our "Invocation" class (part of reducing coupling to JGroups) we should be sure to think about merging the InvocationContext back in. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031390#4031390 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031390

17 years, 3 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Advanced MessageStore implementation

by mark.little＠jboss.com

Let me explain further. The MessageStore interface is basic at the moment, so does need extending. One way to do this would be to standardise on JSR-170. Another would be to have our own interface that may look similar to JSR-170, but narrower in terms of what is required for backend implementations (after all, we're not trying to make the MessageStore a general content repository: it will only ever store Messages). The latter approach is what the group agreed back in June 2006. I haven't looked at JSR-170 in depth, but storage repositories with search and indexing facilities have existed for many years. We don't want to do anything that would preclude users plugging them into the MessageStore. Do you think that it would be easy for non-JSR-170 implementations to be plugged into a JSR-170 based API? Or are we right to stick with the current plan? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031383#4031383 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031383

17 years, 3 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Advanced MessageStore implementation

by mark.little＠jboss.com

The aims you mention are certainly in line with the original intention of the MessageStore, though it's not there yet. If you want to look at extending that, perhaps with a JSR-170 backend implementation, that would be great. However, we don't want to expose backend implementation issues (such as JSR-170, or plain filesystem etc.) through the MessageStore interface. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031381#4031381 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031381

17 years, 3 months

1
0
0 / 0

[Design of JBoss ESB] - Advanced MessageStore implementation

by tpeuss

I am thinking about an advanced MessageStore implementation. From my point of view a MessageStore should have following features: Search for messages based on Header information Properties Message body Type Attachments (?) Performant on writing, searching, changing messages (documents) Flexible installation: file-based, DB-based, ... I good basis for a MessageStore can be a JSR-170 content repository like Apache Jackrabbit or Exo Platform. It has already all features for storing, searching and changing structured information like XML. We can support changing of messages in a traceable way because this repositories allow us to do versioning as well. What do you think? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031378#4031378 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031378

17 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums March 2007