[JBoss Portal Users] - Javascript compatability
by hamptont
I have a portlet that uses Mootools JavaScript framework and it is not working because it is conflicting with the Prototype framework that the portal uses internally. It seems that both Prototype and Mootools are poorly written with respect to compatibility with other libraries.
| 1) Is there anyway to make Mootools work with JBoss Portal ?
|
| 2) Is there a JavaScript compatibility list for JBoss Portal ? There is a lot of JavaScript included in the portal and it's looking like a mountain of work to figure out what is actually compatible.
|
| 3) Is there a way to turn off the JavaScript features of the portal so that my conflict goes away ?
|
| 4) Any other options I've not listed ?
|
|
|
| Thanks.
|
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256749#4256749
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256749
16 years, 7 months
[EJB 3.0 Users] - EJB Entity Bean works in default configuration, failes using
by gldnrtvr
I am trying to figure out if I have found a bug, or if I need to modify my code.
I have a number of EJB3 entity beans that work just fine with -b=0.0.0.0; however, I have to run my services on a separate IP address ( using -b 10.10.10.21 ). I am also using -Djboss.service.binding.set=ports-01 (very complicated political reason why I have to do this)
JBoss starts without error when I run this configuration with none of my EJB3 beans deployed; however when I deploy even the simplest one, I get errors that indicate that my bean is ignoring the -b and binding.set:
javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost/127.0.0.1:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]]
I searched my code and property files, but could find neither 127.0.0.1 nor localhost referenced anywhere. Is there a configuration option that I need to configure the context lookup to use 10.10.10.21:1199 for JNI?
Thank you in advance,
-Mark Henning
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256734#4256734
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256734
16 years, 7 months
[JBoss Cache Users] - Re: how to lock a node for update?
by alllle
"manik.surtani(a)jboss.com" wrote : You can force write locks for a read. There is an Option for this (see the Options API). When used with MVCC, this gives you an exclusive (write) lock, when when you are reading. And when combined with a transaction, this means you hold the write lock until the tx completes.
Thanks for the help.
I assume you are referring to some thing like this (from the doc):
| // first start a transaction
| cache.getInvocationContext().getOptionOverrides().setForceWriteLock(true);
| Node n = cache.getNode(Fqn.fromString("/a/b/c"));
| // make changes to the node
| // commit transaction
|
I wonder if you can explain it in a little more detail. I need some clarification to my confusions:
- when is the lock obtained? is it, like the write lock, at the time when the transaction commits or it is at the time when the read happens?
- What is considered as a "read"? I mean, does cache.getNode() considered a "read", or only when I do a subsequent node.get("key") is when the lock obtained?
- With "REPEATABLE_READ" isolation, is the "write skew" still a problem? - I think it's not but I'd like to get a confirmation from you.
- What is the scope of the current "InvocationContext"? Is it within the current transaction, or current thread, or something else?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256728#4256728
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4256728
16 years, 7 months