EDAS2-Forum

Community Forum :: INFO: EDAS 2 Application in Postgre SQL Database

Sun, 13 Sep 2009 15:02:02 -0400

Hi..

I know this project from Dan Allen post at jsf central. At the beginning I'm just curious about how to upgrade performance in seam framework application. Unfortunately, I don't have a Oracle Database instance in my notebook. I just have a PostgreSQL and MySQL. So I can't try and test the application in my machine.

Then I starting my migration from Oracle to PostgreSQL. Here is the PostgreSQL dump file: edasdb-postgresql. And FYI, here are small change I've been done to original database sample script:
- Change the BLOB datatype to bytea.
- Change the VARCHAR2 datatype to VARCHAR
- Change NUMBER datatype to numeric

Maybe I'm poor some optimization when migrating the data. But my first intent is quick-change-and-run in postgreSQL :D . I hope this is very useful for folks who need it. Thanks.

Community Forum :: Re: couldn't able deply the edas2.war into jboss server using build.xml

Thu, 25 Jun 2009 18:14:53 -0400

By: sdollani

Thank you got it working now !..

Community Forum :: couldn't able deply the edas2.war into jboss server using build.xml

Thu, 25 Jun 2009 09:12:13 -0400

By: sdollani

Hi,

I have been working on this issue from last couple of days, but i couldn't able to fix it.I am getting error like " Could not instantiate dialect class".Below i am giving my error details clearly.It would be really great help full to me if you could put me in right direction.

I am using Myeclipse 6.6 +Jboss 4.2.3+Java 1.5.

Below i have given two error details which are one is exception and other one is caused by....

07:58:53,318 ERROR [[/edas2]] Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener
org.jboss.seam.InstantiationException: Could not instantiate Seam component: entityManagerFactory
at org.jboss.seam.Component.newInstance(Component.java:1986)
at org.jboss.seam.contexts.Contexts.startup(Contexts.java:304)
at org.jboss.seam.contexts.Contexts.startup(Contexts.java:278)
at org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLifecycle.java:95)
at org.jboss.seam.init.Initialization.init(Initialization.java:596)
at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3856)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4361)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:790)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:770)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:296)
at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)

Caused by: javax.persistence.PersistenceException: org.hibernate.HibernateException: Could not instantiate dialect class
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:720)
at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:121)
at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:83)
at org.jboss.seam.persistence.EntityManagerFactory.createEntityManagerFactory(EntityManagerFactory.java:85)
at org.jboss.seam.persistence.EntityManagerFactory.startup(EntityManagerFactory.java:50)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:21)
at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125)
at org.jboss.seam.Component.callComponentMethod(Component.java:2100

Community Forum :: Re: Import settings

Fri, 29 May 2009 09:46:14 -0400

By: Shawn

Sorry, I should have added that I'm talking about results that are Not Detected. To be STORET compliant a result cannot have a Detection Condition and a measurement value.

Community Forum :: Import settings

Fri, 29 May 2009 09:42:39 -0400

By: Shawn

I have been testing and batch uploading data. I found something that is counter productive, if one wishes to use this program for WQX.

When using the import option, under Data Management, you cannot import results if there is no Measurement value filled in. But for a result value to be WQX compliant it cannot have a value for measurement value.

Is there anyway around this? Or am I just missing something?

Thanks!

Community Forum :: Re: Error Messages that are of no help

Fri, 01 May 2009 14:51:01 -0400

By: sroland

Thank you for the prompt response to my issue with EDAS2. It appears the connection problem stemmed from a change to the Host file we made to resolve an issue we had with JBoss halting for no apparent reason. We needed to add the server name to the Host file which fixed the JBoss issue. But that caused the Oracle connection issue. We needed to make the same change to the edas2-prod-ds.xml file which has all the connection information for Oracle. After making the change EDAS2 was then able to connect.

I again wish to thank you for the quick response.

Community Forum :: Re: Error Messages that are of no help

Fri, 01 May 2009 13:05:03 -0400

By: jstwhite

Take a look at the log file for error information, which is usually saved
at C:\jboss-4.2.3.GA\server\default\log\server.log? Remember you need to generate the
error looking\opening the log. As EDAS2 evolves we will be adding more informative error messages.
In this particular case looking at the log file solved the problem - which was a database connection issue.

Community Forum :: Error Messages that are of no help

Tue, 28 Apr 2009 10:01:18 -0400

By: sroland

I am receiving an error message that is of no help. The message is

Error Encountered
Unexpected error, please try again

The message provides me no direction as to what the issue is. This message is currently what I am receiving after the initial login for each screen of the application I enter. The standard senerio applies here, "it was working, what changed". JBoss is running hence the login screen appearing. The database is up and running.

Is there a log that is produced that I can be directed to that will provide me a direction to go to solve my issue?

Community Forum :: Running EDAS2 on Tomcat 6.0

Mon, 13 Apr 2009 13:45:32 -0400

By: dangandhi

I was able to run EDAS2 on Tomcat 6.0 with Oracle 9i & JDK 1.5.Here are the changes required:

1)First of all i had to copy considerable amount of jars into the lib of my tomcat as the compiled version nor the source code in SourceForge do not cover all the libraries.Here is the list(some might not be required):

asm.jar
commons-digester.jar
el-api.jar
hsqldb.jar
all the libraries from Embedded JBOSS package (FYI i am not using Tomcat with EMbedded JBOSS,just using the libraries)
all the libraries from JBOSS SEAM package
jsf-api.jar
jsf-facelets.jar
jsf-impl.jar
jsp-api.jar
jstl-1.1.2.jar
ojdbc14.jar for oracle 9i & JDK 1.5
servlet-api.jar
wstx.jar

2)Changed Hibernate dialect to Oracle 9i in persistence.xml
3)Changed transaction type from “JTA” to “RESOURCE_LOCAL” in persistence.xml
4)Commented transaction manager lookup class property in persistence.xml
5)Added the following line in Components.xml
<transaction:entity-transaction entity-manager="#{entityManager}"/>
Note: Don’t forget to add appropriate name space for the above tag.
6)Defining datasources differs in Tomcat when compared to JBOSS,so you either have to mention JNDI datasource globally or at application level.I could not get the application working by mentioning the datasources at application context level,so i had to mention them at the server level.Dont forget to add the datasource to the web.xml and also change the datasource references in persistence.xml and component.xml to the JNDI ones.
7)The report paths in components.xml can be either absolute or relative.I used relative.Please make sure that you create the appropriate folders otherwise the reports feature throws an exception.
8)Get your own google key if you are using a different URL and the google key usage syntax has changed little bit,change is in bold:
<component name="gmap">
<property name="key">http://maps.google.com/maps?file=api&v=2&sensor=false&key=ABQIAAAAKzQepJ4xyGVgCteyOFBqWxRuDbn5gfLKH-D3d6mkiv5tP6hBmRQV42HcD_woYUf_Ofo4Dtb908Pq1A</property>
</component>

Sensor value needs to be either false or true,please read google documentation to find out what sensor parameter is meant for.

Note:Most of the errors which you run into while deploying is mostly because of missing jars.So make sure you have all the jars required.

Community Forum :: Re: Action button styling not working in IE6

Sat, 11 Apr 2009 15:28:19 -0400

By: jcz

We are not sure exactly what you are seeing. We did notice some issues with styling under IE6 ourselves that were due to RichFaces support in the version that EDAS2 uses. We no longer use IE6 and so it is not an issue for us. Is it merely cosmetic?

Can you post what you did to run EDAS2 under Tomcat?