March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1250) Optimize access to service description

by Chris Laprun (JIRA)

Optimize access to service description -------------------------------------- Key: JBPORTAL-1250 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1250 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.Alpha2 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6 Final Producer information code still tries to access service too many times. Should add a transaction-like concept during which the service description would stay valid since for a single operation it is currently possible to request the service description several times (when cache is not used)... -- 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

13 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1109) WSRP integration API

by Julien Viet (JIRA)

WSRP integration API -------------------- Key: JBPORTAL-1109 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1109 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.Alpha1 Reporter: Julien Viet Assigned To: Chris Laprun Fix For: 2.6.Alpha1 -- 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

13 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1106) Find a way to prevent re-generation of Service Description for each call

by Chris Laprun (JIRA)

Find a way to prevent re-generation of Service Description for each call ------------------------------------------------------------------------ Key: JBPORTAL-1106 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1106 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.DR1, 2.4 Final Reporter: Chris Laprun Assigned To: Chris Laprun Priority: Minor Fix For: 2.6.Alpha1 A way to do it would be to be able to listen to portlet deployment inside the server. This way, we could mark the service description as dirty when a new remotable portlet is deployed and only re-generate the service description when it is dirty. -- 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

13 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1016) Allow creation and deployment of WSRP portlets from descriptors

by Chris Laprun (JIRA)

Allow creation and deployment of WSRP portlets from descriptors --------------------------------------------------------------- Key: JBPORTAL-1016 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1016 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.4 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.4.1 Final Right now, the only way to deploy WSRP portlets is via the management portlet. We should be able to do this via the descriptors. Proposed solution is to evolve the -wsrp.xml file to accomodate portlet definition. -- 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

13 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1251) Tie clones to registration context

by Chris Laprun (JIRA)

Tie clones to registration context ---------------------------------- Key: JBPORTAL-1251 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1251 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.Alpha2 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.Beta1 -- 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

13 years, 6 months

2
11
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1252) Add releaseSessions support on Consumer

by Chris Laprun (JIRA)

Add releaseSessions support on Consumer --------------------------------------- Key: JBPORTAL-1252 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1252 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.6.Alpha2 Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.Beta1 -- 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

13 years, 6 months

2
10
0 / 0

[JBoss JIRA] Created: (JBAS-3970) NPE in JBossTestCase

by Thomas Diesler (JIRA)

NPE in JBossTestCase -------------------- Key: JBAS-3970 URL: http://jira.jboss.com/jira/browse/JBAS-3970 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Reporter: Thomas Diesler Assigned To: Scott M Stark getServerHost() throws a NPE, because the delegate is not initialized before setUp() is called public class SimpleJSETestCase extends JBossTestCase { private String WSDL_LOCATION = "http://" + getServerHost() + ":8080/ws4ee-simple?wsdl"; private String NAMESPACE = "http://test.jboss.org/ws4eesimple"; private QName SERVICE_NAME = new QName(NAMESPACE, "HelloService"); .... } This is quite common in the webservice test suite -- 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

13 years, 7 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-913) java.lang.IllegalStateException in SessionContext::getCallerPrincipal()

by Mihail Druzinin (JIRA)

java.lang.IllegalStateException in SessionContext::getCallerPrincipal() ----------------------------------------------------------------------- Key: EJBTHREE-913 URL: http://jira.jboss.com/jira/browse/EJBTHREE-913 Project: EJB 3.0 Issue Type: Bug Components: Security Affects Versions: EJB 3.0 RC9 - FD Environment: AS: jboss-4.0.5 (ejb3 Version EJB 3.0 RC7 - FD and EJB3 RC9 Patch 1) OS: Windows, GentooLinux Reporter: Mihail Druzinin >From HttpServlet I execute methods from stateless been. All methods executed correctly with authorization. When in method I try sessionContext.getCallerPrincipal(), then throws java.lang.IllegalStateException: No valid security context for the caller identity After see in jboss security module I find that in org.jboss.security.SecurityAssociation getCallerPrincipal() when used RunAsIdentity, it getted not from top of RunAsIdentity stack, but "for the active run-as the previous caller has assumed": Principal thePrincipal = peekRunAsIdentity(1); (SecurityAssociation.java:216). After fixed that string to: Principal thePrincipal = peekRunAsIdentity(0), all start work. -- 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

13 years, 7 months

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-754) isCallerInRole checks should go through JACC layer (if JACC is configured)

by Anil Saldhana (JIRA)

isCallerInRole checks should go through JACC layer (if JACC is configured) -------------------------------------------------------------------------- Key: EJBTHREE-754 URL: http://jira.jboss.com/jira/browse/EJBTHREE-754 Project: EJB 3.0 Issue Type: Task Components: Security Affects Versions: EJB 3.0 RC9 - FD Reporter: Anil Saldhana Assigned To: Scott M Stark Fix For: EJB 3.0 RC10 - FD Since Scott is going to review the ejb3 JACC implementation, I am assigning this issue to Scott. The EJBContext.isCallerInRole checks need to go through the jacc layer, if the user has configured jacc. I am not sure what the best way to tell the xxxContext layer to use jacc helper if user desires. Maybe a simple system property may do it. -- 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

13 years, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-772) Add JBoss EULA

by Rajesh Rajasekaran (JIRA)

Add JBoss EULA -------------- Key: EJBTHREE-772 URL: http://jira.jboss.com/jira/browse/EJBTHREE-772 Project: EJB 3.0 Issue Type: Task Reporter: Rajesh Rajasekaran Fix For: EJB 3.0 RC10 - FD Attachments: JBossORG-EULA.txt Attached is the JBossORG-EULA.txt 1. The eula should be checked into the project's source tree. 2. The project's build should include the EULA in project distributables, ie, whatever is the unit of publish: zip, tgz, etc. -- 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

13 years, 7 months

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2007