November 2006 - jboss-dev-forums - Jboss List Archives

[Design of JBoss jBPM] - Re: coolest feature ever

by kukeltje

AHHHHHHHHHHH I'm ashamed, I did not mean to play down jboss messaging. Just that I would never run it in production as part of the bpm engine/deployment. It would be a separate deployment with it's own release cycles etc.... come to think of it. I have to try it again. It was a long time ago and it has matured greatly from what I've read. I'm curious though for the reason to use a different ui framework and not build e.g. jsf/facelets components View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986062#3986062 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986062

19 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Install not working

by kukeltje

wrong forum, use the user forum View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986060#3986060 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986060

19 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: How to Configure JBPM to use a JMS provider

by tom.baeyens＠jboss.com

the plan is to release 3.2 around newyear View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986040#3986040 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986040

19 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: coolest feature ever

by tom.baeyens＠jboss.com

But i am also interested to know if there was more to it then just a joke. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986039#3986039 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986039

19 years, 4 months

1
0
0 / 0

[Design of JBoss jBPM] - keeping track of cvs commits

by tom.baeyens＠jboss.com

I knew we had fisheye for a while http://fisheye.labs.jboss.com/browse/JBPM But I just discovered the RSS feed feature of fisheye. Really cool ! It gives a nice overview of who committed what with comments and diffs at hand. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986038#3986038 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986038

19 years, 4 months

1
0
0 / 0

[Design of JBossCache] - Re: Name change for PojoCache annotation

by ben.wang＠jboss.com

"genman" wrote : For inheritence, it seems appropriate to add an attribute rather than a separate annotation, for example: | | @Replicable(instanceOf=true) | or | @Replicable(subclasses=true) | | There might be some sort of relation term that would fit better than "instanceof", that means "child classes also". | Idea of using attribute is very good but it won't work as is. If you look at jbosscache-aop.xml, you will see that the now @InstanceOfPojoCacheable tag is used inside the JBoss Aop prepare statement: | <prepare expr="field(!static * $instanceof{(a)org.jboss.cache.pojo.annotation.InstanceOfPojoCacheable}->*)" /> | So replace that with a generic annotation with additional attribute won't work. "sub-class" in better than InstanceOf (I am following the JBoss Aop usage, as you can see here), but SubClassOfReplicable, e.g., seems wordy? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986033#3986033 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986033

19 years, 4 months

1
0
0 / 0

[Design of JBossCache] - Re: static field replication in PojoCache

by ben.wang＠jboss.com

Yes, with the proposed approach, we will have to document that you will attach to be able to replicate the static fields; that means, you need an "aspectized" POJO instance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986032#3986032 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986032

19 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Re: Serilizability of aop proxy

by scott.stark＠jboss.org

The NotSerializableException was valid as the target was not serializable. The only question is why the deserialization of the proxy is not restoring the underlying bean properties correctly. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986027#3986027 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986027

19 years, 4 months

1
0
0 / 0

[Design of POJO Server] - Serilizability of aop proxy

by scott.stark＠jboss.org

When I tried the JndiBinding in the server where the naming service serializes the entries, its failing because the wrapping aop container proxy is not: | Caused by: java.io.NotSerializableException: AOPContainerProxy$0 | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081) | | at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) | at java.rmi.MarshalledObject.<init>(MarshalledObject.java:92) | at org.jnp.interfaces.MarshalledValuePair.<init>(MarshalledValuePair.jav | a:65) | at org.jnp.interfaces.NamingContext.bind(NamingContext.java:562) | ... 76 more | I updated the org.jboss.test.microcontainer.test.JndiLifeCycleTestCase to serialize the bindngs, and although its not failing with this error, its not unserializing the bean correctly. Is the proxy expected to reproduce the underlying object behavior with regard to serialization? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986024#3986024 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986024

19 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: What is the status of the server integration code?

by ovidiu.feodorov＠jboss.com

Scott, I've taken a quick look at the AS head. The most important thing is that dependencies are OK: Remoting 2.2.0.Alpha2, Serialization 1.0.3.GA. I don't know exactly what "snapshot" means for AOP, but as long as is higher than 1.5.0.GA, Messaging should be fine. In conclusion, there's is no reason not to have a fully working unscoped Messaging deployment. I want to adjust the deployment descriptors under jboss-head/messaging so everything works. I plan to use customized copies in jboss-head/messaging/src/etc/..., as we discussed (http://jira.jboss.org/jira/browse/JBMESSAGING-632). http://jira.jboss.org/jira/browse/JBMESSAGING-631 becomes obsolete if I do this, so I'll close it. Will post here if I have questions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3986021#3986021 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3986021

19 years, 4 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 November 2006