September 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-1244) Discovery: set max_rank dynamically

by Bela Ban (JIRA)

Discovery: set max_rank dynamically ----------------------------------- Key: JGRP-1244 URL: https://jira.jboss.org/browse/JGRP-1244 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Priority: Minor Fix For: 2.11 Determine the best value for max_rank dynamically if ergonomics=true -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2041) Refactor the concurrency module into a component

by jaikiran pai (JIRA)

Refactor the concurrency module into a component ------------------------------------------------ Key: EJBTHREE-2041 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2041 Project: EJB 3.0 Issue Type: Task Components: concurrency Reporter: jaikiran pai Assignee: jaikiran pai The concurrency module currently consists of a EJBReadWriteLock and AOP based interceptors. The AOP interceptors need to be split out into a separate module. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-8480) Maven jboss-as-client POM gives Build Error

by Steve Schols (JIRA)

Maven jboss-as-client POM gives Build Error ------------------------------------------- Key: JBAS-8480 URL: https://jira.jboss.org/browse/JBAS-8480 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: 6.0.0.M5 Environment: Windows XP Professional SP3, Java SE 6 SDK, Eclipse 3.6 Helios, Maven 2.1.0 Reporter: Steve Schols I have a build problem with a Maven Eclipse project to generate the Eclipse classpath when using jboss-as-client-6.0.0.20100911-M5 as a dependency in my POM. I am building some demo applications as small proof of concepts. I was trying to migrate one of the demo applications from "Spring / JPA 2" to "EJB 3 / JPA 2". The "Spring / JPA 2" application could be tested standalone, but the "EJB 3 / JPA 2" application needs to be deployed in a JBoss environment that supports EJB 3 and JPA 2. I downloaded JBoss AS 6.0.0.20100911-M5 for this. To test my application, I wrote a small testcase somewhat similar to the workbook examples of the O'Reilly Enterprise JavaBeans 3.0, 5th Edition book. In the testcase I refer to the InitialContext to get a reference to a remote session bean to be able to use that as a service in my test. I have jndi.properties on the classpath with the correct properties set in the file to be able to access the JBoss AS and remote session bean like it's being used in the O'Reilly workbook client examples. I was getting NoClassDefFoundErrors of org.jnp.naming classes. When I added jnp-client to the classpath as a Maven dependency in the POM, I started getting ClassCastExceptions. The class "Reference" couldn't be cast to my own Service interface class. When searching on the Internet I found solutions that regarded adding jbossalll-client.jar on the classpath. I didn't want to add jbossall-client or the JBoss AS Server Runtime manually in Eclipse. I wanted it to be generated by the Maven POM dependencies. Otherwise I would lose the JBoss AS Server Runtime everytime I re-generated the Eclipse classpath with Maven. I found on the Internet that do to this, you should add "jboss-as-client.jar" as a dependency in your POM and it should be the exact same version as the application server. In this case it is jboss-6.0.0.20100911-M5. Luckily I found the correct version of the jboss-as-client dependency of version 6.0.0.20100911-M5 on the JBoss Nexus Maven Repository. <dependency> <groupId>org.jboss.jbossas</groupId> <artifactId>jboss-as-client</artifactId> <version>6.0.0.20100911-M5</version> </dependency> But When I execute the command "mvn eclipse:clean eclipse:eclipse", after downloading a lot of dependencies I get the following error: Downloading: http://jpp.realdolmen.com/nexus/content/groups/public//org/jboss/scanning... [INFO] Unable to find resource 'org.jboss.scanning:scanning-build:pom:1.0.0.Alpha6' in repository central (http://repo1.maven.org/maven2) [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error building POM (may not be this project's POM). Project ID: null:scanning-plugins:jar:null Reason: Cannot find parent: org.jboss.scanning:scanning-build for project: null:scanning-plugins:jar:null for project null:scanning-plugins:jar:null I think something is wrong in one of the POM's that is refered to in the jboss-as-client POM. I'm blocked at the moment to continue my migration, because adding the JBoss 6.0 M5 AS Server Runtime manually to the Eclipse classpath leads to an error when trying to run the testcase. I get the following error of Eclipse itself: CreateProcess error=87, the parameter is incorrect This is apparently due to the fact that the classpath has gotten to long to be able to pass it to the javaw.exe process. http://eclipsecoding.wikidot.com/faq#launchError I don't know which separate JAR's need to be added to the classpath other than jnp-client to the classpath, so I would like to be able to work with the jboss-as-client dependency. When running the O'Reilly EJB3 Workbook examples, with (in this case) The JBoss 4.2.3.GA Server Runtime added manually to the classpath, the client code works perfectly has access to the InitialContext and can cast the Reference objects to specific application classes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
5
0 / 0

[JBoss JIRA] Updated: (JBAS-8483) errors injecting the Weld BeanManager.

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8483?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated JBAS-8483: ---------------------------- Component/s: Weld/CDI > errors injecting the Weld BeanManager. > -------------------------------------- > > Key: JBAS-8483 > URL: https://jira.jboss.org/browse/JBAS-8483 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld/CDI > Affects Versions: 6.0.0.M5 > Environment: jboss as 6 milestone 5 > Reporter: nimo stephan > > The same weld-war does work in jboss as 6 milestone 4. Deploying it in jboss as 6 milestone 5 does work, only when invoking a bean, then weld throws exception: > (The full stacktrace can be seen here: http://community.jboss.org/thread/157055) > 10:57:33,719 SEVERITY [javax.enterprise.resource.webcontainer.jsf.application] javax.ejb.EJBException: java.lang.RuntimeException: Unable to inject jndi dependency: env/org.jboss.weld.integration.ejb.SessionBeanInterceptor/beanManager into property org.jboss.weld.integration.ejb.SessionBeanInterceptor.beanManager: MyWAR not bound: javax.faces.el.EvaluationException: javax.ejb.EJBException: java.lang.RuntimeException: Unable to inject jndi dependency: env/org.jboss.weld.integration.ejb.SessionBeanInterceptor/beanManager into property org.jboss.weld.integration.ejb.SessionBeanInterceptor.beanManager: MyWAR not bound > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [:2.0.2-FCS] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Moved: (JBAS-8483) errors injecting the Weld BeanManager.

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8483?page=com.atlassian.jira.plugin.sy... ] Pete Muir moved WELD-700 to JBAS-8483: -------------------------------------- Project: JBoss Application Server (was: Weld) Key: JBAS-8483 (was: WELD-700) Affects Version/s: 6.0.0.M5 (was: 1.1.0.Beta1) Security: Public > errors injecting the Weld BeanManager. > -------------------------------------- > > Key: JBAS-8483 > URL: https://jira.jboss.org/browse/JBAS-8483 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld/CDI > Affects Versions: 6.0.0.M5 > Environment: jboss as 6 milestone 5 > Reporter: nimo stephan > > The same weld-war does work in jboss as 6 milestone 4. Deploying it in jboss as 6 milestone 5 does work, only when invoking a bean, then weld throws exception: > (The full stacktrace can be seen here: http://community.jboss.org/thread/157055) > 10:57:33,719 SEVERITY [javax.enterprise.resource.webcontainer.jsf.application] javax.ejb.EJBException: java.lang.RuntimeException: Unable to inject jndi dependency: env/org.jboss.weld.integration.ejb.SessionBeanInterceptor/beanManager into property org.jboss.weld.integration.ejb.SessionBeanInterceptor.beanManager: MyWAR not bound: javax.faces.el.EvaluationException: javax.ejb.EJBException: java.lang.RuntimeException: Unable to inject jndi dependency: env/org.jboss.weld.integration.ejb.SessionBeanInterceptor/beanManager into property org.jboss.weld.integration.ejb.SessionBeanInterceptor.beanManager: MyWAR not bound > at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102) [:2.0.2-FCS] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2019) Refactor java:comp

by Carlo de Wolf (JIRA)

Refactor java:comp ------------------ Key: EJBTHREE-2019 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2019 Project: EJB 3.0 Issue Type: Task Reporter: Carlo de Wolf Fix For: EJB 3.1 The container should no longer be responsible for creating java:comp, but should use the java:comp created by the namespace deployers. (This is to allow a shared java:comp in web deployments and have other services augment a java:comp space.) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-535) Release PicketBox 4.0.0.alpha1

by Stefan Guilhen (JIRA)

Release PicketBox 4.0.0.alpha1 ------------------------------ Key: SECURITY-535 URL: https://jira.jboss.org/browse/SECURITY-535 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Reporter: Stefan Guilhen Assignee: Stefan Guilhen Cut the first release of PB v4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2715) Ability to add AgendaFilter to a stateless session

by Arnaud Simon (JIRA)

Ability to add AgendaFilter to a stateless session --------------------------------------------------- Key: JBRULES-2715 URL: https://jira.jboss.org/browse/JBRULES-2715 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-api Affects Versions: 5.1.1.FINAL Reporter: Arnaud Simon Assignee: Mark Proctor It is currently not possible to use AgendaFilter with a stateless session. It would be nice if the stateless session execute method would also be able to take in the agendafilter argument just like fireAllRules does. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (JGRP-1242) ENCRYPT: encrypt_entire_message doesn't encrypt when msg.length == 0

by Bela Ban (JIRA)

ENCRYPT: encrypt_entire_message doesn't encrypt when msg.length == 0 -------------------------------------------------------------------- Key: JGRP-1242 URL: https://jira.jboss.org/browse/JGRP-1242 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.11 ENCRYPT.encrypt_entire_message checks (in sendDown()) whether msg.length == 0 and - if true - passes the message *unencrypted* down. However, for example a JOIN_REQ in AUTH should get encrypted ! SOLUTION: change (in down() and up()) the check for msg.length == 0 to msg.length == 0 && !encrypt_entire_message -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBWEB-181) Allow rewriting URLs for other contexts

by Mike Millson (JIRA)

Allow rewriting URLs for other contexts --------------------------------------- Key: JBWEB-181 URL: https://jira.jboss.org/browse/JBWEB-181 Project: JBoss Web Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Affects Versions: JBossWeb-2.1.7.GA Reporter: Mike Millson Assignee: Remy Maucherat Line 1537 of o.a.c.c.Response.doIsEncodeable()[1] checks that the URL context matches the webapp context: if ((file == null) || !file.startsWith(contextPath)) return (false); There are use cases where a URL would need to be rewritten but not be the same context as the webapp. In addition, Weblogic apparently does not make this check, so it is an issue migrating from Weblogic. Can we remove this check, or add a flag where it can be configured to be removed? [1]http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossweb/branches/2.1.x/java... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2010