Marco Barber [http://community.jboss.org/people/violentstormm] created the discussion
"Re: Looking for Examples" To view the discussion, visit: http://community.jboss.org/message/563896#563896 -------------------------------------------------------------- Here we go: Finally I've managed it to get a working Jboss 5.1 GA with jdk1.6 and Mysql connection. Also the Seam-bay application was deployed successfully with Mysql connection. Therefore I edited the jboss-seam-bay-ds.xml as followed: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE datasources PUBLIC -//JBoss//DTD JBOSS JCA Config 1.5//EN http://www.jboss.org/j2ee/dtd/jboss-ds_1_5.dtd> <datasources> <local-tx-datasource> <jndi-name>seambayDatasource</jndi-name> <connection-url>jdbc:mysql://localhost:3306/jboss</connection-url> <driver-class>com.mysql.jdbc.Driver</driver-class> <user-name>jboss</user-name> <password>jboss</password> <valid-connection-checker-class-name>org.jboss.resource.adapter.jdbc.vendor.MySQLValidConnectionChecker</valid-connection-checker-class-name> <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation> <metadata> <type-mapping>mySQL</type-mapping> </metadata> </local-tx-datasource> </datasources> when I start the server with the all config there are some warnings and 1 Error: Error: 12:31:02,033 ERROR [SchemaExport] schema export unsuccessful org.hibernate.JDBCException: Error during import script execution at line 1 Warnings: 2010-09-28 12:30:50,794 WARN [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (main) WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this. 2010-09-28 12:30:50,814 WARN [org.jboss.annotation.factory.AnnotationCreator] (main) No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent 2010-09-28 12:30:51,031 WARN [org.jboss.annotation.factory.AnnotationCreator] (main) No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent 2010-09-28 12:30:58,616 WARN [org.jboss.ejb3.interceptors.aop.InjectInterceptorsFactory] (main) WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.extendedmanagedobjectadvi...@4c091108 2010-09-28 12:30:58,624 WARN [org.jboss.ejb3.interceptors.aop.InjectInterceptorsFactory] (main) WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.extendedmanagedobjectadvi...@4c091108 2010-09-28 12:30:58,631 WARN [org.jboss.ejb3.interceptors.aop.InjectInterceptorsFactory] (main) WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.extendedmanagedobjectadvi...@4c091108 2010-09-28 12:30:58,633 WARN [org.jboss.ejb3.interceptors.aop.InjectInterceptorsFactory] (main) WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.extendedmanagedobjectadvi...@4c091108 2010-09-28 12:30:59,234 WARN [org.hibernate.ejb.Ejb3Configuration] (main) Persistence provider caller does not implement the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null. 2010-09-28 12:31:01,571 WARN [org.hibernate.impl.SessionFactoryObjectFactory] (main) InitialContext did not implement EventContext 2010-09-28 12:31:02,692 WARN [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) schema_reference.4: Failed to read schema document 'jaxws-config_2.0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. @ *unknown*[4,76] 2010-09-28 12:31:03,182 WARN [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] (main) schema_reference.4: Failed to read schema document 'jaxws-config_2.0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. @ *unknown*[4,76] 2010-09-28 12:31:03,460 WARNING [javax.enterprise.resource.webcontainer.jsf.config] (main) Unable to process deployment descriptor for context '/jboss-seam-bay-jboss-seam-bay' 2010-09-28 12:31:03,735 WARN [org.jboss.seam.jsf.SeamPhaseListener] (main) There should only be one Seam phase listener per application 2010-09-28 12:31:05,800 WARN [org.jboss.seam.Component] (main) Component class should be serializable: bidAction 2010-09-28 12:31:06,111 WARN [org.jboss.seam.async.QuartzDispatcher] (main) No seam.quartz.properties file. Using in-memory job store. 2010-09-28 12:31:06,115 WARN [org.jboss.seam.security.permission.PersistentPermissionResolver] (main) no permission store available - please install a PermissionStore with the name 'org.jboss.seam.security.jpaPermissionStore' if persistent permissions are required. How should I handle these messages? Edit: Could handle the Error by myself. It was caused by some Case-sensetive Erros in the import.sql file.. Now Everything runs smooth until I want to place a bid.. therefore I get some strange exeptions: Exception during request processing: Caused by javax.servlet.ServletException with message: "#{bidAction.confirmBid}: javax.persistence.PersistenceException: org.hibernate.exception.DataException: could not insert: [org.jboss.seam.example.seambay.Bid]" Caused by javax.faces.FacesException with message: "#{bidAction.confirmBid}: javax.persistence.PersistenceException: org.hibernate.exception.DataException: could not insert: [org.jboss.seam.example.seambay.Bid]" Caused by javax.faces.el.EvaluationException with message: "javax.persistence.PersistenceException: org.hibernate.exception.DataException: could not insert: [org.jboss.seam.example.seambay.Bid]" what should I do? Nachricht geändert durch Marco Barber -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/563896#563896] Start a new discussion in Beginner's Corner at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2075]
_______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
