December 2007 - jboss-jira - Jboss List Archives

[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: (JBPORTAL-1841) URL hacking allows edit mode in weather portlet

by Prabhat Jha (JIRA)

URL hacking allows edit mode in weather portlet ----------------------------------------------- Key: JBPORTAL-1841 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1841 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.3 Final Reporter: Prabhat Jha Assigned To: Thomas Heute Priority: Critical If you are not logged in then weather portlet does not show edit icon which is good. But if I hack the URL to http://localhost:8080/portal/auth/portal/default/Weather/WeatherPortletWi..., I am able to get into edit mode and change the zip code. Is this how it supposed to be? Sohil suggests: "no it shouldn't do that. Either the Edit Mode logic of the Portlet should protect against this (a bit painful design), or Portal's security layer should have the granularity to provide role-based protection of the "Edit Mode" of Portlets as a cross cutting aspect. I like the second option better personally" -- 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
8
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: (JBRULES-1387) Drools doesn't build with fresh maven2 installation and no repository

by Geoffrey De Smet (JIRA)

Drools doesn't build with fresh maven2 installation and no repository --------------------------------------------------------------------- Key: JBRULES-1387 URL: http://jira.jboss.com/jira/browse/JBRULES-1387 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.3 Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Minor Fix For: 4.0.4 Some wierd exception is thrown and it's being caused when it's trying to get the pom of this: <extensions> <extension> <groupId>org.apache.maven.wagon</groupId> <artifactId>wagon-webdav</artifactId> <version>1.0-beta-2</version> </extension> </extensions> -- 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: (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: (JBCACHE-1229) Buddy Replication configuration doesn't start if FetchInMemoryState is false.

by Manik Surtani (JIRA)

Buddy Replication configuration doesn't start if FetchInMemoryState is false. ----------------------------------------------------------------------------- Key: JBCACHE-1229 URL: http://jira.jboss.com/jira/browse/JBCACHE-1229 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR2 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.GA Should be allowed to skip in-memory state transfer -- 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: (JBREM-882) Simple static API to easily create simple clients

by David Lloyd (JIRA)

Simple static API to easily create simple clients ------------------------------------------------- Key: JBREM-882 URL: http://jira.jboss.com/jira/browse/JBREM-882 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Priority: Minor Fix For: Remoting 3 M2 Right now the user has to create an endpoint, register protocol handler support, open a session, locate a service, and only then can they open contexts. This is fine in a container where all that stuff would be managed for you. But for trivial clients it's a PITA. Some kind of simple static method for trivial clients would be nice: ContextSource<RequestType, ReplyType> source = Remoting.connectToService(uri, userName, password, serviceType, RequestType.class, ReplyType.class); Context<RequestType, ReplyType> context = source.openContext(); ReplyType r = context.invoke(context.createRequest(new RequestType(...))).getBody(); Maybe even provide some behind-the-scenes session pooling or something... -- 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
1
0 / 0

[JBoss JIRA] Created: (JBREM-881) Stream detection/object substitution

by David Lloyd (JIRA)

Stream detection/object substitution ------------------------------------ Key: JBREM-881 URL: http://jira.jboss.com/jira/browse/JBREM-881 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: Remoting 3 M2 Add in a registry mechanism on Endpoint; make the serializer use the stream detector to get a substitution object; create a lookup mechanism to fetch the appropriate proxy in place of the placeholder object (using readObjectOverride) -- 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
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 December 2007