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

by vinodkv

hi I have 2 processes p1 and p2. I want to call p2 in p1. I have made both the processes separately and deployed them separately too. p2 was deployed first and p1 later. Now when i call p2 in p1, it says cannot initiate process as the ProcessDefinition is NULL. This happens even when i deploy both the processes together. Please provide a solution. Thanks in advance View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168880#4168880 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168880

17 years, 5 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Thread started regarding a common marshalling framework

by david.lloyd＠jboss.com

See http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168874 for the main thread. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168876#4168876 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168876

17 years, 5 months

1
0
0 / 0

[Design of JBoss Serialization] - Thread started regarding a common marshalling framework

by david.lloyd＠jboss.com

See http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168874 for the main thread. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168875#4168875 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168875

17 years, 5 months

1
0
0 / 0

[Design of JBossCache] - Common marshalling infrastructure

by david.lloyd＠jboss.com

At Manik's request, I'm starting a thread here to address this topic. I've started a rough design of an API which forms a basis for a more pluggable form of marshalling than what the basic Java serialization infrastructure provides, and I'd like to outline some of the design ideas here, as well as solicit feedback as to the usefulness of this design to JBoss Cache or any other project for that matter. The requirements being addressed are as follows (some are from Manik's https://jira.jboss.org/jira/browse/JBCACHE-1336 and some are from JBoss Remoting): * Make streams lightweight enough that they can be discarded, and/or provide a mechanism by which a stream may be reused easily and safely (that is, not leak disastrously) * Allow a pluggable scheme for writing abbreviated class headers (for example, using a short magic number for commonly-used classes) * Allow a pluggable scheme for writing actual objects * Allow custom Externalizers for specific object types * Allow a pluggable scheme for object replacement/resolution * Make stream headers optional and/or pluggable * Make compatibility with JDK serialization possible but optional (from both an API and a wire format perspective) (Please add any more requirements that I missed). I've made a proof-of-concept (well, evidence-of-concept anyway) API that addresses these requirements which I'll step through. I'm listing the interface name and URL before the description to prevent the forums from messing up the formatting of the URLs. * MarshallerFactory (http://tinyurl.com/5z6gqj) The main interface used to make marshaller instances is MarshallerFactory. This factory would be configured with all the pluggable elements (which I'll go through down below). Once it's fully configured, use the two create methods to create the actual Marshallers. The create option would be as lightweight as possible by design. * Marshaller (http://tinyurl.com/5ompvf) * Unmarshaller (http://tinyurl.com/6y6euy) The two marshaller interfaces, Marshaller and Unmarshaller are fairly straightforward. You would call the start() method with a stream to read from or write to, and call finish() when you're done. Also there's methods to discard the class and instance cache as described by the javadoc to facilitate pooling if desired. * StreamHeader (http://tinyurl.com/5nhg5o) You can override the stream header by implementing StreamHeader and passing it in to the MarshallerFactory. In my opinion though, the default should be to write no header. * ClassMarshaller (http://tinyurl.com/64yr7d) * ClassMarshallerFactory (http://tinyurl.com/5j4vuy) Customize writing the class header or reading and resolving the class header by implementing ClassMarshaller and its factory interface, ClassMarshallerFactory. The implementation gets plugged into the corresponding setter in MarshallerFactory. Probably it would be sensible to provide a base implementation of this class that reads and writes the class name similar to Java serialization, which can be extended to provide e.g. magic number capability as described in the comments of JBCACHE-1336. Implementations could also write classloader information or whatever. This class would also be responsible for maintaining the class cache; the instance would be discarded when the corresponding discard method is called on the marshaller/unmarshaller. * ObjectMarshaller (http://tinyurl.com/5dxhup) * ObjectMarshallerFactory (http://tinyurl.com/6dgmxy) The basic object writing mechanism is pluggable by means of the ObjectMarshaller interface and its factory. The default implementation would be to support the standard Java serialization semantics. Also this object is what implements the object instance cache. * Externalizer (http://tinyurl.com/5hofaj) It should be possible to plug in a custom externalizer for any class (for example, non-serializable classes can be forwarded by using a custom externalizer). The Externalizer interface can fulfill this function. Right now I just have it set up as a list that gets scanned. But after thinking about it, maybe the MarshallerFactory should keep a Map<Class<?>, Externalizer> or something? * MarshallerObjectInputStream (http://tinyurl.com/6csfdg) * MarshallerObjectOutputStream (http://tinyurl.com/6e67oy) Also I created lightweight(ish) abstract versions of ObjectInputStream and ObjectOutputStream which will make it much easier to make marshallers that support the Java serialization API (instances can be passed in to custom readObject() and writeObject() methods for example). There is a security access check every time an Object*Stream is constructed which we can't really get around, which might in turn slow things down enough that it would be better to pool marshallers than rebuild them per-request. Time will tell. That's about it. You can browse around that directory or check out the whole works from http://anonsvn.jboss.org/repos/sandbox/david.lloyd/jboss-marshalling/trunk and look at it, and let me know what you think of the API. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168874#4168874 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168874

17 years, 5 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - Re: JBAS-5673 - Metadata processing

by scott.stark＠jboss.org

"emuckenhuber" wrote : | Hmm actually @WebServiceRef could work, as it uses the className/fieldName for the name, therefore it would not override the existing reference. I wonder why we use a different key for these? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168872#4168872 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168872

17 years, 5 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - Re: JBAS-5673 - Metadata processing

by scott.stark＠jboss.org

"emuckenhuber" wrote : | So i guess it should rather be something like: | | | AnnotatedEJBReferenceMetaData newRef = createAnnotatedEJBRef(...); | | AnnotatedEJBReferenceMetaData existingRef = refs.get(newRef.getName()); | | if(existingRef == null) | | refs.add(ref); | | else | | mergeInjectionTargets(existingRef, newRef) | | | Or should this be done in a different way ? That sounds right, but you would need to validate that the injection target has the same type. This should not be allowed: | public class FooServlet | { | @EJB(beanName="StatefulTestBean", beanInterface=StatefulIF.class) | private StatefulIF statefulTestBean; | } | public class Foo2Servlet | { | @EJB(beanName="StatefulTestBean", beanInterface=StatefulIF2.class) | private StatefulIF2 statefulTestBean; | } | | @Session | public class SomeEJb | { | @EJB(beanName="StatefulTestBean", beanInterface=StatefulIF.class) | private StatefulIF statefulTestBean; | @EJB(beanName="StatefulTestBean", beanInterface=StatefulIF2.class) | private StatefulIF2 statefulTestBean2; | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168871#4168871 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168871

17 years, 5 months

1
0
0 / 0

[Design of JBossCache] - Re: JBCACHE-166 - TreeSet/Map, LinkedHashMap

by jason.greene＠jboss.com

Also, to emulate TreeMap I would need some methods, that are probably best on other interfaces | interface SortedData { | getSortedMap(); | } | | interface SortedChildren { | subChildMap(Object from, Object to); | tailChildMap(Object from); | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168870#4168870 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168870

17 years, 5 months

1
0
0 / 0

[Design of JBossCache] - Re: JBCACHE-166 - TreeSet/Map, LinkedHashMap

by jason.greene＠jboss.com

For now I think it makes sense as just a per node option. Another API possibility would be something like | enum Sorting {CHILDREN, DATA, BOTH} | cache.createSortedNode(Fqn fqn, Sorting sorting); | cache.createSortedNode(Fqn fqn, Sorting sorting, Comparator<?> nodeComp, Comparator<?> dataComp); | Then you don't have to worry about the sorting switching back and forth on you, as it would be fixed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168869#4168869 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168869

17 years, 5 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - Re: JBAS-5673 - Metadata processing

by emuckenhuber

"emuckenhuber" wrote : | | would result in a AnnotatedReferenceMetaData with one InjectionTarget, instead of two - which basically affects also @Resource, @PersistenceContext, @WebServiceRef processors. | Hmm actually @WebServiceRef could work, as it uses the className/fieldName for the name, therefore it would not override the existing reference. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168850#4168850 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168850

17 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Scripting Language ESB Action

by dward＠redhat.com

Kevin, I noticed you added the action. Thank you! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168839#4168839 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168839

17 years, 5 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