October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4564) Hibernate EntityManager 3.3.2

by Emmanuel Bernard (JIRA)

Hibernate EntityManager 3.3.2 ----------------------------- Key: JBAS-4564 URL: http://jira.jboss.com/jira/browse/JBAS-4564 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Emmanuel Bernard -- 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, 8 months

3
13
0 / 0

[JBoss JIRA] Created: (JBAS-4130) Simple HelloWorld JSF 1.2 application does not work

by sedat ciftci (JIRA)

Simple HelloWorld JSF 1.2 application does not work --------------------------------------------------- Key: JBAS-4130 URL: http://jira.jboss.com/jira/browse/JBAS-4130 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services Affects Versions: JBossAS-5.0.0.Beta1 Environment: Windows XP, JSF application is created with Netbeans5.5 (+ Visual Web Pack) Reporter: sedat ciftci Assigned To: Dimitris Andreadis I have faced with a problem while deploying my JSF 1.2 web application (sun impl) ( I build with Netbeans 5.5 Visual Web pack) to JBoss5 Beta. It works with Glassfish. In order to find the problem, I make a simple Hello world web application and try to deploy it to JBoss5Beta. However, I get the same exception. The first exception that I overcome is related with web-facesconfig_1_2.xsd. JBoss says that it can not resolve this schema. I solve this problem by putting this file into the jboss.jar/schema. The second exception that I cannot solve is although my projects managed-beans.xml file is well formed, JBoss throws such an exception: org.jboss.deployers.spi.DeploymentException: The xml JBoss5Ex.war/WEB-INF/managed-beans.xml is not well formed! at org.jboss.deployers.plugins.deployers.helpers.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:94) at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.parse(AbstractParsingDeployer.java:173) at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.createMetaData(AbstractParsingDeployer.java:114) at org.jboss.deployers.plugins.deployers.helpers.AbstractParsingDeployer.createMetaData(AbstractParsingDeployer.java:88) at org.jboss.deployers.plugins.deployers.kernel.BeanDeployer.deploy(BeanDeployer.java:59) at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDeploy(AbstractSimpleDeployer.java:52) at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(DeployerWrapper.java:145) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(MainDeployerImpl.java:440) at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainDeployerImpl.java:381) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:366) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:246) at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89) at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401) at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340) at org.jboss.Main.boot(Main.java:210) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:595) Note that JBoss5Ex.war is my web application. What can be the problem? Any suggestions? Here is the content of my managed-beans.xml file (starting after the #'s line): ###################################### <?xml version="1.0" encoding="UTF-8"?> <faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_1_2.xsd"> <managed-bean> <managed-bean-name>SessionBean1</managed-bean-name> <managed-bean-class>jboss5ex.SessionBean1</managed-bean-class> <managed-bean-scope>session</managed-bean-scope> </managed-bean> <managed-bean> <managed-bean-name>Page1</managed-bean-name> <managed-bean-class>jboss5ex.Page1</managed-bean-class> <managed-bean-scope>request</managed-bean-scope> </managed-bean> <managed-bean> <managed-bean-name>ApplicationBean1</managed-bean-name> <managed-bean-class>jboss5ex.ApplicationBean1</managed-bean-class> <managed-bean-scope>application</managed-bean-scope> </managed-bean> <managed-bean> <managed-bean-name>RequestBean1</managed-bean-name> <managed-bean-class>jboss5ex.RequestBean1</managed-bean-class> <managed-bean-scope>request</managed-bean-scope> </managed-bean> </faces-config> ################################################# Thanks, Sedat -- 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, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1739) Replace use to QName constuctor to use of QName.valueOf where appropriate.

by Chris Laprun (JIRA)

Replace use to QName constuctor to use of QName.valueOf where appropriate. -------------------------------------------------------------------------- Key: JBPORTAL-1739 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1739 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Core, Portal WSRP Affects Versions: 2.6.3 Final, 2.8 Final Reporter: Chris Laprun Assigned To: Chris Laprun Priority: Minor Fix For: 2.6.3 Final, 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1723) Remove WSDLPortFixFilter

by Chris Laprun (JIRA)

Remove WSDLPortFixFilter ------------------------ Key: JBPORTAL-1723 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1723 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.3 Final, 2.8 Final Reporter: Chris Laprun Assigned To: Chris Laprun Priority: Minor Fix For: 2.6.3 Final, 2.8 Final Since Portal will only be supported on AS 4.2 starting with Portal 2.6.3, WSDLPortFixFilter is not useful anymore and should be removed. -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1718) WSRP interop testing

by Chris Laprun (JIRA)

WSRP interop testing -------------------- Key: JBPORTAL-1718 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1718 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.1 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6.3 Final, 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, 8 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1130) Remove unused column INST_TIME

by Tim Fox (JIRA)

Remove unused column INST_TIME ------------------------------ Key: JBMESSAGING-1130 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1130 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: EAP 4.3 Integration -- 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, 8 months

1
8
0 / 0

[JBoss JIRA] Created: (JBRULES-1283) Unable to serialize rule base

by Jiri Pechanec (JIRA)

Unable to serialize rule base ----------------------------- Key: JBRULES-1283 URL: http://jira.jboss.com/jira/browse/JBRULES-1283 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0.2 Reporter: Jiri Pechanec Assigned To: Mark Proctor Priority: Minor When I am trying to serialize rulebase, I am getting the exception Caused by: java.io.NotSerializableException: org.drools.base.FireAllRulesRuleBaseUpdateListener at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) at java.util.ArrayList.writeObject(ArrayList.java:569) at sun.reflect.GeneratedMethodAccessor147.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:391) at java.util.Collections$SynchronizedCollection.writeObject(Collections.java:1606) at sun.reflect.GeneratedMethodAccessor193.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) at org.drools.common.AbstractRuleBase.doWriteExternal(AbstractRuleBase.java:180) at org.drools.reteoo.ReteooRuleBase.writeExternal(ReteooRuleBase.java:147) at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1310) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1288) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) at org.jbpm.context.exe.converter.SerializableToByteArrayConverter.convert(SerializableToByteArrayConverter.java:49) -- 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, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBFORUMS-230) configure JavaBuilder into .project files

by Luca Stancapiano (JIRA)

configure JavaBuilder into .project files ----------------------------------------- Key: JBFORUMS-230 URL: http://jira.jboss.com/jira/browse/JBFORUMS-230 Project: JBoss Forums Issue Type: Patch Affects Versions: 1.0.1 RC Environment: jboss forums from http://anonsvn.labs.jboss.com/branches/forums101P26 eclipse 3.2.2 Reporter: Luca Stancapiano Assigned To: Ryszard Kozmik Fix For: 1.0.1 RC hi ......I think is better to configure .project files to build with eclipse as jbossportal does.....So is simpliest to build sources with eclipse. I added theese rows into .project files of forums project and authz-jaae-plugin project. Tell me if you are agree: <buildSpec> <buildCommand> <name>org.eclipse.jdt.core.javabuilder</name> <arguments> </arguments> </buildCommand> </buildSpec> <natures> <nature>org.eclipse.jdt.core.javanature</nature> </natures> -- 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, 8 months

2
13
0 / 0

[JBoss JIRA] Created: (JBFORUMS-254) ClassCastException in org.jboss.portlet.forums.ui.PortalUtil in function getPoster

by Lukasz Wiktor (JIRA)

ClassCastException in org.jboss.portlet.forums.ui.PortalUtil in function getPoster ---------------------------------------------------------------------------------- Key: JBFORUMS-254 URL: http://jira.jboss.com/jira/browse/JBFORUMS-254 Project: JBoss Forums Issue Type: Bug Affects Versions: 1.0.0 GA Environment: JBoss Portal 2.6.1.GA bundled with JBoss AS 4.2.1 and integrated with OpenLDAP Reporter: Lukasz Wiktor Assigned To: Ryszard Kozmik In class org.jboss.portlet.forums.ui.PortalUtil in function getPoster() userId is casted to Long. That causes ClassCastException when userId is for example type of String (in LDAP). 2007-10-04 15:35:07,700 ERROR [org.jboss.portlet.forums.ui.JSFUtil] org.jboss.portlet.forums.ui.JSFUtil java.lang.ClassCastException: java.lang.String at org.jboss.portlet.forums.ui.PortalUtil.getPoster(PortalUtil.java:467) ... It prevents from e.g. creating new topic. See my posts on the forum. I have proposed the solution. -- 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, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-608) FLUSH not safe in simultaneous flush situation

by Michael Newcomb (JIRA)

FLUSH not safe in simultaneous flush situation ---------------------------------------------- Key: JGRP-608 URL: http://jira.jboss.com/jira/browse/JGRP-608 Project: JGroups Issue Type: Feature Request Affects Versions: 2.6 Reporter: Michael Newcomb Assigned To: Bela Ban I'm running into a few problems when multiple members request a FLUSH at the same time. I am still in the process of analyzing the situation, but here are a few problems: private void handleStartFlush(Message msg, FlushHeader fh) { byte oldPhase = flushPhase.transitionToFirstPhase(); if(oldPhase == FlushPhase.START_PHASE){ sendBlockUpToChannel(); onStartFlush(msg.getSrc(), fh); }else if(oldPhase == FlushPhase.FIRST_PHASE){ Address flushRequester = msg.getSrc(); Address coordinator = null; synchronized(sharedLock){ if(flushCoordinator != null) coordinator = flushCoordinator; else coordinator = flushRequester; } After a successful transtion to the first phase, onStartFlush is called. Inside the method, the flushCoordinator is set. However a simultaneous handleStartFlush from another member would fail the transitionToFirstPhase() call, but it is possible that the flushCoordinator might not be set yet and the second handleStartFlush would end up setting the 'coordinator' to the flushRequestor. This could grant the second START_FLUSH a FLUSH_OK without rejecting the flush that succeeded in the transitionToFirstPhase(). IMHO the transitionToFirstPhase() should assign the flushCoordinator at that time to avoid the above situation, in fact, all of the protected parts of the onStartFlush() call should be made inside the protected section of transitionToFirstPhase(). The above should take care of the didn't-succeed-in-transitionToFirstPhase-but-became-flushCoordinator-anyways-because-flushCoordinator-wasn't-set-yet problem. Now, there is another problem in the way simultaneous START_FLUSHes are resolved. If the new flushRequestor is < the current flushCoordinator the new requestor will win the flush fight. This is a great strategy because all the members will get the same result here. If A, B, C are members and A < B < C and they all simultaneously request a flush, then the desired effect is for everyone to decide that A will win the flush fight. So the following code handles that situation... private void handleStartFlush(Message msg, FlushHeader fh) { ... }else if(oldPhase == FlushPhase.FIRST_PHASE){ ... if(flushRequester.compareTo(coordinator) < 0){ rejectFlush(fh.viewID, coordinator); ... synchronized(sharedLock){ flushCoordinator = flushRequester; } } If the new flushRequetor is < the old flushCoordinator than reject/abort the old flush. However, the new flushCoordinator is never acknowledged by a onStartFlush (which sends FLUSH_OK). If we moved all the protected parts of onStartFlush() to transitionToFirstPhase() then the flush members would never be set properly, so that situation needs to be resolved as well. I think this might be the problem I'm seeing because I wait indefinitely for my flush to succeed. I will be testing a patch this afternoon and hope to report back. -- 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, 8 months

3
17
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