February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1244) Add ability to easily plugin JCR implementations

by Sohil Shah (JIRA)

Add ability to easily plugin JCR implementations ------------------------------------------------ Key: JBPORTAL-1244 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1244 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Reporter: Sohil Shah Assigned To: Sohil Shah Evaluate the CMS layer to make plugging in different JCR impls very easy Currently the impl is JackRabbit other to look at could be: Alfresco JCR impl, Exo JCR impl -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPM-836) "ejb local timer lookup problem" in EjbSchedulerService.java

by Chris Russell (JIRA)

"ejb local timer lookup problem" in EjbSchedulerService.java ------------------------------------------------------------ Key: JBPM-836 URL: http://jira.jboss.com/jira/browse/JBPM-836 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM jPDL 3.2 beta 2 Environment: cvs trunk build, jboss AS 4.0.5GA, ejb3, jms messaging deploying jbpm-enterprise.ear Reporter: Chris Russell Assigned To: Tom Baeyens After deploying the jbpm-enterprise.ear to a jboss 4.0.5ga server getting an exception when trying to signal a transition to the end state. ===EXCEPTION SEEN=== 13:04:56,785 ERROR [ProcessInstanceBean$SignalTokenListener] Action threw an exception: ejb local timer lookup problem JNDI name lookup in EjbSchedulerService using incorrect name/and or the TimerServiceBean not declared in jboss.xml. ===CODE FIXES FOR EXCEPTION== RCS file: /cvsroot/jbpm/jbpm.3/enterprise/src/main/java/org/jbpm/scheduler/ejbtimer/EjbSchedulerService.java,v retrieving revision 1.1 diff -r1.1 EjbSchedulerService.java 31c31,36 < LocalTimerServiceHome localTimerServiceHome = (LocalTimerServiceHome) initial.lookup("java:comp/env/ejb/LocalTimerServiceBean"); --- > > > //RSC wrong name used > //LocalTimerServiceHome localTimerServiceHome = (LocalTimerServiceHome) initial.lookup("java:comp/env/ejb/LocalTimerServiceBean"); > //See also change to jboss.xml to include TimerServiceBean or this fix wont work either. > LocalTimerServiceHome localTimerServiceHome = (LocalTimerServiceHome) initial.lookup("TimerServiceBean"); RCS file: /cvsroot/jbpm/jbpm.3/enterprise/src/main/resources/jar/META-INF/jboss.xml,v retrieving revision 1.2 diff -r1.2 jboss.xml 12a13,20 >  > <session> > <ejb-name>TimerServiceBean</ejb-name> > <jndi-name>ejb/TimerServiceBean</jndi-name> > <local-jndi-name>TimerServiceBean</local-jndi-name> > </session> > > -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3261) Serialization of EJB handles

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3261?page=all ] Dimitris Andreadis updated JBAS-3261: ------------------------------------- Fix Version/s: JBossAS-4.2.1.CR1 (was: JBossAS-4.2.0.CR1) > Serialization of EJB handles > ---------------------------- > > Key: JBAS-3261 > URL: http://jira.jboss.com/jira/browse/JBAS-3261 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB2 > Affects Versions: JBossAS-3.2.8.SP1, JBossAS-4.0.4.GA > Reporter: Lars Kral > Assigned To: Scott M Stark > Fix For: JBossAS-4.2.1.CR1 > > Attachments: test-ejb.jar > > > According to [JBAS-1620], we have to use org.jboss.naming.NamingContextFactory to allow the handle to remember the JNDI environment that was in effect when it was created. But what about handles constructed inside the JBoss server JVM and later serialized into the client JVM? Each JVM may use different properties to access the JNDI - e.g. the "java.naming.provider.url" property, which is not available in the JBoss JVM but is required in a client JVM. Sure, I can add the "java.naming.provider.url" property to the $JBOSS_SERVER_HOME/conf/jndi.properties file, but as far as I know this forces in-VM calls to use RMI. > Please have a look at the attached testcase (sources are included). The code works in our production environment (v3.2.7) but fails with the latest JBoss releases (4.0.4.GA and 3.2.8.SP1). > Regards, > lkral -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3253) jnps not maintaining the transport settings correctly

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3253?page=all ] Dimitris Andreadis updated JBAS-3253: ------------------------------------- Fix Version/s: JBossAS-4.2.1.CR1 (was: JBossAS-4.2.0.CR1) > jnps not maintaining the transport settings correctly > ----------------------------------------------------- > > Key: JBAS-3253 > URL: http://jira.jboss.com/jira/browse/JBAS-3253 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Naming > Affects Versions: JBossAS-4.0.4.GA > Reporter: Scott M Stark > Assigned To: Scott M Stark > Fix For: JBossAS-4.2.1.CR1 > > > There is a report that using a jnps configuration does not maintain the ssl and host settings correctly when interacting with context objects returned from the InitialContext. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2885) Need a JBossXB base XMBean schema and JBossXMBean implementation

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2885?page=all ] Dimitris Andreadis updated JBAS-2885: ------------------------------------- Fix Version/s: JBossAS-4.2.1.CR1 (was: JBossAS-4.2.0.CR1) > Need a JBossXB base XMBean schema and JBossXMBean implementation > ---------------------------------------------------------------- > > Key: JBAS-2885 > URL: http://jira.jboss.com/jira/browse/JBAS-2885 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMX > Affects Versions: JBossAS-4.0.3 SP1 > Reporter: Scott M Stark > Assigned To: Scott M Stark > Fix For: JBossAS-4.2.1.CR1 > > > I'm tired of the legacy, unextensible, non-object centric xmbean descriptor format and JBossXMBean implementation. We need a pojo container driven by an extensible jbossxb schema for better migration of components between the legacy jmx based kernels and the pojo micrcontainer based kernels. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1486) Allow for deployments without an explicit suffix

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1486?page=all ] Dimitris Andreadis updated JBAS-1486: ------------------------------------- Fix Version/s: JBossAS-4.2.1.CR1 (was: JBossAS-4.2.0.CR1) > Allow for deployments without an explicit suffix > ------------------------------------------------ > > Key: JBAS-1486 > URL: http://jira.jboss.com/jira/browse/JBAS-1486 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMX, Deployment services > Affects Versions: JBossAS-4.0.1 Final, JBossAS-3.2.7 Final, JBossAS-4.0.1 SP1 > Reporter: Scott M Stark > Assigned To: Scott M Stark > Fix For: JBossAS-4.2.1.CR1 > > > A not uncommon request is to allow for deployments that do not have a qualifying suffix, for example, myejb/ instead of myejb.jar/, mywebapp instead of mywebapp.war > Most deployers require both a sepcific suffix and the correct deployment descriptor to exist in order to accept the deployment. We should look into supporting such deployments. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3275) Can't chain ldap login modules together using useFirstPass=password-stacking

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3275?page=all ] Dimitris Andreadis updated JBAS-3275: ------------------------------------- Fix Version/s: JBossAS-4.2.1.CR1 (was: JBossAS-4.2.0.CR1) > Can't chain ldap login modules together using useFirstPass=password-stacking > ---------------------------------------------------------------------------- > > Key: JBAS-3275 > URL: http://jira.jboss.com/jira/browse/JBAS-3275 > 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.2.1.CR1 > > > The way roles are pulled in from the authentication phase validatePassword callback precludes chaining of ldap login modules. If one server does authentication and another authorization this cannot be configured to work currently. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3729) Add alternate run-as mappings for container callbacks

by Scott M Stark (JIRA)

Add alternate run-as mappings for container callbacks ----------------------------------------------------- Key: JBAS-3729 URL: http://jira.jboss.com/jira/browse/JBAS-3729 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: EJB2, EJB3, Security, Web (Tomcat) service Affects Versions: JBossAS-4.0.4.GA Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-4.0.6.CR1 Other app servers support anlternate run-as semantics from the container init/destroy lifecycle callbacks. Weblogic for example: http://e-docs.bea.com/wls/docs81/webapp/weblogic_xml.html#1041058 This is an equivalent of <run-as> for init method for servlets. For example: <init-as> <servlet-name>FooServlet</servlet-name> <principal-name>joe</principal-name> </init-as> <destroy-as> <servlet-name>BarServlet</servlet-name> <principal-name>bob</principal-name> </destroy-as> This would allow more control over how these methods interact with secured resources. Similar options could be added for ejb lifecycle methods as well. -- 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

19 years, 3 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBAS-1490) EJB component environment (ENC) is not read only

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1490?page=all ] Dimitris Andreadis updated JBAS-1490: ------------------------------------- Fix Version/s: JBossAS-4.2.1.CR1 (was: JBossAS-4.2.0.CR1) > EJB component environment (ENC) is not read only > ------------------------------------------------ > > Key: JBAS-1490 > URL: http://jira.jboss.com/jira/browse/JBAS-1490 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB2 > Affects Versions: JBossAS-3.2.6 Final > Environment: Windows XP > Reporter: Tim Fox > Assigned To: Scott M Stark > Fix For: JBossAS-4.2.1.CR1 > > > The component JNDI environment for a Stateless session bean does not appear to be read-only. > I have a SLSB running in 3.2.6. > It attempts to modify it's ENC (java:comp/env environment) and succeeds. I.e. the following succeeds: > InitialContext ic = new InitialContext(); > Context envCtx = (Context)new InitialContext().lookup("java:comp/env"); > envCtx.bind("foo", "bar"); > log.debug("Worked!!"); > Also bind stuff into the context works. > I haven't tried with other types of EJB. > According to the EJB 2.0 spec (Sec. 20.2.4) an enterprise beans's environment should be read-only. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3353) Add support for jmx-depends to mc bean deployer

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3353?page=all ] Dimitris Andreadis updated JBAS-3353: ------------------------------------- Fix Version/s: JBossAS-4.2.1.CR1 (was: JBossAS-4.2.0.CR1) > Add support for jmx-depends to mc bean deployer > ----------------------------------------------- > > Key: JBAS-3353 > URL: http://jira.jboss.com/jira/browse/JBAS-3353 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMX, MicroContainer bus > Affects Versions: JBossAS-4.0.4.GA > Reporter: Scott M Stark > Assigned To: Scott M Stark > Fix For: JBossAS-4.2.1.CR1 > > > There is a mismatch in terms of dependencies between the mc beans and the legacy jmx beans that affect integration of the bean deployer in jboss-4.0.x. It should be possible to extend the org.jboss.kernel.plugins.deployment.xml.BeanSchemaBinding to add a jmx-depends tag that specifies the jmx mbeans that the org.jboss.kernel.deployment.jboss.JBossBeanDeployment which is registered with the jmx kernel depends on. -- 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

19 years, 3 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-jira February 2007