August 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-744) AbstractAopMetaDataDeployer.FakeComponentUnit.getScope() does not create a new scope

by Kabir Khan (JIRA)

AbstractAopMetaDataDeployer.FakeComponentUnit.getScope() does not create a new scope ------------------------------------------------------------------------------------ Key: JBAOP-744 URL: https://jira.jboss.org/jira/browse/JBAOP-744 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 2.1.4.GA, 2.2.0.GA From: smarlow(a)redhat.com Subject: ScopeKey + AbstractAopMetaDataDeployer.FakeComponentUnit.getScope()... Date: 4 August 2009 02:07:52 BST To: kkhan(a)redhat.com Reply-To: smarlow(a)redhat.com Kabir, I am still getting up to speed on the mc internals and am looking at different uses of ScopeKey. I came across the following code fragment and wanted to ping you about it. For the case where the "scope" variable is null, I don't see where we are assigning "key" to "scope" and we would therefore return null to the caller (whom is probably expecting the new ScopeKey value). // org.jboss.aop.asintegration.jboss5.AbstractAopMetaDataDeployer.FakeComponentUnit ScopeKey getScope() { if (scope == null) { ScopeKey key = parent.getScope().clone(); key.removeScopeLevel(CommonLevels.INSTANCE); key.addScope(CommonLevels.INSTANCE, bmd.getName()); } return scope; } The JBoss AOP unit tests still succeed with a small code change to return the new ScopeKey instead of null. Scott -- 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

16 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-7155) Confusing typo in documentation

by Peter HagstrÃ¶m (JIRA)

Confusing typo in documentation ------------------------------- Key: JBAS-7155 URL: https://jira.jboss.org/jira/browse/JBAS-7155 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Docs/Installation and Getting Started Guide Reporter: Peter HagstrÃ¶m Priority: Trivial In section "9.5. Hot-deployment of services in JBoss" we are told to take a look in the "server/production/deploy" directory. Should this not be "server/default/deploy"? -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7151) Minor typo in documentation

by Peter HagstrÃ¶m (JIRA)

Minor typo in documentation --------------------------- Key: JBAS-7151 URL: https://jira.jboss.org/jira/browse/JBAS-7151 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Docs/Installation and Getting Started Guide Reporter: Peter HagstrÃ¶m Priority: Trivial The listing of components in paragraph "1.3. Major Component Upgrades" lists "JGroups v.2.6.7.GA" twice. -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7150) Failed to connect to iiop:1099

by Ramesh Jamana (JIRA)

Failed to connect to iiop:1099 ------------------------------ Key: JBAS-7150 URL: https://jira.jboss.org/jira/browse/JBAS-7150 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Environment: WINDOWS XP Reporter: Ramesh Jamana Hi, I am new to JBOSS. And planning to migrate from websphere to JBOSS. I am getting the following exception while running the application. javax.naming.CommunicationException: Failed to connect to server iiop:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server iiop:1099 [Root exception is java.net.UnknownHostException: iiop: iiop]] at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:254) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1370) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:579) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.apache.jsp.executeBuildNavdb_jsp._jspService(org.apache.jsp.executeBuildNavdb_jsp:510) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:153) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:534) Please help me. Thanks, Ramesh -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2436) JBPC 2.0 : ResourceResponse.setCharacterEncoding always throws UnsupportedOperationException

by Bernard de Terwangne (JIRA)

JBPC 2.0 : ResourceResponse.setCharacterEncoding always throws UnsupportedOperationException -------------------------------------------------------------------------------------------- Key: JBPORTAL-2436 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2436 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: Portlet-2.0 Environment: Any Reporter: Bernard de Terwangne package org.jboss.portal.portlet.impl.jsr168.api; ... public class ResourceResponseImpl extends MimeResponseImpl implements ResourceResponse { ... public void setLocale(Locale locale) { throw new UnsupportedOperationException(); } public void setCharacterEncoding(String s) { throw new UnsupportedOperationException(); } public void setContentLength(int i) { throw new UnsupportedOperationException(); } ... } Problems come when you want to deploy your portlet on JBoss PortletContainer and on other portals. JSR-286 does not state that portals my throw UnsupportedOperationException. -- 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

16 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBID-155) Consolidated Build: Create IDM Dependency pack

by Anil Saldhana (JIRA)

Consolidated Build: Create IDM Dependency pack ----------------------------------------------- Key: JBID-155 URL: https://jira.jboss.org/jira/browse/JBID-155 Project: JBoss Identity Issue Type: Task Components: Community-Build Reporter: Anil Saldhana Assignee: Jeff Yu Jeff, we need to create a zip of IDM dependency pack just the way we do for OpenID. Please take a look at how we do it for openid in: https://svn.jboss.org/repos/jbossidentity/consolidated-build/trunk/ Just create a module such as jboss-identity-idm and have the assembly plugin build up the zip. -- 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

16 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2442) typeParameter constant in ActionURL286Tag and other *URL*Tag should be declared final

by Bernard de Terwangne (JIRA)

typeParameter constant in ActionURL286Tag and other *URL*Tag should be declared final ------------------------------------------------------------------------------------- Key: JBPORTAL-2442 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2442 Project: JBoss Portal Issue Type: Quality Risk Security Level: Public (Everyone can see) Environment: Any Reporter: Bernard de Terwangne Just for clarity and to prevent people from changing this static for any reason -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBID-158) IDFedLSInputResolver should have the ws-t schemas

by Anil Saldhana (JIRA)

IDFedLSInputResolver should have the ws-t schemas ------------------------------------------------- Key: JBID-158 URL: https://jira.jboss.org/jira/browse/JBID-158 Project: JBoss Identity Issue Type: Sub-task Components: Identity-Federation Affects Versions: IDENTITY-1.0.0.alpha5 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: IDFED-1.0.0.beta1 -- 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

16 years, 9 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBBUILD-158) Jar canonicalization and dependency isolation

by Paul Gier (JIRA)

[ https://jira.jboss.org/jira/browse/JBBUILD-158?page=com.atlassian.jira.pl... ] Paul Gier commented on JBBUILD-158: ----------------------------------- Scott, I think this issue has become out of date. I have cleaned up some of the unused dependencies in the process of refactoring the testsuite (JBBUILD-529). Probably what still needs to happen is to use "mvn dependency:analyze" in each module and find out where more improvements can be made. > Jar canonicalization and dependency isolation > --------------------------------------------- > > Key: JBBUILD-158 > URL: https://jira.jboss.org/jira/browse/JBBUILD-158 > Project: JBoss Build System > Issue Type: Feature Request > Components: Maven Builds > Reporter: Scott M Stark > Assignee: Paul Gier > Fix For: Maven Build - App Server (Phase 3) > > > We need to look at the jar hell issue we have in terms of uneccessary dependencies and exposure of neccessary dependencies as something other than an implementation detail. Two tools in this space we should look at are: > genjar (http://genjar.sourceforge.net/) and jarjar (http://jarjar.sourceforge.net/). -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBBUILD-502) Change the ant scripts to match the properties in libraries.ent

by Paul Gier (JIRA)

Change the ant scripts to match the properties in libraries.ent --------------------------------------------------------------- Key: JBBUILD-502 URL: https://jira.jboss.org/jira/browse/JBBUILD-502 Project: JBoss Build System Issue Type: Task Reporter: Paul Gier Assignee: Paul Gier Fix For: Maven Build - App Server (Phase 2) Currently the thirdparty pom has dependency mappings to give the maven dependencies the names that the ant build is expecting. Gradually these mappings should be removed as the ant build scripts are updated to point to the correct maven names. -- 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

16 years, 9 months

1
4
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 August 2009