[Design of JBoss jBPM] - Re: [sim] Configuration of Experiment
by camunda
Okay, a small misunderstanding here ;-) I know what's a DSL, my problem was how to apply it here.
But if I read it right between the lines, you mean to have a XML-based "DSL" to configure the scenarios. I wouldn't have called it DSL in this approach, but I think you can.
But the name DSL maybe strengthen the idea to make the scenario description a bit more general, no tied to jPDL or even jBPM, but "only" for simulation scenarios of business processes.
Basically, I like this idea, but I think I prefer a two way approach then: Embedding in the process definition (namespaces or not) for fast and easy use, and an own scenario description XML file (some kind of DSL if you wish) for more complex scenarios (information there override the "inline" configuration).
I think, this would be a good solution, easy but also powerful.
One additonal thought: The external scenario description is a good idea for an addtional reason: When porting simulation to jbpm 4 with different languages, it is maybe not so easy to embedd stuff in BPEL or XPDL process descriptions like it is now in jPDL.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092255#4092255
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092255
18 years, 6 months
[Design of JBossXB] - @XmlElementWrapper/@XmlElements
by scott.stark@jboss.org
I'm trying to use @XmlElementWrapper/@XmlElements to create the ear modules, but its not parsing as expected. I created a simple test in jbossxb that is also failing to parse. See the org.jboss.test.xb.builder.object.element.wrapper.test.WrapperUnitTestCase
testFooWrapper fails with:
anonymous wrote :
| Caused by: org.jboss.xb.binding.JBossXBRuntimeException: float not found as a child of bar
| at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:370)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402)
| at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
| at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
| at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
| at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
| at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:180)
| ... 22 more
|
testFoo2Wrapper is essentially the same, but Foo2 has a parameterized items property. This fails with:
anonymous wrote :
| Caused by: java.lang.InstantiationException
| at sun.reflect.InstantiationExceptionConstructorAccessorImpl.newInstance(InstantiationExceptionConstructorAccessorImpl.java:30)
| at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
| at org.jboss.reflect.plugins.introspection.ReflectionUtils.newInstance(ReflectionUtils.java:136)
| at org.jboss.reflect.plugins.introspection.ReflectConstructorInfoImpl.newInstance(ReflectConstructorInfoImpl.java:104)
| at org.jboss.joinpoint.plugins.BasicConstructorJoinPoint.dispatch(BasicConstructorJoinPoint.java:80)
| at org.jboss.beans.info.plugins.AbstractBeanInfo.newInstance(AbstractBeanInfo.java:222)
| at org.jboss.beans.info.plugins.AbstractBeanInfo.newInstance(AbstractBeanInfo.java:216)
| at org.jboss.xb.spi.AbstractBeanAdapter.construct(AbstractBeanAdapter.java:115)
| ... 41 more
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092236#4092236
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092236
18 years, 6 months
[Design of JBossCache] - Re: Proxy Based POJOs (No AOP) in POJO Cache
by jason.greene@jboss.com
"bela(a)jboss.com" wrote : I don't like this approach, as it defeats the uniformity of byte code instrumentation. I always disliked that - although we do instrument user classes - we cannot do the same for collections, so that's where we use AOP proxies.
| I'd prefer a uniform approach. Having to writter getters and setters in one case and being able to use complete POJOs in another is cumbersome IMO.
Thanks for sharing your thoughts on this, to be honest, my initial reaction to this request was pretty much the same. I agree that the AOP approach is better. I also don't like introducing confusion, and I have a feeling that having to reget proxy objects after they are attached will do exactly that. However, if there is enough community demand for this, especially enough that someone is willing to submit the code to do it, provided the final patch looks good, and doesn't over complicate the code base, I'm ok with making some kind of option for it.
-Jason
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4092227#4092227
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4092227
18 years, 6 months