[Design of JBoss Portal] - Problem with multiples wars
by eroscc
Hello
I have a problem with multiples wars.
My JboosPortal version is: 2.2.1RC3
My classes are shared, but my jboss-web.xml is:
| <class-loading java2ClassLoadingCompliance="false">
| <loader-repository>
| com.sumersoft:loader=demo
| <loader-repository-config>
| java2ParentDelegation=false
| </loader- repository-config>
| </loader-repository>
| </class-loading>
|
I see the problem when I try load one .properties that it is inside of war.
Each war it has a different file .properties, with equals name but with
different content.
In my class that load .properties this code is used:
| public class CommonInformationPortal implements ServletContextListener {
|
| private static Properties properties = null;
|
| public static void load()
| {
| try{
| if(properties == null)
| {
| properties = new Properties();
| properties.load(Thread.currentThread().getContextClassLoader().getResourceAsStream("CommonInformation.properties"));
| }
| }
| catch(Exception e)
| {
| return;
| }
| }
|
|
| public static String getProperty(String property) {
| try{
| return properties.getProperty(property);
| }
| catch(Exception e)
| {
| return null;
| }
| }
| }
|
But always return the ClassLoader of last deployed war.
So the file .properties read is always the file of last deployed war.
I try use ServletContextListener the load of file .properties is ok, but when I get any propertie of this file is returned propertie of last deployed war.
How i can resolve this problem?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980790#3980790
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980790
19 years, 5 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Messaging and Remoting
by ovidiu.feodorov@jboss.com
Tim wrote : By avoiding blocking on reads or writes it enables a small number of threads to handle a large amound of "connections". If reads or writes were blocking that wouldn't be possible. That's the crux of the matter.
Well, read again my previous post. I am quoting it here for completness:
"First there is the fact that a non-blocking IO implementation, complete with readiness selection, allows a single thread (or a precisely limited number of threads) to efficiently do what in a thread-per-connection model would take a number of threads equal with the number of connections. This approach a) avoids thread context switching that becomes toxic after the number of threads in use reaches a certain threshold and b) prevents using the thread scheduler as a substitute for a readiness selection mechanism (threads that suddenly get something to read, or write, are un-blocked by the scheduler, which acts as a "de facto" readiness detector)."
So I really don't see what we're arguing about.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980789#3980789
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980789
19 years, 5 months
[Design of JBoss ESB] - Re: Design of a Content Based Routing Service
by ddunkin
"mark.little(a)jboss.com" wrote : "ddunkin" wrote : I have a ProcessPurchaseOrder document that comes into the system. That document is routed to the order management system for the supplier identified in the document. Now what I want to do is send a copy of all ProcessPurchaseOrder documents to a component that will extract certain information and store it for statistical analysis. It's a separation of concerns. The listener doesn't need to know anything about the statistical analysis. Neither does the order management system.
| |
|
| So this is routing sequentially though? I had assumed you were maybe talking about routing the message concurrently, e.g., like a broadcast of the message to multiple destinations.
|
No, it would be concurrent. The order management system shouldn't have to wait for the statisticl analysis system.
"mark.little(a)jboss.com" wrote :
| anonymous wrote :
| | Another example is a document that contains hours worked on a case where the employee working the case is paid billable time. That document should go to both receivables, so that the client can be billed, and to payroll, so the employee can be paid.
|
| Is this done sequentially or concurrently? Do you wait for the receivables to ack before sending to the payroll? If the answer is yes, then there's not really a problem AFAICT. If the answer is no, then we're talking about "asynchronous" interactions and, assuming the sender wants some kind of ack from each, the underlying infrastructure will need to be able to tally responses with "rendezvous" requests from the client, in just the same way it would for any "asynchronous" interaction.
It would be concurrent. I think the assumption that the sender needs an ack from each receiver is not necessarily true. In fact, the sender doesn't even need to know where the message is going, just that the message was received by the ESB.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980787#3980787
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980787
19 years, 5 months
[Design of JBoss ESB] - Re: Design of a Content Based Routing Service
by daniel.brum@jboss.com
anonymous wrote : Is this done sequentially or concurrently? Do you wait for the receivables to ack before sending to the payroll? If the answer is yes, then there's not really a problem AFAICT. If the answer is no, then we're talking about "asynchronous" interactions and, assuming the sender wants some kind of ack from each, the underlying infrastructure will need to be able to tally responses with "rendezvous" requests from the client, in just the same way it would for any "asynchronous" interaction.
I would say that this is actually not a part of routing, but in fact a BPM process that keeps track of all the routings required for a particular message that comes in. The routing should be fire and forget, and it should be the job of an encompassing business process definition that knows if all parties required have been notified or not. If not, maybe it takes an action to have the message routed again, or if it's an optional recipient (say a statistical analysis system) that can live without the data being there for a real-time process, then it let's the logic continue, etc.
I don't think we should be coupling the routing system to the systems receiving those routed data sets.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980774#3980774
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980774
19 years, 5 months
[Design of JBoss ESB] - Re: Design of a Content Based Routing Service
by mark.little@jboss.com
"ddunkin" wrote : anonymous wrote : I think the first question to ask is: why multiple destinations? The answer to that will impact the rest.
|
| I have a ProcessPurchaseOrder document that comes into the system. That document is routed to the order management system for the supplier identified in the document. Now what I want to do is send a copy of all ProcessPurchaseOrder documents to a component that will extract certain information and store it for statistical analysis. It's a separation of concerns. The listener doesn't need to know anything about the statistical analysis. Neither does the order management system.
|
So this is routing sequentially though? I had assumed you were maybe talking about routing the message concurrently, e.g., like a broadcast of the message to multiple destinations.
anonymous wrote :
| Another example is a document that contains hours worked on a case where the employee working the case is paid billable time. That document should go to both receivables, so that the client can be billed, and to payroll, so the employee can be paid.
Is this done sequentially or concurrently? Do you wait for the receivables to ack before sending to the payroll? If the answer is yes, then there's not really a problem AFAICT. If the answer is no, then we're talking about "asynchronous" interactions and, assuming the sender wants some kind of ack from each, the underlying infrastructure will need to be able to tally responses with "rendezvous" requests from the client, in just the same way it would for any "asynchronous" interaction.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980771#3980771
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980771
19 years, 5 months