[JBoss Messaging] - Re: Bridge error because of network problems also influences
by mclu
Hi Howard!
No sorry... not easy to explain :-)
All 6 Bridges are deployed on X
X is our so called root server which do the message processing and delegates the messages to the other nodes.
A, B and C are our nodes/instances which only uses local queues. Each node has an incoming and an outgoing queue.
X has 3 JMSProviderLoader configured. One for each node.
The
example:
| <mbean code="org.jboss.jms.jndi.JMSProviderLoader" name="jboss.messaging:service=JMSProviderLoaderRemote,name=RemoteJMSProvider_AeosA">
| <attribute name="ProviderName">RemoteJMSProvider_AeosA</attribute>
| <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
| <!-- The combined connection factory -->
| <attribute name="FactoryRef">/XAConnectionFactory</attribute>
| <!-- The queue connection factory -->
| <attribute name="QueueFactoryRef">/XAConnectionFactory</attribute>
| <!-- The topic factory -->
| <attribute name="TopicFactoryRef">/XAConnectionFactory</attribute>
| <attribute name="Properties">
| java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| java.naming.factory.url.pkgs=org.jnp.interfaces
| java.naming.provider.url=localhost:2099
| </attribute>
| </mbean>
|
Because there are 3 Nodes I have 3 Bridges for the incoming queue and 3 Bridges for the outgoing queue on instance X.
On X there are also only 2 queues. The incoming bridges are sending all messages from "ABC incoming" to "X incoming".
The Outgoing bridges uses selectors to only fetch the node (ABC) related messages out of the outgoing queue of X.
In production we only have remote nodes. Currently 8 nodes and one root server X.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215311#4215311
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215311
15 years, 10 months
[JBoss Portal] - Re: Portal Themes and Richfaces
by wesleyhales
This would be cool if you could create it and submit it back to the portlet bridge project. I could add it as a bridgelet.
Here is what you need to do to match the current portal theme:
1. Create a file called renewal.skin.properties (if this is the theme you are trying to match, if not, name it something else besides "renewal") and place it in your RichFaces applications WEB-INF/lib.
2. Here is a sample properties file I had laying around:
#Colors
headerBackgroundColor=#FFD863
headerGradientColor=#FF9B19
headerTextColor=#000000
headerWeightFont=bold
generalBackgroundColor=#FFFFFF
generalTextColor=#000000
generalSizeFont=12px
generalFamilyFont=Tahoma, Verdana, sans-serif
controlTextColor=#000000
controlBackgroundColor=#ffffff
additionalBackgroundColor=#FFFFFF
shadowBackgroundColor=#000000
shadowOpacity=1
panelBorderColor=#C0C0C0
subBorderColor=#ffffff
tabBackgroundColor=#dcdcdc
tabDisabledTextColor=#dcdcdc
trimColor=#dcdcdc
tipBackgroundColor=#dcdcdc
tipBorderColor=#dcdcdc
selectControlColor=#dcdcdc
generalLinkColor=#0078D0
hoverLinkColor=#0090FF
visitedLinkColor=#0090FF
# Fonts
headerSizeFont=12px
headerFamilyFont=Tahoma, Verdana, sans-serif
tabSizeFont=12
tabFamilyFont=Tahoma, Verdana, sans-serif
buttonSizeFont=12
buttonFamilyFont=Tahoma, Verdana, sans-serif
tableBackgroundColor=#FFFFFF
tableFooterBackgroundColor=#cccccc
tableSubfooterBackgroundColor=#f1f1f1
tableBorderColor=#C0C0C0
3. Next just change the colors to match the renewal theme. And place this in your web.xml:
<context-param>
<param-name>org.richfaces.SKIN</param-name>
<param-value>renewal</param-value>
</context-param>
4. Read more about it here and post on the forum when you are done.
http://www.jboss.org/file-access/default/members/jbossrichfaces/freezone/...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215307#4215307
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215307
15 years, 10 months