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

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Patching app server versus scoping messaging

by mskonda

I am not sure whether I should butt in, but oops, I already did! Just want to let you know that we have ditched scoping logn ago by patching remoting AND aop libraries on the appserver. We have been successfully running our servers since then and we have not encountered any issues. I agree with Tim, it's quite a big headache scoping JBM. I vote for 'get rid of scoping - go for patching' :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037636#4037636 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037636

19 years, 1 month

1
0
0 / 0

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

by mark.little＠jboss.com

Derek, just checking: did you update the administrator's guide with these required configuration changes? I want to make sure all of the docs are up-to-date so the ESB deployment is self-contained. Don't want users to have to keep running back to the forum to check for things like this if possible. Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037634#4037634 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037634

19 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: NotifyFTP class for NotificationAction

by mark.little＠jboss.com

Thanks Derek. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037633#4037633 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037633

19 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: JSR-170 message store

by mark.little＠jboss.com

"derek.adams" wrote : "kurt.stam(a)jboss.com" wrote : I think we need one extra argument, a message store id/message classification. | | I think we want to use the message store for all sorts of purposes. One example would be the DLQ I was talking about, so we need to be able to have 'substore' in this store, where I can store messages for this purpose. Is this posiible? | | The JCR allows arbitrary metadata to be associated with each node. I was thinking we could just add a jbossesb:delivered boolean property to each message node. We could then do queries against that metadata to get the list of undelivered messages. The JCR spec allows the base repository schema to be extended with custom types, so we could have a well-defined layout for all of the info related to a message. I could see attributes like jbossesb:message-id, jbossesb:message-created-date, jbossesb:message-category, etc.. which would make reporting against messages really easy. The database message store impl would do the equivalent by adding columns in the message table. | Because we can never know all possible search (and save) criteria, we want an interface that doesn't need to be updated everytime something new comes along. Do you think we've got that now, or are there more changes to be made? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037631#4037631 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037631

19 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Patching app server versus scoping messaging

by timfox

As already mentioned in other threads, JBM needs to be deployed scoped in JBoss AS 4.x. This proves to be a big headache for many of our users and is providing a big barrier to adoption IMHO. A different approach would be to patch the AS during the JBM installation procedure. I.e. we could overwrite the JBoss Remoting and JBoss AOP jars in server/lib with the later ones that we know to work. This would prevent us having to scope messaging. I exchanged some emails with Bill offline about this, and this is apparently what EJB3 does for 4.0.3.SP1 (see http://docs.jboss.org/ejb3/app-server/tutorial/installing.html), so I guess there is nothing in principle wrong with this approach. For AS 4.2.1 and later we would make sure we align dependencies properly so no scoping or patching would be necessary. Comments? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037630#4037630 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037630

19 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Install Items

by alesj

Why should InstallItem be referenced by DependencyInfo? I need to register a 'callback / install' item directly into the controller - holding the information of requested class, cardinality, target context, target method/property. Since with Controller.resolveContexts() I never iterate over already installed context's. And even if I did, I should only iterate over those who actually hold any install item. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037546#4037546 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037546

19 years, 1 month

1
0
0 / 0

[Design of the JBoss EJB Container] - Re: jdbc2.StoreManager2 and key-generators

by alex.loubyansky＠jboss.com

Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037517#4037517 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037517

19 years, 1 month

1
0
0 / 0

[Design of the JBoss EJB Container] - Re: jdbc2.StoreManager2 and key-generators

by jesper.pedersen

Ok -- that is also the way we are looking at it currently. We will start to submit the patches tomorrow as 3 different issues: 1) QualifiedTableName in EntityBridge2 2) LIMIT/OFFSET functionality in AbstractQueryCommand 3) Key generators for StoreManager2 As they are unrelated (in some way). Thanks, Alex. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037508#4037508 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037508

19 years, 1 month

1
0
0 / 0

[Design of the JBoss EJB Container] - Re: jdbc2.StoreManager2 and key-generators

by alex.loubyansky＠jboss.com

"jesper.pedersen" wrote : Looking at the next at the next exception in our trace it seems that jdbc2.AbstractQueryCommand doesn't implement LIMIT/OFFSET functionality such the jdbc.JDBCAbstractQueryCommand does. Correct ? | | If so, how should jdbc2.AbstractQueryCommand implement this functionality ? | | The interface between the two classes are different, so the OFFSET/LIMIT information isn't directly available. | Probably, in a similar way. Seems like static fetchCollection is the place to offset and pass the limit to collectionStrategy.readResultSet(con, ps, rs, factory); View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037499#4037499 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037499

19 years, 1 month

1
0
0 / 0

[Design of the JBoss EJB Container] - Re: jdbc2.StoreManager2 and key-generators

by alex.loubyansky＠jboss.com

"jesper.pedersen" wrote : There is a bug in JDBCEntityBridge2::getQualifiedTableName(). | | The method should do the same as the JDBCEntityBridge::getQualifiedTableName() namely | | | SQLUtil.fixTableName(metadata.getDefaultTableName(), dataSource); | | | | Should the bug be fixed in the constructor (as local variable) or in the method ? | | I'm for the fix in the constructor. | Yes, in the ctor or init. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037498#4037498 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037498

19 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2007