October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-1128) Add a full component-info.xml to source tree

by Brian Stansberry (JIRA)

Add a full component-info.xml to source tree -------------------------------------------- Key: JBCACHE-1128 URL: http://jira.jboss.com/jira/browse/JBCACHE-1128 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: 2.0.0.GA The component-info.xml that goes into repository.jboss.org should be coming from the JBC source tree. -- 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

18 years, 4 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1738) can not access a member of class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag

by David Schlechtweg (JIRA)

can not access a member of class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag ------------------------------------------------------------------------------------------- Key: JBPORTAL-1738 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1738 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.6.2 Final Reporter: David Schlechtweg Assigned To: Julien Viet Hi, i get a IllegalAccessException when i use a jsp tag in freemarker: <#assign portlet=JspTaglibs["http://java.sun.com/portlet"]> <#import "/spring.ftl" as spring /> <@portlet.actionURL var="postURL"> <@portlet.param name="action" value="newQuery" /> </(a)portlet.actionURL> I use freemarker 2.3.10 in jboss-portal-2.6.2.GA java.lang.IllegalAccessException: Class freemarker.ext.jsp.TagTransformModel can not access a member of class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag with modifiers "public" The problematic instruction: ---------- ==> user-directive portlet.actionURL [on line 3, column 1 in template/search/simple/view.ftl] ---------- Java backtrace for programmers: ---------- freemarker.template.TemplateModelException: java.lang.IllegalAccessException: Class freemarker.ext.jsp.TagTransformModel can not access a member of class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag with modifiers "public" at freemarker.ext.jsp.TagTransformModel.getWriter(TagTransformModel.java:177) at freemarker.core.Environment.visit(Environment.java:220) at freemarker.core.UnifiedCall.accept(UnifiedCall.java:116) at freemarker.core.Environment.visit(Environment.java:196) at freemarker.core.MixedContent.accept(MixedContent.java:92) at freemarker.core.Environment.visit(Environment.java:196) at freemarker.core.Environment.process(Environment.java:176) at freemarker.template.Template.process(Template.java:232) at org.springframework.web.servlet.view.freemarker.FreeMarkerView.processTemplate(FreeMarkerView.java:344) any ideas? My hunch is that the class org.jboss.portal.portlet.impl.jsr168.taglib.GenerateURLTag is not public, and you're trying to invoke a method on it that though itself is public, it is not declared in any public superclass of GenerateURLTag, or public interface that GenerateURLTag implements. -- 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

18 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-152) Dependency names need to be validated earlier

by Scott M Stark (JIRA)

Dependency names need to be validated earlier --------------------------------------------- Key: JBMICROCONT-152 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-152 Project: JBoss MicroContainer Issue Type: Bug Components: Dependency Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossMC_2_0_0 Beta3 I'm seeing an error like the following testing profileservice attachments overrides: Caused by: java.lang.IllegalArgumentException: Null name at org.jboss.dependency.plugins.AbstractController.getContext(AbstractController.java:129) at org.jboss.kernel.plugins.dependency.AbstractKernelController.getContext(AbstractKernelController.java:101) at org.jboss.dependency.plugins.AbstractDependencyItem.resolve(AbstractDependencyItem.java:117) at org.jboss.dependency.plugins.AbstractDependencyInfo.resolveDependencies(AbstractDependencyInfo.java:128) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:595) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:531) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:289) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:192) at org.jboss.system.ServiceController.doInstall(ServiceController.java:638) at org.jboss.system.ServiceController.install(ServiceController.java:271) This error regarding the invalid dependency item name not showing up until there is an attempt to resolve it makes it impossible to debug the problem as there is no context in the dependency to understand why its null. -- 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

18 years, 4 months

3
11
0 / 0

[JBoss JIRA] Created: (JBOSGI-10) OSGi Listeners

by Adrian Brock (JIRA)

OSGi Listeners -------------- Key: JBOSGI-10 URL: http://jira.jboss.com/jira/browse/JBOSGI-10 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Adrian Brock Assigned To: Adrian Brock OSGi defines three types of listeners 1) Framework listener for global events related to the server 2) Bundle listener for events related to the deployments 3) Service listener for events related services Where these already exist, these need to be "adapted" to the OSGi api. The missing notifications need to be implemented. -- 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

18 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-4) Deployer changes for OSGi

by Adrian Brock (JIRA)

Deployer changes for OSGi ------------------------- Key: JBOSGI-4 URL: http://jira.jboss.com/jira/browse/JBOSGI-4 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Adrian Brock Assigned To: Adrian Brock This is a holder task for the Deployer changes need to make OSGi work and integrate OSGi bundles with other JBoss deployments (and vice versa). -- 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

18 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-7) OSGi ClassLoader

by Adrian Brock (JIRA)

OSGi ClassLoader ---------------- Key: JBOSGI-7 URL: http://jira.jboss.com/jira/browse/JBOSGI-7 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Adrian Brock Assigned To: Adrian Brock Implementation of the OSGi classloader. This should be usable for both OSGi bundles and all other JBoss deployments. An new classloader.xml will be supported such that non OSGi deployments can specify their classloading constraints (import, export, etc.) Additionally, it should provide support for things outside the OSGi spec that are required in JavaEE or for backwards compatibility like scoping and j2se classloading compliance. -- 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

18 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-15) Create a concrete subclass of the VFSClassLoaderPolicy that has injectable policy

by Adrian Brock (JIRA)

Create a concrete subclass of the VFSClassLoaderPolicy that has injectable policy --------------------------------------------------------------------------------- Key: JBOSGI-15 URL: http://jira.jboss.com/jira/browse/JBOSGI-15 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Other Reporter: Adrian Brock Assigned To: Adrian Brock Once the VFSClassLoader is done JBOSGI-14, we need to create a concrete subclass that allows injectable policy. i.e. setters. This will be used by the both JBossAS and OSGi through the Deployer layer to construct classloaders from the classloading dependencies/rules they define. -- 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

18 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-189) Make DeploymentContext totally invisible

by Adrian Brock (JIRA)

Make DeploymentContext totally invisible ---------------------------------------- Key: JBMICROCONT-189 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-189 Project: JBoss MicroContainer Issue Type: Task Components: Deployment Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC-2.0.0.GA The DeploymentContext should be totally invisble (possible still exposed for testing/debugging purposes as a deprecated method on the main deployer?) There's still a number of places where it is showing up. See the attached forum thread for a discussion. -- 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

18 years, 4 months

1
3
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-201) Create a generic describing deployer for dependencies

by Adrian Brock (JIRA)

Create a generic describing deployer for dependencies ----------------------------------------------------- Key: JBMICROCONT-201 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-201 Project: JBoss MicroContainer Issue Type: Sub-task Components: Deployment Reporter: Adrian Brock There should be a generic describing stage deployer that looks at all the metadata and creates dependencies from it, either via an interface implemented by the metadata or a annotation on the metadata describing an adapter/factory. -- 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

18 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-203) Analyze microcontainer dependencies

by Paul Gier (JIRA)

Analyze microcontainer dependencies ----------------------------------- Key: JBMICROCONT-203 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-203 Project: JBoss MicroContainer Issue Type: Task Components: General Reporter: Paul Gier Assigned To: Paul Gier Fix For: JBossMC-2.0.0.CR1 Using the mvn dependency plugin "mvn dependency:analyze", I noticed that several of the microcontainer modules are using transitive dependencies directly and/or are listing dependencies that aren't used. This dependency tool should be used to clean up these dependencies a bit to make it more clear which ones are required for compilation. -- 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

18 years, 4 months

2
1
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 2007