[Design of JBossCache] - Re: JBCACHE-941 discussion
by manik.surtani@jboss.com
anonymous wrote :
|
| Manik suggests also an adaptor for JCache (JSR-107).
|
|
Just that JCACHE uses a Map interface rather than a tree structured one.
In general, I think this is a good idea as there are many use cases (Hibernate, among others) where a tree structure is too complex and unnecessary from an API perspective (but necessary from a performance/efficiency perspective).
E.g., Coherence offers a Map interface, but internally key/value pairs are broken up into buckets for finer grained concurrency and replication.
anonymous wrote :
| Actually, it might also be nifty if JBoss Cache could supply adaptors for competing Cache APIs. I'm not sure of the legality of this for commercially published interfaces.
|
Hmm, this would mean shipping with those interfaces though. Perhaps these could be additional downloads? Like you said, we'd need to research legality anyway.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004827#4004827
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004827
19 years, 2 months
[Design of JBoss Portal] - Re: LayouStrategy and StrategyResponse API
by julien@jboss.com
I have added in the actual trunk an attempt to match the explanations. It is done by coding an interceptor that goes on the command stack of the portal.
For now the code can be found in org.jboss.portal.core.WindowInterceptor, but it's likely that it will be removed (because it is not very useful for the actual portal). For now it is here as an attempt to show how to code that kind of stuff.
Later we will see if we can introduce an API that provides those semantics wrapping the internal of portals (but doing a good API is hard...). It could be part of the actual IPC API if we introduce a PageEvent but note sure of that.
To activate it you need to modify in jboss-portal.sar/META-INF/jboss-service.xml
Add in the section <!-- Command stack --> the mbean :
| <mbean
| code="org.jboss.portal.core.WindowInterceptor"
| name="portal:service=Interceptor,type=Command,name=Window"
| xmbean-dd=""
| xmbean-code="org.jboss.portal.jems.as.system.JBossServiceModelMBean">
| <xmbean/>
| </mbean>
|
and modify the portal:service=InterceptorStackFactory,type=Command mbean to add a dependency :
| <depends-list-element>portal:service=Interceptor,type=Command,name=Window</depends-list-element>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004821#4004821
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004821
19 years, 2 months
[Design of JBoss Web Services] - Re: JBWS-1464 - Adding MTOM support to WSDL To Java - Design
by heiko.braun@jboss.com
I would favour point (1). This is what i communicated to the users already. It's simple and fits the overall problem the best. There is many cases where
a) you dont know the exact mimetype
b) data is send inlined
c) you need to pass the content type along
DataHandler is the best chioce IMO.
Regarding Noel's considerations:
anonymous wrote :
| I see base64Binary data that should not be considered as attachment. It's a type that is often used for IDs. For exemple, you can have an operation with an ID as argument and an attachment as a result.
|
It's right what you are saying, but in the only (rare) case this becomes a problem is when users types contain base64 types that should be optimized and others that shouldnt at the same time. If this doesnt occur on the same payload then you easily turn off MTOM for that port.
On the otherhand, if you want to meet that rare case a treshold switch should be used to decide at runtime wether or not optimization should be done.
This is a good idea in many cases, because MTOM optimization does pay off only when data reaches several kb.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004817#4004817
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004817
19 years, 2 months
[Design of JCA on JBoss] - Re: JBAS-3997
by adrian@jboss.org
We only currently cover the case where a previous connection in the pool is invalid.
We don't cover the following cases:
* Somebody bounces the database server (or whatever the backend is)
making it unavailable for a few seconds, the pool will be drained of previous
connections (they are invalid) but then fail immediately to create a new one.
* The error is not raised by the pooling but by something in front of it
i.e. something in the connection manager causes the transient failure
e.g.
1) The original example is where the pool is flushed which causes a small
"window of opportunity" where a request is going through to the old subpool
that is being shutdown, rather than to the new subpool.
2) Other things in the connection manager like a transient failure in the
security login module that creates the subject
If you are really worried about only doing this for transient failures
we could create a subclass of ResourceException, e.g. TransientResourceException
and then have the places we think can be retried throw this exception,
* pool exhausted
* subpool shutdown
* etc.
We would then only do the retries for a TransientResourceException
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004801#4004801
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004801
19 years, 2 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Bug in transactional delivery in an MDB
by adrian@jboss.org
"ovidiu.feodorov(a)jboss.com" wrote :
| On one hand, the fixes for JBMESSAGING-410 and JBMESSAGING-520 insure that a JMS session created using a JMS connection produced by the JCA connection factory behaves as NON-TRANSACTED in absence of a global JTA transaction.
|
| This is an intuitive behavior, users rely on it, JBossMQ behaves similarly, and reportedly, other JMS providers as well.
|
There is actually nothing in the spec about this behaviour.
The XA stuff is massively underspecified in the JMS spec.
And of course it is optional whether a JMS impl supports XA.
The JBossMQ behaviour is to assume that an XASession behaves like
AUTO_ACKNOWLEDGE when the XASession is not enlisted in a JTA transaction.
(Some JMS implements throw an exception in this case).
There is one exception to this. When the XASession is being used as part of
a ServerSessionPool, the semantics need to be receive then enlist.
So for this, the XASession behaves like there is a transaction, it will be told
later what XID to use for the 2PC protocol.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4004783#4004783
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4004783
19 years, 2 months