[Design the new POJO MicroContainer] - Re: JBMICROCONT-105, structural deployer, vfs refactoring
by scott.stark@jboss.org
One issue I'm running into with the refactored structural deployer code is that a number of the unit tests expect that "top-level" deployments are accepted as valid. Both the JarStructure and FileStructure were accepting top-level directories (based on DeploymentContext.isTopLevel()) as valid without validating anything about the actual structure.
Before trying to restore this behavior, I want to question this as a valid construct. Its essentially a mix of pre-determined structure with the root being marked as a valid deployment, but the children unknown. With the new structure deployment spi, such a deployment would have to have a StructureMetaData with a ContextInfo that corresponds to the valid root. With such a StructureMetaData, there is not much point in validating that the structure deployers recognize the VirtualFile for the root as valid since its declared to be so.
I'll hack around it for now and come back to this if its causing other issues.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980472#3980472
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980472
19 years, 5 months
[Design of POJO Server] - Re: VirtualFile.toURL() returning vfsfile:
by bill.burke@jboss.com
For example:
| 13:06:18,406 ERROR [AbstractKernelController] Error installing to Create: name=jboss.management.local:j2eeType=J2EEDomain,name=Manager state=Configured mode=Manual requiredState=Create
| java.lang.NoClassDefFoundError: org/jboss/management/j2ee/statistics/StatisticsProvider
| at java.lang.ClassLoader.defineClass1(Native Method)
| at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
| at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
| at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
| at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
| at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
| at java.security.AccessController.doPrivileged(Native Method)
| at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
| at org.jboss.mx.loading.RepositoryClassLoader.findClassLocally(RepositoryClassLoader.java:566)
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980458#3980458
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980458
19 years, 5 months
[Design of JBoss ESB] - Re: Design of a Content Based Routing Service
by ddunkin
Upgrading to JBossRules 3 will mean rewriting the DSL, which is fine. I haven't looked at how it's done in the new version, but it was dead simple to write a DSL for Drools. What do you mean by "plain java implementation?"
Do you want to support a single language for rule matching (e.g. XPath) or leave it open-ended/extensible? I think that will help define whether or not to support Serializable. It would be cool to be able to specify a rule using EL on a POJO graph and XPath on an XML document. I guess it wouldn't really matter as long as the RHS of the rule fulfilled some contract like asserting a Destination to working memory.
For my needs, if no rule matches the message, the message router returns an error. I could envision others wanting a default route/destination. I'm not very familiar with the action chain, but could that just be another action for those that require that functionality? I.e. an action after the CBR action would check for a defined destination and set a default if none exists. I suppose that would only work if the CBR service returns an action name instead of forwarding the message.
I don't have an immediate need for sending one message to multiple destinations, but I will in the future. The only tricky part about that I can think of is with synchronous messages. If I send a message and am expecting a reply, who do I accept a reply from? My thought would be for synchronous messages to have one primary destination, from which the reply would come, and secondary destinations, which would be sent the message asynchronously. I haven't followed JBossESB that closely -- is there even the concept of synchronous and asynchronous messages?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3980455#3980455
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3980455
19 years, 5 months