May 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss jBPM] - Re: Identity module cascading delete of doom

by kukeltje

no objections. afaik it was mentioned before by someone. There might even be a jira issue for this View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043915#4043915 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043915

17 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Scoped deployments

by timfox

"clebert.suconic(a)jboss.com" wrote : | I thought ObjectMessages could still use it. Not currently. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043864#4043864 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043864

17 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Scoped deployments

by timfox

"clebert.suconic(a)jboss.com" wrote : | I'm just following Scott's suggestion for jboss-client.jar. | | I'm hopping that a reference into jboss-messaging-client.jar would also add other libraries. I'm sure Scott had good reason for suggesting it, but you need to make sure you're understanding his real motivation behind the suggestion before just adding it blindly :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043863#4043863 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043863

17 years, 9 months

1
0
0 / 0

[Design of JBoss jBPM] - Identity module cascading delete of doom

by david.lloyd＠jboss.com

In User.hbm.xml, we have this collection: | <set name="memberships" cascade="all"> | <key column="USER_" /> | <one-to-many class="org.jbpm.identity.Membership" /> | </set> | In Group.hbm.xml, the same collection is referenced: | <set name="memberships" cascade="all"> | <key column="GROUP_" /> | <one-to-many class="org.jbpm.identity.Membership" /> | </set> | and Membership.hbm.xml has: | <many-to-one name="user" column="USER_" cascade="all" foreign-key="FK_ID_MEMSHIP_USR"/> | <many-to-one name="group" column="GROUP_" cascade="all" foreign-key="FK_ID_MEMSHIP_GRP"/> | This is a problem because if you delete a user or a group, it cascades madly through all the users and groups that are related by membership. I think that the desired behavior would be that if a User is deleted, then all the corresponding memberships should be deleted but NOT the groups. Likewise, if a Group is deleted, the memberships for that Group should also be deleted, but not the Users. I think (pending some testing) that the way to achieve this is to remove the cascade="all" from the "many-to-one" tags in Membership. Anyone have any objection or thoughts on this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043816#4043816 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043816

17 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Scoped deployments

by clebert.suconic＠jboss.com

anonymous wrote : We don't use jboss serialization any more, so this can be removed. I thought ObjectMessages could still use it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043802#4043802 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043802

17 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Scoped deployments

by clebert.suconic＠jboss.com

anonymous wrote : I thought this was only uses if it is an executable jar file, or, say when inspected by an app server? I'm just following Scott's suggestion for jboss-client.jar. I'm hopping that a reference into jboss-messaging-client.jar would also add other libraries. anonymous wrote : I believe it is "Class-Path", not "classpath": Oops.. Thanks! :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043792#4043792 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043792

17 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Scoped deployments

by timfox

"clebert.suconic(a)jboss.com" wrote : | Also.. I'm changing jboss-messaging-client.jar to use classpath argument on METAINF as follows: | How does listing the jars on the Class-Path attribute in the manifest help? I thought this was only uses if it is an executable jar file, or, say when inspected by an app server? | classpath: jboss-aop.jar jboss-remoting.jar jboss-serialization.jar ja | vassist.jar trove.jar jboss-common-core.jar jboss-logging-log4j.jar j | boss-logging-spi.jar jboss-j2ee.jar jboss-j2se.jar jnp-client.jar con | current.jar log4j.jar commons-logging.jar tomcat-coyote.jar tomcat-ht | tp.jar tomcat-util.jar | I believe it is "Class-Path", not "classpath": http://java.sun.com/j2se/1.3/docs/guide/jar/jar.html View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043791#4043791 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043791

17 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Scoped deployments

by timfox

First thing to do is get the dependencies sorted out. We don't use jboss serialization any more, so this can be removed. The tomcat jars are only needed for the remoting http transport, i don't think we need to replace them. AFAICT just need to replace remoting and AOP for 4.0.x, and no need to replace anything for 4.2.x Regarding the client classpath - are you sure we need all those jars? The tomcat ones we can probably get rid of. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043783#4043783 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043783

17 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Graphic Installer for Messaging (Repost)

by clebert.suconic＠jboss.com

"Tim Fox" wrote : The installer needs to be changed anyway (from 1.2.0.sp2) since we won't be doing scoped deployments. That's why I was looking into this. Since this setup is using our release-admin.xml, I wanted to look at how this would work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043779#4043779 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043779

17 years, 9 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Scoped deployments

by clebert.suconic＠jboss.com

This is a discussion of http://jira.jboss.com/jira/browse/JBMESSAGING-925: I'm working on this issue, and I have a question regarding tomcat-coyote.jar, tomcat-http.jar and tomcat-util.jar. I know what to do with jboss-remoting, serialization and aop. But I don't have any clue about what to do with those. Should I replace them anywhere on the server? Also.. I'm changing jboss-messaging-client.jar to use classpath argument on METAINF as follows: | Manifest-Version: 1.0 | Ant-Version: Apache Ant 1.7.0 | Created-By: 1.5.0_07-b03 (Sun Microsystems Inc.) | classpath: jboss-aop.jar jboss-remoting.jar jboss-serialization.jar ja | vassist.jar trove.jar jboss-common-core.jar jboss-logging-log4j.jar j | boss-logging-spi.jar jboss-j2ee.jar jboss-j2se.jar jnp-client.jar con | current.jar log4j.jar commons-logging.jar tomcat-coyote.jar tomcat-ht | tp.jar tomcat-util.jar | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043781#4043781 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4043781

17 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums May 2007