November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1688) Maven module template

by Julien Viet (JIRA)

Maven module template --------------------- Key: JBPORTAL-1688 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1688 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Julien Viet Assigned To: Wesley Hales Fix For: 2.8 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

18 years, 6 months

3
2
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-177) Merge the unified metadata work

by Scott M Stark (JIRA)

Merge the unified metadata work ------------------------------- Key: JBMICROCONT-177 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-177 Project: JBoss MicroContainer Issue Type: Task Components: MetaData Reporter: Scott M Stark Need to merge the unified metadata work so we can start integrate it into the deployers. -- 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, 6 months

5
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1745) DTD documentation is out of date

by Chris Laprun (JIRA)

DTD documentation is out of date -------------------------------- Key: JBPORTAL-1745 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1745 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Chris Laprun This applies to the actual documentation in the DTD but also to the DTD documentation in the reference guide. -- 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, 6 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1462) Documentation should include a section on how to remove/destroy created objects via the Admin GUI

by Chris Laprun (JIRA)

Documentation should include a section on how to remove/destroy created objects via the Admin GUI ------------------------------------------------------------------------------------------------- Key: JBPORTAL-1462 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1462 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.6.CR2 Reporter: Chris Laprun Assigned To: Julien Viet Fix For: 2.6 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

18 years, 6 months

3
8
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1521) Missing documentation on properties?

by Chris Laprun (JIRA)

Missing documentation on properties? ------------------------------------ Key: JBPORTAL-1521 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1521 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.6 Final Reporter: Chris Laprun Assigned To: Julien Viet Fix For: 2.6.1 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

18 years, 6 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-4725) Upgrade Hibernate to 3.3.x (from 3.2.4.SP1_CP01)

by Dimitris Andreadis (JIRA)

Upgrade Hibernate to 3.3.x (from 3.2.4.SP1_CP01) ------------------------------------------------ Key: JBAS-4725 URL: http://jira.jboss.com/jira/browse/JBAS-4725 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Hibernate service Reporter: Dimitris Andreadis Assigned To: Steve Ebersole Fix For: JBossAS-5.0.0.CR1 An issue to track the hibernate upgrade needed by JBoss Cache. Brian: "The current Hibernate core release is not compatible with JBoss Cache 2.0 (JBC API is very different.) This breaks using JBC as a Hibernate 2nd level cache. For EJB3 entity caching I've written a CacheProvider impl that deals with JBC 2.0, so that use case is handled. But if people want to use Hibernate+JBC outside of EJB3, that will be a problem. A workaround to this would be to write an equivalent to what I did for EJB3 and include it in the hibernate-int module. I'm currently working with Steve on a *much* improved Hibernate/JBC integration for Hibernate 3.3. It would certainly be nicer to have AS 5 use that." -- 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, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JASSIST-34) Throw a more descriptive exception when a class file does not start with 0xCAFEBABE

by Josh Devins (JIRA)

Throw a more descriptive exception when a class file does not start with 0xCAFEBABE ----------------------------------------------------------------------------------- Key: JASSIST-34 URL: http://jira.jboss.com/jira/browse/JASSIST-34 Project: Javassist Issue Type: Bug Environment: Jboss 4.0.5 GA with EJB3 deployer and IBM DB2 JDBC driver v3.3.54 Reporter: Josh Devins Assigned To: Shigeru Chiba Attachments: server.snipped.log I have deployed an application that is using the IBM DB2 JDBC driver jar version 3.3.54. With the EJB3 deployer installed (since we have EJB3s), some class file in the DB2 jar apparently does not start with 0XCAFEBABE, or "the magic hex code". The EJB3 deployer is using Javassist to examine all of the class files in the jar, but when it hits one of these wonky IBM class files, Javaasisst is throwing an IOException with message "non class file". This is rather useless as the EJB3 deployer then rethrows this IOException as a RuntimeException. I get no info about what class failed, what jar file it was in, etc. Perhaps this is an EJB3 deployer issue, but I believe that Javassist should at least throw a more descriptive exception, and not even an IOException. Or better yet, the EJB3 deployer should not just die and rethrow the RuntimeException, just skip the file! Stepping through the JBoss and Javassist code with my debugger was the only way to figure this out. You can look at the attached stack trace from the server log for the exact files and line numbers. -- 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, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1284) ClassCastException when using "<" constraint on field of type java.lang.Object containing data of type java.lang.Integer

by Justin Wick (JIRA)

ClassCastException when using "<" constraint on field of type java.lang.Object containing data of type java.lang.Integer ------------------------------------------------------------------------------------------------------------------------ Key: JBRULES-1284 URL: http://jira.jboss.com/jira/browse/JBRULES-1284 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.2 Environment: Windows XP, Eclipse 3.2 Reporter: Justin Wick Assigned To: Mark Proctor If I'm doing a pattern constraint, say "< 50" on a field, and that field is type java.lang.Object, with a value of type java.lang.Integer, a ClassCastException is generated at run time, although there is no compile-time error saying that this is an illegal constraint. See attached files for an example -- 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, 6 months

4
14
0 / 0

[JBoss JIRA] Created: (JBAS-4254) Client read timeout setting wanted for HTTP Invoker

by Anders Welen (JIRA)

Client read timeout setting wanted for HTTP Invoker ---------------------------------------------------- Key: JBAS-4254 URL: http://jira.jboss.com/jira/browse/JBAS-4254 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.3 SP1 Reporter: Anders Welen Priority: Minor There is no read timeout setting to prevent client threads from hanging while using the HTTP Invoker. A quick fix (if you are using SUN JVM) is to use the parameter "-Dsun.net.client.defaultReadTimeout=60000". The problem with this solution is that it affects all connection, not just the HTTPInvoker. A solution that works (if Java 5 is used) is to add a call to the method "setReadTimeout(xxx)" on the "conn" variable in the method "invoke()" in "org.jboss.invocation.http.interfaces.Util". (The same problem exists with the standard JRMP Invoker aswell. It's just the Pooled Invoker that has a read timeout) -- 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, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBFORUMS-262) Empty post error displays MessageValidationException

by Luc Boudreau (JIRA)

Empty post error displays MessageValidationException ---------------------------------------------------- Key: JBFORUMS-262 URL: http://jira.jboss.com/jira/browse/JBFORUMS-262 Project: JBoss Forums Issue Type: Bug Components: Forum View Layer Affects Versions: 1.0.1 RC Environment: Any Reporter: Luc Boudreau Assigned To: Ryszard Kozmik Priority: Critical Try to create a post, don't write anything as a subject or a body and press submit. The error message is totally useless. Message : org.jboss.portlet.forums.ui.action.MessageValidationException. Please try again Stack : 2007-11-05 15:41:35,075 ERROR [org.jboss.portlet.forums.ui.JSFUtil] org.jboss.po rtlet.forums.ui.JSFUtil org.jboss.portlet.forums.ui.action.MessageValidationException at org.jboss.portlet.forums.ui.action.PostAction.validateMessage(PostAct ion.java:561) at org.jboss.portlet.forums.ui.action.NewTopic.execute(NewTopic.java:118 ) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.sun.el.parser.AstValue.invoke(AstValue.java:130) at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:274) at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.ja va:68) at com.sun.facelets.el.LegacyMethodBinding.invoke(LegacyMethodBinding.ja va:69) at org.apache.myfaces.application.ActionListenerImpl.processAction(Actio nListenerImpl.java:63) at org.jboss.portlet.forums.auth.AuthorizationListener.processAction(Aut horizationListener.java:101) at javax.faces.component.UICommand.broadcast(UICommand.java:106) at javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:9 0) at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1 64) at org.apache.myfaces.lifecycle.LifecycleImpl.invokeApplication(Lifecycl eImpl.java:316) at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java :86) at org.jboss.portlet.forums.ui.ForumsJSFPortlet.processAction(ForumsJSFP ortlet.java:281) at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.invokeActio n(PortletContainerImpl.java:458) at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.dispatch(Po rtletContainerImpl.java:401) at org.jboss.portal.portlet.container.PortletContainerInvoker$1.invoke(P ortletContainerInvoker.java:86) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.j ava:131) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.org$jbos s$portal$core$aspects$portlet$TransactionInterceptor$invokeRequired$aop(Transact ionInterceptor.java:106) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRe quired_9103964459766407072.invokeNext(TransactionInterceptor$invokeRequired_9103 964459766407072.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java :195) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRe quired_9103964459766407072.invokeNext(TransactionInterceptor$invokeRequired_9103 964459766407072.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java :195) -- 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, 6 months

2
10
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 November 2007