October 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-8506) Upgrade JBossWS to 3.4.0.CR1

by Alessio Soldano (JIRA)

Upgrade JBossWS to 3.4.0.CR1 ---------------------------- Key: JBAS-8506 URL: https://jira.jboss.org/browse/JBAS-8506 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Web Services Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: 6.0.0.CR1 Move to JBossWS-CXF 3.4.0.CR1. This includes upgrades of all the other ws components to CR1, plus move to Apache CXF 2.3.0 and synch of remaining javaee api jars (the jaxrpc one for instance still needs to be updated) -- 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2181) EJBBinder doesn't bind to the additional JNDI name in the presence of just a single view for EJB

by jaikiran pai (JIRA)

EJBBinder doesn't bind to the additional JNDI name in the presence of just a single view for EJB ------------------------------------------------------------------------------------------------ Key: EJBTHREE-2181 URL: https://jira.jboss.org/browse/EJBTHREE-2181 Project: EJB 3.0 Issue Type: Bug Components: jndi Reporter: jaikiran pai Assignee: jaikiran pai The EJB3.1 spec (section 4.4.1) says this: In addition to the previous requirements, if the bean exposes only one of the applicable client interfaces(or alternatively has only a no-interface view), the container registers an entry for that view with the following syntax : java:global[/<app-name>]/<module-name>/<bean-name> The container is also required to make session bean JNDI names available through the java:app and java:module namespaces. The EJBBinder currently doesn't bind to this additional JNDI name. -- 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2086) Missing interpretation of EJB-Annotation results in wrong call of dynamic method

by Tobias Grundmann (JIRA)

Missing interpretation of EJB-Annotation results in wrong call of dynamic method --------------------------------------------------------------------------------- Key: EJBTHREE-2086 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2086 Project: EJB 3.0 Issue Type: Bug Components: ejb3 Affects Versions: trunk Environment: java version "1.6.0_18" Reporter: Tobias Grundmann when looking up a method for invocation in StatefulContainer.dynamicInvoke():522 jboss tries to determine if it's an EJB-Object-Method via SessionSpecContainer.isEjBObjectMethod(). This results wrongly in "false" if the class in question doesn't implement EJBObject but has e.g. a @Stateful annotation. Futher the method EJBContainer.getNonBridgeMethod() seems to be rather optimistic in trying to find the correct method only according to the number of parameters. This was tested with jboss-6.0.0.M1, but the corresponding code in trunk seems to be the same. -- 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

15 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBCOMMON-108) CVE-2009-2693

by Mike Millson (JIRA)

CVE-2009-2693 ------------- Key: JBCOMMON-108 URL: https://jira.jboss.org/jira/browse/JBCOMMON-108 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: common-old (1.x) Affects Versions: 1.2.1.GA, 1.0.0.GA Reporter: Mike Millson CVE-2009-2693: When deploying WAR files, the WAR files were not checked for directory traversal attempts. This allows an attacker to create arbitrary content outside of the web root by including entries such as ../../bin/catalina.sh in the WAR. -- 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

15 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-983) @EJB injection fails, RuntimeException, IllegalArgumentException

by dpocock (JIRA)

@EJB injection fails, RuntimeException, IllegalArgumentException ---------------------------------------------------------------- Key: EJBTHREE-983 URL: http://jira.jboss.com/jira/browse/EJBTHREE-983 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: AS 4.2.0 GA, EJB 3.0 RC9 - Patch 1 Environment: Debian Linux, Sun Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Reporter: dpocock Similar to bug EJBTHREE-862. However, setting `Isolated' to false in $JBOSS_HOME/server/XXX/deploy/ear-deployer.xml does not resolve the issue for me. Here is the scenario: There are two applications, app1.ear and app2.ear. app1.ear contains a stateless session bean, App1Bean, with local and remote interface app2.ear contains a stateless session bean, App2Bean, which has a field defined like so: @EJB(mappedName="app1/App1Bean/local") // I've tried local and remote com.app1.ejb.session.App1 app1; app1.ear and app2.ear are loaded successfully by the application server. When App2Bean is activated, JBoss tries to perform the injections. At this point, the RuntimeException (see stack below) occurs. App2Bean can successfully obtain a reference to app1 bean using the traditional JNDI lookup methods. This is a workaround. When inspecting the stack, notice the presence of IllegalArgumentException, even though the interface matches. 16:22:12,155 ERROR [STDERR] java.lang.RuntimeException: Non matching type for inject of field: App1Bean app1 for type: $Proxy79 of jndiName env/App2Bean/app2 intfs: , App1, org.jboss.ejb3.JBossProxy, javax.ejb.EJBObject 16:22:12,155 ERROR [STDERR] at org.jboss.injection.JndiFieldInjector.inject(JndiFieldInjector.java:135) 16:22:12,155 ERROR [STDERR] at org.jboss.injection.JndiFieldInjector.inject(JndiFieldInjector.java:104) 16:22:12,155 ERROR [STDERR] at org.jboss.injection.JndiFieldInjector.inject(JndiFieldInjector.java:61) 16:22:12,155 ERROR [STDERR] at org.jboss.ejb3.AbstractPool.create(AbstractPool.java:92) 16:22:12,155 ERROR [STDERR] at org.jboss.ejb3.ThreadlocalPool.get(ThreadlocalPool.java:48) 16:22:12,165 ERROR [STDERR] at org.jboss.ejb3.cache.simple.SimpleStatefulCache.create(SimpleStatefulCache.java:209) 16:22:12,165 ERROR [STDERR] at org.jboss.ejb3.stateful.StatefulContainer.dynamicInvoke(StatefulContainer.java:303) 16:22:12,165 ERROR [STDERR] at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) 16:22:12,165 ERROR [STDERR] at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) 16:22:12,175 ERROR [STDERR] at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:828) 16:22:12,175 ERROR [STDERR] at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:681) 16:22:12,175 ERROR [STDERR] at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:358) 16:22:12,175 ERROR [STDERR] at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:412) 16:22:12,175 ERROR [STDERR] at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:239) 16:22:12,185 ERROR [STDERR] Caused by: java.lang.IllegalArgumentException 16:22:12,185 ERROR [STDERR] at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:63) 16:22:12,185 ERROR [STDERR] at java.lang.reflect.Field.set(Field.java:656) 16:22:12,185 ERROR [STDERR] at org.jboss.injection.JndiFieldInjector.inject(JndiFieldInjector.java:119) 16:22:12,185 ERROR [STDERR] ... 13 more -- 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

15 years, 7 months

5
5
0 / 0

[JBoss JIRA] Resolved: (JBAS-8304) Use shared library mode in JBoss AS

by Marius Bogoevici (JIRA)

[ https://jira.jboss.org/browse/JBAS-8304?page=com.atlassian.jira.plugin.sy... ] Marius Bogoevici resolved JBAS-8304. ------------------------------------ Resolution: Done > Use shared library mode in JBoss AS > ----------------------------------- > > Key: JBAS-8304 > URL: https://jira.jboss.org/browse/JBAS-8304 > Project: JBoss Application Server > Issue Type: Feature Request > Components: Weld/CDI > Reporter: Pete Muir > Assignee: Marius Bogoevici > Priority: Critical > Fix For: 6.0.0.CR1 > > -- 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

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2170) no-interface view doesn't pass on the invoked business interface to Endpoint

by jaikiran pai (JIRA)

no-interface view doesn't pass on the invoked business interface to Endpoint ---------------------------------------------------------------------------- Key: EJBTHREE-2170 URL: https://jira.jboss.org/browse/EJBTHREE-2170 Project: EJB 3.0 Issue Type: Bug Components: nointerface Affects Versions: depchain-1.0.0-alpha-4 Reporter: jaikiran pai Assignee: jaikiran pai The NoInterfaceViewInvocationHandler passes null as the invoked business interface to the Endpoint: // finally pass-on the control to the endpoint return endpoint.invoke(this.session, null, method, args); Instead, it should be passing the no-interface view type http://download.oracle.com/javaee/6/api/javax/ejb/SessionContext.html#get... -- 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2485) Search on the page Editor

by Jim Tyrrell (JIRA)

Search on the page Editor ------------------------- Key: JBPORTAL-2485 URL: https://jira.jboss.org/browse/JBPORTAL-2485 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: All Reporter: Jim Tyrrell Attachments: Screen shot 2010-10-12 at 9.13.06 AM.png It would be nice if the Page Editor had a box in it to do a search to bring up only the items matching the string instead of having to hunt through each of the various buckets that hold portlets. As more and more things get added this list would become huge. See the attached screen shot to see what dialogue I am talking about. -- 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

15 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8448) Update parsing code to generate domain updates instead of models directly

by Jason Greene (JIRA)

Update parsing code to generate domain updates instead of models directly ------------------------------------------------------------------------- Key: JBAS-8448 URL: https://jira.jboss.org/browse/JBAS-8448 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Jason Greene -- 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

15 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2731) Guvnor web guided decision table: sorting on integer and date fields should sort correctly

by Geoffrey De Smet (JIRA)

Guvnor web guided decision table: sorting on integer and date fields should sort correctly ------------------------------------------------------------------------------------------ Key: JBRULES-2731 URL: https://jira.jboss.org/browse/JBRULES-2731 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-guvnor Affects Versions: 5.1.1.FINAL Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Minor Fix For: FUTURE the row number apparently sorts correctly, but the others don't Problem is because org.drools.ide.common.client.modeldriven.dt.GuidedDecisionTable#data is a String[][] -- 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

15 years, 7 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 October 2010