August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAOP-279) Weaving native methods

by Kabir Khan (JIRA)

Weaving native methods ---------------------- Key: JBAOP-279 URL: http://jira.jboss.com/jira/browse/JBAOP-279 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.5.0.GA Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.0 Unset NATIVE modifier in wrapper method -- 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

19 years, 11 months

1
4
0 / 0

[JBoss JIRA] Created: (JBRULES-404) make the rule node have a child node of type nt:file for documentation

by Michael Neale (JIRA)

make the rule node have a child node of type nt:file for documentation ---------------------------------------------------------------------- Key: JBRULES-404 URL: http://jira.jboss.com/jira/browse/JBRULES-404 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale Hmmm... not sure. Perhaps it should just be a text attribute of the rule node. -- 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

19 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3529) Add support for JBoss Serialization in JBossFaces (JSF)

by Stan Silvert (JIRA)

Add support for JBoss Serialization in JBossFaces (JSF) ------------------------------------------------------- Key: JBAS-3529 URL: http://jira.jboss.com/jira/browse/JBAS-3529 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta Reporter: Stan Silvert Assigned To: Stan Silvert Fix For: JBossAS-5.0.0.Beta Sun's JSF implementation now has the ability to specify a Serialization Provider. We need to allow the application developer to specify that he wants to use JBoss Serialization for client side state saving. -- 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

19 years, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-3390) Error starting up tomcat-ssl config on jboss-head testsuite module

by Rajesh Rajasekaran (JIRA)

Error starting up tomcat-ssl config on jboss-head testsuite module ------------------------------------------------------------------ Key: JBAS-3390 URL: http://jira.jboss.com/jira/browse/JBAS-3390 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-5.0.0.Beta Reporter: Rajesh Rajasekaran Fix For: JBossAS-5.0.0.Beta The "tomcat-ssl" configuration fails to start with the following error: 2006-07-13 06:11:48,320 INFO [org.apache.coyote.http11.Http11Protocol] Initializing Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080 2006-07-13 06:11:48,585 INFO [org.apache.coyote.http11.Http11Protocol] Initializing Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8443 2006-07-13 06:11:48,587 INFO [org.apache.coyote.http11.Http11Protocol] Initializing Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-9080 2006-07-13 06:11:48,598 ERROR [org.apache.coyote.http11.Http11Protocol] Error initializing endpoint java.io.IOException at org.apache.tomcat.util.net.jsse.JSSESocketFactory.init(JSSESocketFactory.java:393) at org.apache.tomcat.util.net.jsse.JSSESocketFactory.createSocket(JSSESocketFactory.java:134) at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:495) at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:160) at org.apache.catalina.connector.Connector.initialize(Connector.java:1016) at org.jboss.web.tomcat.tc6.StandardService.initialize(StandardService.java:688) at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:791) The error messages are enclosed in the following server log file. http://cruisecontrol.jboss.com/cc/artifacts/jboss-head-testsuite-1.5/2006... This can be verified by running the following target on the testsuite module. ant tomcat-ssl-tests http://cruisecontrol.jboss.com/cc/artifacts/jboss-head-testsuite-1.5/2006... -- 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

19 years, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-691) POJO MDB: Default message delivery is NON-PERSISTENT. Should be PERSISTENT

by fred chen (JIRA)

POJO MDB: Default message delivery is NON-PERSISTENT. Should be PERSISTENT -------------------------------------------------------------------------- Key: EJBTHREE-691 URL: http://jira.jboss.com/jira/browse/EJBTHREE-691 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: EJB 3.0 RC8 - FD Environment: Windows XP SP2, JBoss 4.0.4, EJB 3.0 RC8 Reporter: fred chen Priority: Trivial If a Producer class is not tagged with any @MessageProperties, the default delivery mode of the message is NON-PERSISTENT. According to documentation/tutorial, the default delivery mode should be PERSISTENT. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-690) POJO MDB: @MessageProperties tagged to Producer class ignored

by fred chen (JIRA)

POJO MDB: @MessageProperties tagged to Producer class ignored ------------------------------------------------------------- Key: EJBTHREE-690 URL: http://jira.jboss.com/jira/browse/EJBTHREE-690 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: EJB 3.0 RC8 - FD Environment: Windows XP Profession SP2, Jboss 4.0.4 with EJB 3.0 RC8 Reporter: fred chen Priority: Minor It appears the overrides specified in @MessageProperties tagged to a Producer class is being ignored. I assigned @MessageProperties ( delivery=DeliveryMode.PERSISTENT, timeToLive=0, priority=3 ) to a Producer class, however the actual message was delivered with priority 4, non-persistent. If I don't assign a @MessageProperties, the default delivery is NON-PERSISTENT and priority 4 as well (which is another bug imho, since the default behavior as documented should be PERSISTENT). @MessageProperties assigned to individual methods of a producer, however, appear to work correctly. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-938) "Default Context deos not exist" on MySQL5 deploy of 2.4.0.CR1

by Roy Russo (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-938?page=all ] Roy Russo resolved JBPORTAL-938. -------------------------------- Fix Version/s: 2.4 Final (was: 2.6 Final) Resolution: Done Use the JEMS isntaller for ejb3 installation, as per the new docs: http://docs.jboss.org/jbportal/v2.4/reference-guide/en/html/installation.... > "Default Context deos not exist" on MySQL5 deploy of 2.4.0.CR1 > -------------------------------------------------------------- > > Key: JBPORTAL-938 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-938 > Project: JBoss Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Fedora Core 5, JBoss 4.0.4.GA, JBoss Portal 2.4.0.CR1 > Reporter: Philipp Taprogge > Assigned To: Roy Russo > Fix For: 2.4 Final > > > When deploying JBoss Portal 2.4.0.CR1 on JBoss 4.0.4.GA and MySql 5.0.22 with the MySQL datasource, I find no errors in the server output. > I have appended the "jdbcCompliantTruncations=false" parameter to my connection URL. Deployment seems fine, but upon accessing the portal context, JBoss throws this: > java.lang.IllegalStateException: Default context does not exist > org.jboss.portal.core.model.portal.DefaultPortalCommandFactory.doMapping(DefaultPortalCommandFactory.java:71) > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > java.lang.reflect.Method.invoke(Method.java:585) > org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) > org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) > org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) > $Proxy54.doMapping(Unknown Source) > org.jboss.portal.core.CoreController.handle(CoreController.java:124) > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > java.lang.reflect.Method.invoke(Method.java:585) > org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) > org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) > org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) > org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) > org.jboss.mx.server.Invocation.invoke(Invocation.java:88) > org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) > org.jboss.mx.util.JMXInvocationHandler.invoke(JMXInvocationHandler.java:287) > $Proxy271.handle(Unknown Source) > org.jboss.portal.server.ServerInvocation.dispatch(ServerInvocation.java:79) > org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:140) > org.jboss.portal.server.aspects.server.NavigationInterceptor.invoke(NavigationInterceptor.java:64) > org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:37) > org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:130) > org.jboss.portal.server.aspects.server.ContentTypeInterceptor.invoke(ContentTypeInterceptor.java:65) > org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:37) > org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:130) > org.jboss.portal.core.aspects.server.LocaleInterceptor.invoke(LocaleInterceptor.java:74) > org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:37) > org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:130) > org.jboss.portal.core.aspects.server.UserInterceptor.invoke(UserInterceptor.java:161) > org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:37) > org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:130) > org.jboss.portal.server.aspects.server.SessionInvalidatorInterceptor.invoke(SessionInvalidatorInterceptor.java:92) > org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:37) > org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:130) > org.jboss.portal.core.aspects.server.TransactionInterceptor.org$jboss$portal$core$aspects$server$TransactionInterceptor$invoke$aop(TransactionInterceptor.java:49) > org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java) > org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) > org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:275) > org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java) > org.jboss.portal.core.aspects.server.TransactionInterceptor.invoke(TransactionInterceptor.java) > org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:37) > org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:130) > org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:171) > org.jboss.portal.server.servlet.PortalServlet.process(PortalServlet.java:270) > org.jboss.portal.server.servlet.PortalServlet.doGet(PortalServlet.java:172) > javax.servlet.http.HttpServlet.service(HttpServlet.java:697) > javax.servlet.http.HttpServlet.service(HttpServlet.java:810) > org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBPORTAL-880) Move PortalDeployment classes to JBoss XB

by Chris Laprun (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-880?page=all ] Chris Laprun updated JBPORTAL-880: ---------------------------------- Priority: Minor (was: Major) > Move PortalDeployment classes to JBoss XB > ----------------------------------------- > > Key: JBPORTAL-880 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-880 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.2.1 Final > Reporter: Chris Laprun > Assigned To: Chris Laprun > Priority: Minor > Fix For: 2.6 Final > > Original Estimate: 3 days > Time Spent: 5 hours > Remaining Estimate: 2 days, 3 hours > > Portal deployment files are currently "manually" parsed via the common.util.XML class. Leveraging JBoss XB should allow for easier maintenance and possibly speed. -- 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

19 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-976) Improve WSRP documentation

by Chris Laprun (JIRA)

Improve WSRP documentation -------------------------- Key: JBPORTAL-976 URL: http://jira.jboss.com/jira/browse/JBPORTAL-976 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation, Portal WSRP Affects Versions: 2.4 Final Reporter: Chris Laprun Assigned To: Chris Laprun Priority: Minor Fix For: 2.4 Final -- 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

19 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3513) adding <distributable> to webapp's web.xml causes ERROR on startup in default server profile

by Hany Mesha (JIRA)

adding <distributable> to webapp's web.xml causes ERROR on startup in default server profile -------------------------------------------------------------------------------------------- Key: JBAS-3513 URL: http://jira.jboss.com/jira/browse/JBAS-3513 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-4.0.4.GA Environment: Suse Linux Enterprise Desktop 10 on IBM Thinkpad T40p with JDK 1.5 Reporter: Hany Mesha Assigned To: Brian Stansberry Priority: Minor To reproduce, add <distributable> to a webapp's web.xml and deploy to a default server profile. You'll see the following exception thrown on the server console: 11:50:38,181 ERROR [JBossCacheManager] JBossCacheService to Tomcat clustering not found java.lang.NoClassDefFoundError: org/jboss/cache/CacheException [stacktrace].... followed by .. 11:50:38,215 ERROR [TomcatDeployer] Failed to setup clustering, clustering disabled. Exception: org.jboss.web.tomcat.tc5.session.ClusteringNotSupportedException: JBossCacheService to Tomcat clustering not found [stacktrace]... While the exception is true and the cluster is disabled at the end. It should only warn the user and not throw the exception. -- 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

19 years, 11 months

3
2
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 2006