July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Moved: (JBMICROCONT-98) Make the annotation metadata more free format

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBMICROCONT-98?page=all ] Kabir Khan moved JBTPL-20 to JBMICROCONT-98: -------------------------------------------- Project: JBoss MicroContainer (was: README 1st - JBoss Project Template) Key: JBMICROCONT-98 (was: JBTPL-20) > Make the annotation metadata more free format > --------------------------------------------- > > Key: JBMICROCONT-98 > URL: http://jira.jboss.com/jira/browse/JBMICROCONT-98 > Project: JBoss MicroContainer > Issue Type: Task > Reporter: Kabir Khan > Assigned To: Ivelin Ivanov > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBREM-527) Allow user to pass Connector to be used for stream server

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-527?page=comments#action_12339789 ] Tom Elrod commented on JBREM-527: ---------------------------------- Opps. Meant stream server to be created internally, not callback server. > Allow user to pass Connector to be used for stream server > --------------------------------------------------------- > > Key: JBREM-527 > URL: http://jira.jboss.com/jira/browse/JBREM-527 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: stream > Affects Versions: 2.0.0.Beta2 (Boon) > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: 2.0.0.CR1 (Boon) > > > Currently when sending a stream from the client to the server, the client internally creates a Connector to receive read requests from the server's stream proxy. Need to allow user to be able to specify their own Connector to use for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBREM-527) Allow user to pass Connector to be used for stream server

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-527?page=comments#action_12339788 ] Tom Elrod commented on JBREM-527: ---------------------------------- Also added following to Client: public Object invoke(InputStream inputStream, Object param, InvokerLocator streamServerLocator) throws Throwable so can also just pass the locator url of the callback server to be created internally. > Allow user to pass Connector to be used for stream server > --------------------------------------------------------- > > Key: JBREM-527 > URL: http://jira.jboss.com/jira/browse/JBREM-527 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: stream > Affects Versions: 2.0.0.Beta2 (Boon) > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: 2.0.0.CR1 (Boon) > > > Currently when sending a stream from the client to the server, the client internally creates a Connector to receive read requests from the server's stream proxy. Need to allow user to be able to specify their own Connector to use for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

1
0
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-97) Move AnnotationCreator into MC from AOP

by Kabir Khan (JIRA)

Move AnnotationCreator into MC from AOP --------------------------------------- Key: JBMICROCONT-97 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-97 Project: JBoss MicroContainer Issue Type: Task Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: JBossMC_2_0_0M1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

1
1
0 / 0

[JBoss JIRA] Created: (JBAOP-277) Move AnnotationCreator into MC

by Kabir Khan (JIRA)

Move AnnotationCreator into MC ------------------------------ Key: JBAOP-277 URL: http://jira.jboss.com/jira/browse/JBAOP-277 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

1
1
0 / 0

[JBoss JIRA] Commented: (HIBERNATE-36) @ManyToMany associations removed after entity listener @PreUpdate call

by Henrique Sousa (JIRA)

[ http://jira.jboss.com/jira/browse/HIBERNATE-36?page=comments#action_12339787 ] Henrique Sousa commented on HIBERNATE-36: ----------------------------------------- I still do not know why the many-to-many relations are cleared, however I was able to work around the double flush by setting the flush mode to commit in all queries created due to calls from the entity listener: entityManager.createQuery("...").setFlushMode(FlushModeType.COMMIT).getSingleResult(); > @ManyToMany associations removed after entity listener @PreUpdate call > ---------------------------------------------------------------------- > > Key: HIBERNATE-36 > URL: http://jira.jboss.com/jira/browse/HIBERNATE-36 > Project: Hibernate > Issue Type: Bug > Environment: JBoss AS 4.0.4 CR2, Windows XP, JDK 1.5_05 > Reporter: Henrique Sousa > Assigned To: Steve Ebersole > > After calling EntityManager.merge() for an entity, its @EntityListeners @PreUpdate methods are invoked. In the @PreUpdate method, locate another entity with @ManyToMany associations. After the @PreUpdate method completes, the @ManyToMany associations are cleaned. Below is some code which can be tested. Call the doSomething() method in the RemoteInterfaceBean to perform the test. > /*** Bar.java */ > package com.foo; > import javax.persistence.Entity; > import javax.persistence.EntityListeners; > import javax.persistence.Id; > import javax.persistence.ManyToOne; > import javax.persistence.Table; > @Entity > @Table(name = "TEST_BAR") > @EntityListeners(MyListener.class) > public class Bar { > private Integer id; > private String description; > private MyEntity entity; > > @Id > public Integer getId() { > return id; > } > public String getDescription() { > return description; > } > @ManyToOne > public MyEntity getEntity() { > return entity; > } > > public void setId(Integer id) { > this.id = id; > } > public void setDescription(String description) { > this.description = description; > } > public void setEntity(MyEntity entity) { > this.entity = entity; > } > > public boolean equals(Object obj) { > if (!(obj instanceof Bar)) > return false; > Integer other = ((Bar)obj).getId(); > return id == null? other == null: id.equals(other); > } > > public int hashCode() { > return getClass().getName().hashCode() + (id == null? 0: id.hashCode()); > } > } > /*** MyEntity.java */ > package com.foo; > import java.util.Set; > import javax.persistence.Entity; > import javax.persistence.FetchType; > import javax.persistence.Id; > import javax.persistence.JoinColumn; > import javax.persistence.JoinTable; > import javax.persistence.ManyToMany; > import javax.persistence.Table; > @Entity > @Table(name = "TEST_ENTITY") > public class MyEntity { > > private Integer id; > private String description; > private Set<Target> targets; > > @Id > public Integer getId() { > return id; > } > public String getDescription() { > return description; > } > @ManyToMany(fetch = FetchType.LAZY) > @JoinTable(name = "TEST_ASSOCIATION", > joinColumns = {@JoinColumn(name = "ENTITY")}, > inverseJoinColumns = {@JoinColumn(name = "TARGET")}) > public Set<Target> getTargets() { > return targets; > } > public void setId(Integer id) { > this.id = id; > } > public void setDescription(String description) { > this.description = description; > } > public void setTargets(Set<Target> targets) { > this.targets = targets; > } > > public boolean equals(Object obj) { > if (!(obj instanceof MyEntity)) > return false; > Integer other = ((MyEntity)obj).getId(); > return id == null? other == null: id.equals(other); > } > > public int hashCode() { > return getClass().getName().hashCode() + (id == null? 0: id.hashCode()); > } > } > /*** MyListener.java */ > package com.foo; > import javax.naming.InitialContext; > import javax.persistence.PrePersist; > import javax.persistence.PreUpdate; > public class MyListener { > private static ThreadLocal<Object> running = new ThreadLocal<Object>(); > > @PrePersist > @PreUpdate > public void test(Bar bar) { > System.out.println("Started listener"); > if (running.get() != null) { > System.out.println("Already running on this thread! Interrupting listener"); > return; > } > running.set(new Object()); > try { > RemoteInterface ejb = (RemoteInterface)new InitialContext().lookup( > "WorldNet/RemoteInterfaceBean/remote"); > MyEntity entity = ejb.getEntity(); > bar.setEntity(entity); > System.out.println("entity description: " + entity.getDescription()); > System.out.println("bar id: " + bar.getId()); > System.out.println("Finished listener"); > } > catch (Exception e) { > e.printStackTrace(); > } > finally { > running.set(null); > } > } > > } > /*** RemoteInterface.java */ > package com.foo; > import javax.ejb.Remote; > @Remote > public interface RemoteInterface { > void doSomething(); > > MyEntity getEntity(); > > } > /*** RemoteInterfaceBean.java */ > package com.foo; > import java.util.Random; > import javax.ejb.Stateless; > import javax.persistence.EntityManager; > import javax.persistence.PersistenceContext; > @Stateless > public class RemoteInterfaceBean implements RemoteInterface { > static EntityManager staticPersistence; > > @PersistenceContext > private EntityManager persistence; > > public void doSomething() { > simplify(); > Bar bar = new Bar(); > bar.setId(5); > bar.setDescription("" + new Random().nextInt()); > persistence.merge(bar); // MUST be merge, not persist!!! > } > > public MyEntity getEntity() { > MyEntity entity = (MyEntity)persistence.createQuery( > "select x from MyEntity x join fetch x.targets").getSingleResult(); > return entity; > } > > private void simplify() { > staticPersistence = persistence; > } > } > /*** Target.java */ > package com.foo; > import javax.persistence.Entity; > import javax.persistence.Id; > import javax.persistence.Table; > @Entity > @Table(name = "TEST_TARGET") > public class Target { > > private Integer id; > private String description; > > @Id > public Integer getId() { > return id; > } > public String getDescription() { > return description; > } > public void setId(Integer id) { > this.id = id; > } > public void setDescription(String description) { > this.description = description; > } > > public boolean equals(Object obj) { > if (!(obj instanceof Target)) > return false; > Integer other = ((Target)obj).getId(); > return id == null? other == null: id.equals(other); > } > > public int hashCode() { > return getClass().getName().hashCode() + (id == null? 0: id.hashCode()); > } > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

1
0
0 / 0

[JBoss JIRA] Created: (JBWEB-63) Migration of JBoss AS 5 to JBoss Web

by Remy Maucherat (JIRA)

Migration of JBoss AS 5 to JBoss Web ------------------------------------ Key: JBWEB-63 URL: http://jira.jboss.com/jira/browse/JBWEB-63 Project: JBoss Web Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Remy Maucherat Assigned To: Remy Maucherat Priority: Blocker -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

1
1
0 / 0

[JBoss JIRA] Commented: (JBAS-3312) LdapExtLoginModule is missing the first role group of a nested structure

by Tobias Frech (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3312?page=comments#action_12339780 ] Tobias Frech commented on JBAS-3312: ------------------------------------ ... and LdapExtLoginModule is not documented in the JBoss AS Guide :-/ > LdapExtLoginModule is missing the first role group of a nested structure > ------------------------------------------------------------------------ > > Key: JBAS-3312 > URL: http://jira.jboss.com/jira/browse/JBAS-3312 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Security > Affects Versions: JBossAS-4.0.4.GA > Reporter: Scott M Stark > Assigned To: Scott M Stark > Fix For: JBossAS-4.0.5.CR1 > > > When traversing through a hiearchical role structure, the first matching context does not have its role name added to the resulting subject roles. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-2044) References to org.jboss.webservice.server.ServiceEndpointInterceptor from standard-jboss.xml

by Tobias Frech (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2044?page=comments#action_12339779 ] Tobias Frech commented on JBAS-2044: ------------------------------------ On JBoss 4.0.4GA installed with the AS-installer we still get this if we leave the WebSerivcestuff out: 2006-07-19 08:54:44,518 WARN [org.jboss.ejb.EjbModule] Could not load the org.jboss.ws.server.ServiceEndpointInterceptor interceptor java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.ws.server.ServiceEndpointInterceptor at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212) at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:511) > References to org.jboss.webservice.server.ServiceEndpointInterceptor from standard-jboss.xml > -------------------------------------------------------------------------------------------- > > Key: JBAS-2044 > URL: http://jira.jboss.com/jira/browse/JBAS-2044 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web Services > Affects Versions: JBossAS-4.0.3RC1 > Environment: SuSE-9.3 with JDK-1.5_04 > Reporter: Jesper Pedersen > Assigned To: Thomas Diesler > Priority: Minor > Fix For: JBossAS-4.0.4.GA > > > The class org.jboss.webservice.server.ServiceEndpointInterceptor (jboss-ws4ee.jar) is currently deployed in the webservice module under deploy. > If the webservice module is removed the server currently generates warnings during startup since > o Standard Stateless SessionBean > o Clustered Stateless SessionBean > have the interceptor defined (standardjboss.xml) - that is if you use SLSBs. > A solution would be to deploy jboss-ws4ee.jar in server/lib and keep the rest under the webservice module. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

1
0
0 / 0

[JBoss JIRA] Closed: (JBCACHE-108) Make CacheLoader use SPI rather than TreeCache implementation

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-108?page=all ] Manik Surtani closed JBCACHE-108. --------------------------------- > Make CacheLoader use SPI rather than TreeCache implementation > ------------------------------------------------------------- > > Key: JBCACHE-108 > URL: http://jira.jboss.com/jira/browse/JBCACHE-108 > Project: JBoss Cache > Issue Type: Sub-task > Reporter: Bela Ban > Assigned To: Manik Surtani > Fix For: 2.0.0 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

20 years

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-jira July 2006