July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JASSIST-21) release javassist 3.1 to ibiblio

by Shigeru Chiba (JIRA)

[ https://jira.jboss.org/jira/browse/JASSIST-21?page=com.atlassian.jira.plu... ] Shigeru Chiba closed JASSIST-21. -------------------------------- > release javassist 3.1 to ibiblio > -------------------------------- > > Key: JASSIST-21 > URL: https://jira.jboss.org/jira/browse/JASSIST-21 > Project: Javassist > Issue Type: Task > Environment: ibiblio.org/maven2 > Reporter: Jesse Kuhnert > Assignee: Shigeru Chiba > > I have a project using javassist 3.1 and would find it easier to manage if the ibiblio/maven2 repo hosted javassist 3.1 (already has 3.0 > ) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1441) QuerySyntaxException class is not mapped

by Kenneth RenÃ© SÃ¡nchez SÃ¡nchez (JIRA)

QuerySyntaxException class is not mapped ---------------------------------------- Key: EJBTHREE-1441 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1441 Project: EJB 3.0 Issue Type: Task Environment: JBoss 4.2.0.GA - Seam 2.0.1.GA Reporter: Kenneth RenÃ© SÃ¡nchez SÃ¡nchez I have a jar file (acad.jar) than contain TemaIcfes Entity: package co.academico.entidades; import java.io.Serializable; import javax.persistence.Entity; import javax.persistence.Id; import javax.persistence.Table; import javax.persistence.GeneratedValue; import org.jboss.seam.annotations.Name; @Entity @Name("TemaIcfes") @Table(name = "temas_icfes") public class TemaIcfes implements Serializable{ @Id @GeneratedValue private short tema; private String descripcion_tema; public short getTema(){ return tema; } public void setTema(short tema){ this.tema = tema; } public String getDescripcion_tema(){ return descripcion_tema; } public void setDescripcion_tema(String descripcion_tema){ this.descripcion_tema = descripcion_tema; } } The problem is that when I use it in another application through an EJB shows the following error: Exception during request processing: Caused by javax.el.ELException with message: "javax.ejb.EJBTransactionRolledbackException: org.hibernate.hql.ast.QuerySyntaxException: TemaIcfes is not mapped [SELECT a FROM TemaIcfes a ORDER BY tema]" Classes: HacerMantenimiento.java: package co.academico.admin; import java.util.List; import co.academico.entidades.TemaIcfes; import javax.ejb.Local; @Local public interface HacerMantenimiento{ public void crear(TemaIcfes tema); public List<TemaIcfes> consultarTemaIcfes(); public void modificar(TemaIcfes tema); public void listar(); public void eliminar(TemaIcfes tema); public void destroy(); } HacerMantenimientoEJB.java: package co.academico.admin; import static org.jboss.seam.ScopeType.SESSION; import java.util.List; import co.academico.entidades.TemaIcfes; import org.jboss.seam.annotations.Destroy; import org.jboss.seam.annotations.Name; import org.jboss.seam.annotations.Scope; import org.jboss.seam.annotations.datamodel.DataModel; import javax.ejb.Remove; import javax.ejb.Stateful; import javax.persistence.EntityManager; import javax.persistence.PersistenceContext; @Stateful @Scope(SESSION) @Name("hacerMantenimiento") public class HacerMantenimientoEJB implements HacerMantenimientoTemaIcfes{ @PersistenceContext private EntityManager em; @DataModel private List<TemaIcfes> temasIcfes; public void crear(TemaIcfes tema){ em.persist(tema); } public List<TemaIcfes> consultarTemaIcfes(){ temasIcfes = em.createQuery ("SELECT a "+ "FROM TemaIcfes a "+ "ORDER BY tema").getResultList(); return temasIcfes; } public void modificar(TemaIcfes tema){ em.merge(tema); em.flush(); } public void listar(){} public void eliminar(TemaIcfes tema){ em.remove(tema); } @Remove @Destroy public void destroy(){} } home.xhtml: <!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <ui:composition xmlns="http://www.w3.org/1999/xhtml" xmlns:s="http://jboss.com/products/seam/taglib" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html" xmlns:rich="http://richfaces.org/rich" template="layout/template.xhtml"> <ui:define name="body"> <h:messages globalOnly="true" styleClass="message"/> <rich:panel> <div class="section" style=" width : 593px;"> <h:outputText value="No existen temas registrados" rendered="#{temasIcfes != null and temasIcfes.rowCount==0}"/> <h:dataTable id="temasIcfes" value="#{temasIcfes}" var="tema" rendered="#{temasIcfes.rowCount>0}" style=" width : 377px;"> <h:column> <f:facet name="header">Codigo</f:facet> #{tema.tema} </h:column> <h:column> <f:facet name="header">Descripcion</f:facet> #{tema.descripcion_tema} </h:column> </h:dataTable> </div> </rich:panel> </ui:define> </ui:composition> pages.xml: ... <page view-id="/home.xhtml" action="#{hacerMantenimiento.consultarTemaIcfes}"> <navigation> <rule if="#{identity.loggedIn}"> <redirect view-id="/main.xhtml"/> </rule> </navigation> </page> ... persistence.xml: <?xml version="1.0" encoding="UTF-8"?>  <persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd" version="1.0"> <persistence-unit name="admisiones"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <jta-data-source>java:/admisionesDatasource</jta-data-source> <properties> <property name="hibernate.dialect" value="org.hibernate.dialect.InformixDialect"/> <property name="hibernate.show_sql" value="true"/> <property name="hibernate.format_sql" value="true"/> <property name="jboss.entity.manager.factory.jndi.name" value="java:/admisionesEntityManagerFactory"/> </properties> </persistence-unit> </persistence> What is the problem? They could help to solve this problem please? -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4811) Integrate the JBossWS core testsuite in the release QA

by Thomas Diesler (JIRA)

Integrate the JBossWS core testsuite in the release QA ------------------------------------------------------ Key: JBAS-4811 URL: http://jira.jboss.com/jira/browse/JBAS-4811 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossAS-4.2.2.GA Changes to the AS code base (especially EJB3) may break JAX-WS functionality that likely will not get discovered through the existing JAX-WS test coverage in the AS test suite. The jbossws core tests should be run (automated) as part of every AS community release. -- 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

16 years, 2 months

5
34
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1961) portal/portlet security broken with josso

by Martin Schubert (JIRA)

portal/portlet security broken with josso ----------------------------------------- Key: JBPORTAL-1961 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1961 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Environment: JOSSO 1.7 Reporter: Martin Schubert - Admin portal is not showing up in the header and is not accessible even if logged in as admin with admin role assigned - Portlets with role restrictions are not accessible anymore How to reproduce: - take a fresh jboss portal bundle - install josso 1.7 - follow the guide at http://docs.jboss.com/jbportal/v2.6.4/referenceGuide/html/sso.html -- 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

16 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBREM-1005) Prevent build up of cancelled TimerTasks in bisocket transport

by Ron Sigal (JIRA)

Prevent build up of cancelled TimerTasks in bisocket transport -------------------------------------------------------------- Key: JBREM-1005 URL: http://jira.jboss.com/jira/browse/JBREM-1005 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP8, 2.4.0.GA (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.SP1, 2.2.2.SP9 The behavior of java.util.Timer and java.util.TimerThread is such that a cancelled java.util.TimerTask is removed from the Timer's queue the next time it is executed after being cancelled. JBossMessaging has effectively disabled the bisocket control connection ping mechanism by setting the parameter "pingFrequency" to 214748364, which means that the org.jboss.remoting.transport.bisocket.BisocketServerInvoker.ControlMonitorTimerTask gets created but essentially "never" runs. So when a JBM connection closes, it also shuts down the Remoting bisocket connection, which causes the ControlMonitorTimerTask to get cancelled, but it remains in the Timer queue "forever". -- 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

16 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1951) CMS Portlet Window Last-Modified HTTP Header

by Mike Millson (JIRA)

CMS Portlet Window Last-Modified HTTP Header -------------------------------------------- Key: JBPORTAL-1951 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1951 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.4 Final, 2.6.3 Final, 2.6.2 Final, 2.6.1 Final, 2.6 Final Reporter: Mike Millson Assigned To: Sohil Shah Add the HTTP last-modified header to the CMS Portlet Window. Currently CMS page links (images, css, js) do have the last-modified header set; however, the main page does not. Perhaps change the CMSPortlet to outject the header info so it can be injected during final page rendering. -- 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

16 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-60) Add nestedWarManfiestClasspath option for processing of war manifest classpaths

by Scott M Stark (JIRA)

Add nestedWarManfiestClasspath option for processing of war manifest classpaths ------------------------------------------------------------------------------- Key: JBDEPLOY-60 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-60 Project: JBoss Deployers Issue Type: Feature Request Components: structure Affects Versions: JBDEPLOY-2.0.0.Beta18 Reporter: Scott M Stark Assignee: Adrian Brock Fix For: JBDEPLOY-2.0.0.CR1 As discussed in the forum thread there is a regression in the default behavior of how the classpath of wars with manifest classpaths that reference parent deployment jars behaves in jbossas5.0.0.CR1 vs jbossas5.0.0.Beta4 and jbossas4.x. We need an option to ignore manifest classpath references to parent deployment classpath entries. -- 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, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2008) adding an image from CMS to dashboard renders image's binary representation

by Prabhat Jha (JIRA)

adding an image from CMS to dashboard renders image's binary representation --------------------------------------------------------------------------- Key: JBPORTAL-2008 URL: http://jira.jboss.com/jira/browse/JBPORTAL-2008 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.5 Final Reporter: Prabhat Jha Assigned To: Sohil Shah When configuring dashboard, if you add an image using CMS as content type, image is displayed at binary gibberish -- 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

16 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-5725) Verify EJB3 tests are passing

by Dimitris Andreadis (JIRA)

Verify EJB3 tests are passing ----------------------------- Key: JBAS-5725 URL: http://jira.jboss.com/jira/browse/JBAS-5725 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assigned To: Shelly McGowan Priority: Critical Fix For: JBossAS-4.2.3.GA Verify the status regarding the EJB3 testsuite (not sure which exactly) :-) -- 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

16 years, 2 months

1
5
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-244) Enable quotas for users

by Jay Howell (JIRA)

[ https://jira.jboss.org/jira/browse/JBMESSAGING-244?page=com.atlassian.jir... ] Jay Howell commented on JBMESSAGING-244: ---------------------------------------- I'm addding a feature request to constrain sessions on the server. I was going to change this jira to match the session request, but this feature seems to stand on it's own. Clarification of this feature. This feature seems to allow quotas for a specific user or a specific group of users. I would suggest that this feature be geared off of the security group perqueue. I would suggest that this feature be a security feature for the queues. When we define the security constraints for a queue, you could also define quota's for users for specific queues. > Enable quotas for users > ----------------------- > > Key: JBMESSAGING-244 > URL: https://jira.jboss.org/jira/browse/JBMESSAGING-244 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Priority: Optional > Fix For: 2.0.0 Beta > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Investigate whether we need to provide quotas functionality for users. I.e. limit number of messages able to send per sec etc. -- 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, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2008