February 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1590) Problem when deploying seam application as directory deployment in glassfish

by ivica c (JIRA)

Problem when deploying seam application as directory deployment in glassfish ---------------------------------------------------------------------------- Key: JBSEAM-1590 URL: http://jira.jboss.com/jira/browse/JBSEAM-1590 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Environment: glassfish V2 build 53 seam 2.0.0 beta1 jdk 1.6.0 update1 netbeans 6 daily build Reporter: ivica c Fix For: 2.0.0.CR1 Problem occurs when deploying seam application as directory deployment in glassfish. I am getting this exception: Exception occured in J2EEC Phasejava.lang.IllegalArgumentException: Invalid ejb jar [lib/jboss-seam.jar]: it contains zero ejb. Note: 1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean. 2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar. com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [ctg-main] -- Invalid ejb jar [lib/jboss-seam.jar]: it contains zero ejb. Note: 1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean. 2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar. at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:388) at com.sun.enterprise.deployment.backend.AppDeployerBase.loadDescriptors(AppDeployerBase.java:358) at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:226) at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:148) at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:191) at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108) at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:905) at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:279) at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:774) at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187) at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:223) Caused by: java.lang.IllegalArgumentException: Invalid ejb jar [lib/jboss-seam.jar]: it contains zero ejb. Note: 1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean. 2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar. at com.sun.enterprise.deployment.util.EjbBundleValidator.accept(EjbBundleValidator.java:95) at com.sun.enterprise.deployment.util.ApplicationValidator.accept(ApplicationValidator.java:82) at com.sun.enterprise.deployment.EjbBundleDescriptor.visit(EjbBundleDescriptor.java:729) at com.sun.enterprise.deployment.Application.visit(Application.java:1754) at com.sun.enterprise.deployment.archivist.ApplicationArchivist.validate(ApplicationArchivist.java:470) at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:790) at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:744) at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:349) ... 10 more but when I deploy as norma arhive(when upload it) everything works fine. -- 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

15 years, 10 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3398) To extend seam's Pages component to override "pages.xml" loading strategy

by Alex Sun (JIRA)

To extend seam's Pages component to override "pages.xml" loading strategy ------------------------------------------------------------------------- Key: JBSEAM-3398 URL: https://jira.jboss.org/jira/browse/JBSEAM-3398 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.0.BETA1 Reporter: Alex Sun Fix For: 2.1.0.CR1 -- 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

15 years, 10 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3959) excel-2.1.xsd not valid

by Jozef Hartinger (JIRA)

excel-2.1.xsd not valid ----------------------- Key: JBSEAM-3959 URL: https://jira.jboss.org/jira/browse/JBSEAM-3959 Project: Seam Issue Type: Bug Components: Excel Affects Versions: 2.1.1.GA Reporter: Jozef Hartinger Assignee: Nicklas Karlsson Fix For: 2.1.2.CR1 excel-2.1.xsd does not pass schema validation Error message: src/excel/org/jboss/seam/excel/excel-2.1.xsd:13:71: cvc-complex-type.2.4.a: Invalid content was found starting with element 'xs:element'. xs:element should be nested in xs:sequence or so -- 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

15 years, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3466) @UserRoles only works when using one ManyToMany-Relation instead of two OneToMany-Relations

by nimo stephan (JIRA)

@UserRoles only works when using one ManyToMany-Relation instead of two OneToMany-Relations ------------------------------------------------------------------------------------------- Key: JBSEAM-3466 URL: https://jira.jboss.org/jira/browse/JBSEAM-3466 Project: Seam Issue Type: Quality Risk Components: Security Affects Versions: 2.1.0.BETA1 Environment: EJB 3.0, JBOSS 4.2, SEAM 2.1, RichFaces (3.2) Reporter: nimo stephan Priority: Minor @UserRoles only works in ManyToMany-Relation. If we provide two @OneToMany-relations instead of one @ManyToMany, then @UserRoles does not work! The UserRolesProperty returns the UserRoles-Instance instead of the Roles-Instance. However, when having additional attributes in UserRoles we should better use two @OneToMany-Relations - but then @UserRoles does not work. As Shane said: "I don't think that we currently support cross reference tables in this manner, although we should. " Yes, it would be fine:-) thanks. -- 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

15 years, 10 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3937) rename of event org.jboss.seam.notLoggedIn to org.jboss.seam.security.notLoggedIn not fully encorporated in manual

by koen handekyn (JIRA)

rename of event org.jboss.seam.notLoggedIn to org.jboss.seam.security.notLoggedIn not fully encorporated in manual ------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3937 URL: https://jira.jboss.org/jira/browse/JBSEAM-3937 Project: Seam Issue Type: Bug Components: Documentation Issues Affects Versions: 2.1.1.GA Reporter: koen handekyn Priority: Trivial the seam manual still references the old event name on some places -- 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

15 years, 10 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3954) Turkish Language Support for Documentation

by Serhad Burakan (JIRA)

Turkish Language Support for Documentation ------------------------------------------ Key: JBSEAM-3954 URL: https://jira.jboss.org/jira/browse/JBSEAM-3954 Project: Seam Issue Type: Feature Request Components: Documentation Translation Reporter: Serhad Burakan Priority: Optional Turkish Language Support for Documentation -- 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

15 years, 10 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3953) change logLevel to log-level in the docs!

by Francisco Jose Peredo Noguez (JIRA)

change logLevel to log-level in the docs! ----------------------------------------- Key: JBSEAM-3953 URL: https://jira.jboss.org/jira/browse/JBSEAM-3953 Project: Seam Issue Type: Sub-task Affects Versions: 2.1.1.GA Reporter: Francisco Jose Peredo Noguez In http://docs.jboss.com/seam/2.1.1.GA/reference/en-US/html/events.html it still uses logLevel not log-level. -- 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

15 years, 10 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3952) LogLevel default should be LogLevel.error but it is null

by Francisco Jose Peredo Noguez (JIRA)

LogLevel default should be LogLevel.error but it is null -------------------------------------------------------- Key: JBSEAM-3952 URL: https://jira.jboss.org/jira/browse/JBSEAM-3952 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA, 2.1.1.CR2, 2.1.1.CR1, 2.1.0.SP1 Reporter: Francisco Jose Peredo Noguez In org.jboss.seam.exception.Exceptions in the parse method: LogLevel logLevel = LogLevel.error; <--- THIS LINE IS IRRELEVANT try { logLevel = exception.attributeValue("log-level") != null ? //<--- THIS LINE SETS THE DEFAULT TO NULL LogLevel.valueOf(exception.attributeValue("log-level").toLowerCase()) : null; //<--- THIS LINE TOO // The logLevel attribute is deprecated! Use log-level instead if (logLevel == null && exception.attributeValue("logLevel") != null) { logLevel = LogLevel.valueOf(exception.attributeValue("logLevel").toLowerCase()); } The line (168,169) sets the logLevel to null if it does not find the attribute in the .xml attribute, making the line 165 irrelevant, the actual default becomes "null" -- 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

15 years, 10 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3951) This issue is regarding Dynamic Datasource invocation at runtime in JSF-EJB3-MySql application on Eclipse3.4.1-JBoss5.0.0 plateform.

by Pragun Mehta (JIRA)

This issue is regarding Dynamic Datasource invocation at runtime in JSF-EJB3-MySql application on Eclipse3.4.1-JBoss5.0.0 plateform. ------------------------------------------------------------------------------------------------------------------------------------ Key: JBSEAM-3951 URL: https://jira.jboss.org/jira/browse/JBSEAM-3951 Project: Seam Issue Type: Task Components: Framework Environment: JSF-EJB3-MySql5 application on Eclipse3.4.1-JBoss5.0.0 Reporter: Pragun Mehta This issue is regarding Dynamic Datasource invocation at runtime in JSF-EJB3-MySql application on Eclipse3.4.1-JBoss5.0.0 plateform. I have created a sample JSF-EJB3-MySql application on JBoss5.0.0 AS. Application works fine which performs CRUD operation in database schema "schema1" on table "table1". my JBoss5.0.0 server datasource file C:\jboss5.0.0\server\default\deploy\mysql-ds.xml looks like <datasources> <local-tx-datasource> <jndi-name>DefaultDS</jndi-name> <connection-url>jdbc:mysql://host1:3306/schema1</connection-url> <driver-class>com.mysql.jdbc.Driver</driver-class> <user-name>username</user-name> <password>password</password> <min-pool-size>1</min-pool-size> <max-pool-size>2</max-pool-size> <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLExceptionSorter</exception-sorter-class-name> <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name> <metadata> <type-mapping>mySQL</type-mapping> </metadata> </local-tx-datasource> </datasources> my sample application has persistence.xml which looks like <persistence-unit name="pmtest"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <jta-data-source>java:/DefaultDS</jta-data-source> <properties> <property name="hibernate.archive.autodetection" value="class"/> <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/> <property name="hibernate.connection.driver_class" value="com.mysql.jdbc.Driver"/> <property name="hibernate.connection.username" value="username"/> <property name="hibernate.connection.password" value="password"/> <property name="hibernate.connection.url" value="jdbc:mysql://host1:3306/schema1"/> </properties> </persistence-unit> Primary requirement for my new application is as below, (1) Use JBoss Seam Framework to develop JSF-EJB3-MySql application on Eclipse3.4.1-JBoss5.0.0 (2) There are multiple databases (having exactly same table design structure) running on single database server "host1" placed in a central "Head Office" location i.e. jdbc:mysql://host1:3306/schema1 jdbc:mysql://host1:3307/schema2 jdbc:mysql://host1:3308/schema3 All the schemas listed above have has different JNDI name defined in mysql-ds.xml (multiple datasource configuration in one mysql-ds.xm file). As "table1" design structure is same in all the schema, the table1.java entity class of the application can be common. (3) The application will be deployed on one application server machine placed at the same central "Head Office" location where the database server "host1" is placed. This single application will access multiple databases running on database server "host1". This application will be called by various "Branch Office" from any other location say "Branch1", "Branch2" etc. So, is there any way in JBoss Seam framework using which, the application can identify which datasource to be invoked on the basis of "Branch User" login information ? i.e. Branch1 user --> invoke Schema1 datasource Branch2 user --> invoke Schema2 datasource I came across an article by Spring that provides the features as explained in http://blog.springsource.com/2007/01/23/dynamic-datasource-routing/ So, can we implement the Dynamic Datasource invocation logic in JBoss Seam using JSF-EJB3-MySql application on Eclipse3.4.1-JBoss5.0.0 plateform ? Thanks for your help in advance. -- 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

15 years, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3117) Configure label direction of chart's domain axis

by Alexander Kunkel (JIRA)

Configure label direction of chart's domain axis ------------------------------------------------ Key: JBSEAM-3117 URL: http://jira.jboss.com/jira/browse/JBSEAM-3117 Project: Seam Issue Type: Feature Request Components: PDF Reporter: Alexander Kunkel -- 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

15 years, 10 months

2
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2009