August 2008 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: JBMICROCONT-330 - Preconfigured MDR and scopes

by adrian＠jboss.org

"alesj" wrote : "adrian(a)jboss.org" wrote : | | 1) ScopingOverridingTestCase | | | | This is failing because of the problem I suspected when taling to Kabir | | about the issue that led to finding JBMICROCONT-330 | | i.e. a scoped controller context is sharing the same metadata | | as one that should not be scoped. | | | How did this ever worked? :-) | Or what changed that 'broke' this? | It only worked because the second bean to be deployed overwrote the first's bean instance scope. That's what I fixed with JBMICROCONT-330 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169872#4169872 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169872

17 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBMICROCONT-330 - Preconfigured MDR and scopes

by adrian＠jboss.org

You need to change the name of the INSTANCE scope for scoped beans to include something that identifies the scoped controller, e.g. | new ScopeKey(CommonLevels.INSTANCE, scopedController.getScopeID() + "/" name.toString()); | It should be something predictable - not hashCode(). You also need to be able to do this ahead of time in the deployers so people can populate the instance scope before controller context exists. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169871#4169871 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169871

17 years, 8 months

1
0
0 / 0

[Design of JBoss ESB] - Re: JBossESB Filters - Using Spring context on Filters

by mark.little＠jboss.com

At first glance it should be possible, though nothing out-of-the-box as yet. I'll take a look. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169848#4169848 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169848

17 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBMICROCONT-330 - Preconfigured MDR and scopes

by alesj

"alesj" wrote : | Perhaps we should change what value we keep at INSTANCE scope. | e.g. the stuff we already discussed, adding ID to ControllerContext, | which is unique, and pass that as INSTANCE value. | Changing INSTANCE value to | scopeKey.addScope(CommonLevels.INSTANCE, name.toString() + hashCode()); | if (className != null) | scopeKey.addScope(CommonLevels.CLASS, className); | setScope(scopeKey); | setMutableScope(new ScopeKey(CommonLevels.INSTANCE, name.toString() + hashCode())); | Only breaks tests that explicitly set MetaData to repository via bean name. All other tests pass. Perhaps completely random/unique INSTANCE value isn't good solution, since then you cannot do what we do in MutableMetaDataTestCase, setting predetermined metadata to an instance. But then again, getting some ID in advance, applying predetermined metadata, and the somehow passing this ID to ControllerContext, is again the same problem as we already have - how to uniquely map ID to class and bean name. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169845#4169845 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169845

17 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBMICROCONT-330 - Preconfigured MDR and scopes

by alesj

"adrian(a)jboss.org" wrote : | 1) ScopingOverridingTestCase | | This is failing because of the problem I suspected when taling to Kabir | about the issue that led to finding JBMICROCONT-330 | i.e. a scoped controller context is sharing the same metadata | as one that should not be scoped. | How did this ever worked? :-) Or what changed that 'broke' this? I remember adding WORK scope to handle this duplicate issue. Looking at the code, I don't see how that helped, since it's the other two scopes that are 'interesting'; CLASS and INSTANCE, which were always the same. I don't see a good way to solve this, since although scoped, beans should still share the same metadata, if the key matches, e.g. CLASS scope on the same class. Perhaps we should change what value we keep at INSTANCE scope. e.g. the stuff we already discussed, adding ID to ControllerContext, which is unique, and pass that as INSTANCE value. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169840#4169840 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169840

17 years, 8 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Problem in Content Based Routing

by beve

anonymous wrote : 2008-08-11 15:52:13,700 WARN [org.jboss.soa.esb.message.mapping.ObjectMapper] The value of body.Task is null You are getting this error because the Task object in not located in the location named Task. The task object instance is located as the default entry: anonymous wrote : objects: {org.jboss.soa.esb.message.defaultEntry=task.Task Try adding a action that puts the Task object in the correct location: message.getBody().add("Task",message.getBody().get()); Regards, /Daniel View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169837#4169837 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169837

17 years, 8 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Problem in Content Based Routing

by Neha29

hi beve, Thankyou for the reply. I receive the following error when i execute the code . | 2008-08-11 15:51:52,216 INFO [org.quartz.core.QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started. | 2008-08-11 15:52:13,700 INFO [STDOUT] Message structure: | 2008-08-11 15:52:13,700 INFO [STDOUT] [ message: [ JBOSS_XML ] | header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/B/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: ID:JBM-262656 RelatesTo: jms:correlationID#ID:JBM-262144 ] | context: [ ] | body: [ objects: {org.jboss.soa.esb.message.defaultEntry=task.Task@1b3a9cd, org.jboss.soa.esb.message.defaultEntry-set-stack=Deferred serialized value: 50e304} ] | fault: [ ] | attachments: [ Named:{}, Unnamed:[] ] | properties: [ {org.jboss.soa.esb.message.time.dod=Mon Aug 11 15:52:13 IST 2008, org.jboss.soa.esb.message.time.dob=Deferred serialized value: 68291b, org.jboss.soa.esb.message.source=Deferred serialized value: 62c67e, jbesbfilename=SimpleCBRTest.log, org.jboss.soa.esb.message.transport.type=Deferred serialized value: d58bd5, javax.jms.message.redelivered=false, org.jboss.soa.esb.gateway.original.queue.name=Deferred serialized value: 1cf4e67} ] ] | 2008-08-11 15:52:13,700 WARN [org.jboss.soa.esb.message.mapping.ObjectMapper] The value of body.Task is null | 2008-08-11 15:52:31,872 ERROR [org.jboss.soa.esb.actions.ContentBasedWiretap] No rule destination(s) [normal, express, test] were matched, . Please fix your configuration and/or routing rules. | 2008-08-11 15:52:41,278 WARN [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/B/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: ID:JBM-262656 RelatesTo: jms:correlationID#ID:JBM-262144 ] | org.jboss.soa.esb.actions.ActionProcessingException: No rule destination(s) [normal, express, test] were matched, . Please fix your configuration and/or routing rules. | at org.jboss.soa.esb.actions.ContentBasedWiretap.process(ContentBasedWiretap.java:106) | at org.jboss.soa.esb.actions.ContentBasedRouter.process(ContentBasedRouter.java:52) | at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) | at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:530) | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) | at java.lang.Thread.run(Thread.java:595) | 2008-08-11 15:52:41,294 WARN [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] No fault address defined for fault message! To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/B/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.url.pkgs : org.jnp.interfaces/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : AUTO_ACKNOWLEDGE/>, <wsa:ReferenceProperties jbossesb:transacted : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > ] MessageID: ID:JBM-262656 RelatesTo: jms:correlationID#ID:JBM-262144 | I am sending Task object with status =1 . In body the object is there but still the error comes that body.Task is null. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169833#4169833 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169833

17 years, 8 months

1
0
0 / 0

[Design of JBossCache] - Re: JBoss Cache 3.0 and JBoss AS 5

by manik.surtani＠jboss.com

Ok, this is good to know. Would these be in AS5 at some point (if not 5.0, a point release afterwards)? And I guess more importantly EAP 5? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169831#4169831 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169831

17 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Some duplicated code in MessageReferenceImpl

by jmesnil

the code formatting has been corrected and the duplicate code is removed: expire(), move() and sendToDLQ() now all calls the private move() method View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169819#4169819 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169819

17 years, 8 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Problem in Content Based Routing

by beve

Hi, try printing the whole message structure by adding the property "printfull" and setting it to "true" on the SystemPrintln action. This will show the location of the Task object in the message. By the look of this: <object-path esb="body.Task" /> you are expecting it to be bound under the location 'Task'. One quickstart that might help you out is the business_rules_service quickstart. Regards, /Daniel View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169789#4169789 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169789

17 years, 8 months

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 August 2008