Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Gemini » Gemini JPA Getting Started Sample App(Gemini JPA Getting Started Sample App)
Gemini JPA Getting Started Sample App [message #780514] Wed, 18 January 2012 12:22 Go to next message
Stijn Deroo is currently offline Stijn Deroo
Messages: 4
Registered: January 2012
Junior Member
Hi,

I'm trying to run the sample application contained in the latest gemini jpa download (gemini-jpa-1.0.0.RELEASE.zip)

I followed the getting started guide, but only changed the jdbc driver of the sample app (org.eclipse.gemini.jpa.samples_1.0.0.RELEASE.jar) (to use an embedded driver instead):
<property name="javax.persistence.jdbc.driver" value="org.apache.derby.jdbc.EmbeddedDriver"/>
<property name="javax.persistence.jdbc.url" value="jdbc:derby:comics;create=true"/>

Following bundles are started:

javax.persistence 2.0.3
org.apache.derby 10.5.11
org.eclipse.gemini.dbaccess.derby 1.0.0
org.eclipse.gemini.jpa 1.0.0
org.eclipse.osgi 3.7.1
org.eclipse.persistence.antlr 2.3.1
org.eclipse.persistence.asm 2.3.1
org.eclipse.persistence.core 2.3.1
org.eclipse.persistence.jpa 2.3.1
osgi.enterprise 4.2

And off course the sample application bundle (org.eclipse.gemini.jpa.samples).

When running this configuration, I get following error trace:

osgi> Gemini DBAccess Derby starting
Gemini JPA Sample started
Gemini JPA Sample stopped
!SESSION 2012-01-18 13:23:30.509 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_23
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments:  -dev file:/home/stijn/workspace_jpatest/.metadata/.plugins/org.eclipse.pde.core/jpatest/dev.properties -os linux -ws gtk -arch x86 -consoleLog -console -clean

!ENTRY org.eclipse.osgi 2 0 2012-01-18 13:23:31.225
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-01-18 13:23:31.225
!MESSAGE Bundle org.eclipse.gemini.jpa.samples_1.2.0.RELEASE [2] was not resolved.
[EL Config]: ServerSession(17131806)--The access type for the persistent class [class model.account.Customer] is set to [FIELD].
[EL Config]: ServerSession(17131806)--The target entity (reference) class for the one to one mapping element [field account] is being defaulted to: class model.account.Account.
[EL Config]: ServerSession(17131806)--The access type for the persistent class [class model.account.Transaction] is set to [FIELD].
[EL Config]: ServerSession(17131806)--The target entity (reference) class for the many to one mapping element [field account] is being defaulted to: class model.account.Account.
[EL Config]: ServerSession(17131806)--The access type for the persistent class [class model.account.Account] is set to [FIELD].
[EL Config]: ServerSession(17131806)--The target entity (reference) class for the one to many mapping element [field txns] is being defaulted to: class model.account.Transaction.
[EL Config]: ServerSession(17131806)--The target entity (reference) class for the one to one mapping element [field customer] is being defaulted to: class model.account.Customer.
[EL Config]: ServerSession(17131806)--The alias name for the entity class [class model.account.Customer] is being defaulted to: Customer.
[EL Config]: ServerSession(17131806)--The table name for entity [class model.account.Customer] is being defaulted to: CUSTOMER.
[EL Config]: ServerSession(17131806)--The column name for element [id] is being defaulted to: ID.
[EL Config]: ServerSession(17131806)--The alias name for the entity class [class model.account.Transaction] is being defaulted to: Transaction.
[EL Config]: ServerSession(17131806)--The column name for element [id] is being defaulted to: ID.
[EL Config]: ServerSession(17131806)--The column name for element [amount] is being defaulted to: AMOUNT.
[EL Config]: ServerSession(17131806)--The column name for element [txTime] is being defaulted to: TXTIME.
[EL Config]: ServerSession(17131806)--The alias name for the entity class [class model.account.Account] is being defaulted to: Account.
[EL Config]: ServerSession(17131806)--The table name for entity [class model.account.Account] is being defaulted to: ACCOUNT.
[EL Config]: ServerSession(17131806)--The column name for element [id] is being defaulted to: ID.
[EL Config]: ServerSession(17131806)--The column name for element [balance] is being defaulted to: BALANCE.
[EL Config]: ServerSession(17131806)--The column name for element [dateCreated] is being defaulted to: DATECREATED.
[EL Config]: ServerSession(17131806)--The primary key column name for the mapping element [field account] is being defaulted to: ID.
[EL Config]: ServerSession(17131806)--The foreign key column name for the mapping element [account] is being defaulted to: ACCOUNT_ID.
[EL Config]: ServerSession(17131806)--The primary key column name for the mapping element [field account] is being defaulted to: ID.
[EL Config]: ServerSession(17131806)--The foreign key column name for the mapping element [account] is being defaulted to: ACCOUNT_ID.
Gemini JPA Sample started
[EL Config]: ServerSession(24678922)--The access type for the persistent class [class model.account.Customer] is set to [FIELD].
[EL Config]: ServerSession(24678922)--The target entity (reference) class for the one to one mapping element [field account] is being defaulted to: class model.account.Account.
[EL Config]: ServerSession(24678922)--The access type for the persistent class [class model.account.Transaction] is set to [FIELD].
[EL Config]: ServerSession(24678922)--The target entity (reference) class for the many to one mapping element [field account] is being defaulted to: class model.account.Account.
[EL Config]: ServerSession(24678922)--The access type for the persistent class [class model.account.Account] is set to [FIELD].
[EL Config]: ServerSession(24678922)--The target entity (reference) class for the one to many mapping element [field txns] is being defaulted to: class model.account.Transaction.
[EL Config]: ServerSession(24678922)--The target entity (reference) class for the one to one mapping element [field customer] is being defaulted to: class model.account.Customer.
[EL Config]: ServerSession(24678922)--The alias name for the entity class [class model.account.Customer] is being defaulted to: Customer.
[EL Config]: ServerSession(24678922)--The table name for entity [class model.account.Customer] is being defaulted to: CUSTOMER.
[EL Config]: ServerSession(24678922)--The column name for element [id] is being defaulted to: ID.
[EL Config]: ServerSession(24678922)--The alias name for the entity class [class model.account.Transaction] is being defaulted to: Transaction.
[EL Config]: ServerSession(24678922)--The column name for element [id] is being defaulted to: ID.
[EL Config]: ServerSession(24678922)--The column name for element [amount] is being defaulted to: AMOUNT.
[EL Config]: ServerSession(24678922)--The column name for element [txTime] is being defaulted to: TXTIME.
[EL Config]: ServerSession(24678922)--The alias name for the entity class [class model.account.Account] is being defaulted to: Account.
[EL Config]: ServerSession(24678922)--The table name for entity [class model.account.Account] is being defaulted to: ACCOUNT.
[EL Config]: ServerSession(24678922)--The column name for element [id] is being defaulted to: ID.
[EL Config]: ServerSession(24678922)--The column name for element [balance] is being defaulted to: BALANCE.
[EL Config]: ServerSession(24678922)--The column name for element [dateCreated] is being defaulted to: DATECREATED.
[EL Config]: ServerSession(24678922)--The primary key column name for the mapping element [field account] is being defaulted to: ID.
[EL Config]: ServerSession(24678922)--The foreign key column name for the mapping element [account] is being defaulted to: ACCOUNT_ID.
[EL Config]: ServerSession(24678922)--The primary key column name for the mapping element [field account] is being defaulted to: ID.
[EL Config]: ServerSession(24678922)--The foreign key column name for the mapping element [account] is being defaulted to: ACCOUNT_ID.
[EL Info]: ServerSession(24678922)--EclipseLink, version: Eclipse Persistence Services - 2.3.1.v20110908-r10021
[EL Config]: ServerSession(24678922)--Connection(26625789)--connecting(DatabaseLogin(
	platform=>DerbyPlatform
	user name=> ""
	connector=>JNDIConnector datasource name=>null
))
[EL Config]: ServerSession(24678922)--Connection(15860788)--Connected: jdbc:derby:comics
	User: APP
	Database: Apache Derby  Version: 10.5.1.1 - (764942)
	Driver: Apache Derby Embedded JDBC Driver  Version: 10.5.1.1 - (764942)
[EL Config]: ServerSession(24678922)--Connection(15865423)--connecting(DatabaseLogin(
	platform=>DerbyPlatform
	user name=> ""
	connector=>JNDIConnector datasource name=>null
))
[EL Config]: ServerSession(24678922)--Connection(27750143)--Connected: jdbc:derby:comics
	User: APP
	Database: Apache Derby  Version: 10.5.1.1 - (764942)
	Driver: Apache Derby Embedded JDBC Driver  Version: 10.5.1.1 - (764942)
[EL Info]: ServerSession(24678922)--Accounts_nonJtaDataSource=33440105 login successful
[EL Fine]: ServerSession(24678922)--Connection(24803078)--ALTER TABLE CUSTOMER DROP CONSTRAINT CUSTOMERACCOUNT_ID
[EL Fine]: ServerSession(24678922)--Connection(11369856)--ALTER TABLE ACCT_TXN DROP CONSTRAINT ACCT_TXNACCOUNT_ID
[EL Fine]: ServerSession(24678922)--Connection(13743917)--DROP TABLE ACCOUNT
[EL Fine]: ServerSession(24678922)--Connection(6200759)--CREATE TABLE ACCOUNT (ID INTEGER NOT NULL, BALANCE FLOAT, DATECREATED DATE, PRIMARY KEY (ID))
[EL Fine]: ServerSession(24678922)--Connection(5329507)--DROP TABLE CUSTOMER
[EL Fine]: ServerSession(24678922)--Connection(12793227)--CREATE TABLE CUSTOMER (ID INTEGER NOT NULL, ADDR VARCHAR(255), FNAME VARCHAR(255), LNAME VARCHAR(255), ACCOUNT_ID INTEGER, PRIMARY KEY (ID))
[EL Fine]: ServerSession(24678922)--Connection(11800934)--DROP TABLE ACCT_TXN
[EL Fine]: ServerSession(24678922)--Connection(6546787)--CREATE TABLE ACCT_TXN (ID INTEGER NOT NULL, AMOUNT FLOAT, OP INTEGER, TXTIME TIME, ACCOUNT_ID INTEGER, PRIMARY KEY (ID))
[EL Fine]: ServerSession(24678922)--Connection(31596370)--ALTER TABLE CUSTOMER ADD CONSTRAINT CUSTOMERACCOUNT_ID FOREIGN KEY (ACCOUNT_ID) REFERENCES ACCOUNT (ID)
[EL Fine]: ServerSession(24678922)--Connection(11970262)--ALTER TABLE ACCT_TXN ADD CONSTRAINT ACCT_TXNACCOUNT_ID FOREIGN KEY (ACCOUNT_ID) REFERENCES ACCOUNT (ID)
[EL Fine]: ServerSession(24678922)--Connection(29083513)--CREATE TABLE SEQUENCE (SEQ_NAME VARCHAR(50) NOT NULL, SEQ_COUNT DECIMAL(15), PRIMARY KEY (SEQ_NAME))
[EL Fine]: ServerSession(24678922)--VALUES(1)
[EL Warning]: ServerSession(24678922)--Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.1.v20110908-r10021): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Table/View 'SEQUENCE' already exists in Schema 'APP'.
Error Code: 30000
Call: CREATE TABLE SEQUENCE (SEQ_NAME VARCHAR(50) NOT NULL, SEQ_COUNT DECIMAL(15), PRIMARY KEY (SEQ_NAME))
Query: DataModifyQuery(sql="CREATE TABLE SEQUENCE (SEQ_NAME VARCHAR(50) NOT NULL, SEQ_COUNT DECIMAL(15), PRIMARY KEY (SEQ_NAME))")
[EL Fine]: ServerSession(24678922)--Connection(28681226)--DELETE FROM SEQUENCE WHERE SEQ_NAME = SEQ_GEN
[EL Fine]: ServerSession(24678922)--Connection(13261823)--SELECT * FROM SEQUENCE WHERE SEQ_NAME = SEQ_GEN
[EL Fine]: ServerSession(24678922)--Connection(28926916)--INSERT INTO SEQUENCE(SEQ_NAME, SEQ_COUNT) values (SEQ_GEN, 0)
[EL Fine]: ClientSession(6040101)--Connection(13823905)--UPDATE SEQUENCE SET SEQ_COUNT = SEQ_COUNT + ? WHERE SEQ_NAME = ?
[EL Fine]: ClientSession(6040101)--Connection(13823905)--	bind => [50, SEQ_GEN]
[EL Fine]: ClientSession(6040101)--Connection(13823905)--SELECT SEQ_COUNT FROM SEQUENCE WHERE SEQ_NAME = ?
	bind => [SEQ_GEN]
[EL Fine]: ClientSession(6040101)--Connection(21018877)--INSERT INTO ACCOUNT (ID, BALANCE, DATECREATED) VALUES (?, ?, ?)
[EL Fine]: ClientSession(6040101)--Connection(21018877)--	bind => [2, 100.0, 2012-01-18]
[EL Fine]: ClientSession(6040101)--Connection(21018877)--INSERT INTO CUSTOMER (ID, ADDR, FNAME, LNAME, ACCOUNT_ID) VALUES (?, ?, ?, ?, ?)
[EL Fine]: ClientSession(6040101)--Connection(21018877)--	bind => [1, 1034 KingFu Lane, Los Angeles, CA, Jackie, Chan, 2]
[EL Fine]: ServerSession(24678922)--Connection(10039205)--SELECT ID, BALANCE, DATECREATED FROM ACCOUNT

*** Account Report ***
Account: Account(2, Chan, Balance: $100.0)





Someone any clue?

Thanks in advance!
Stijn.

[Updated on: Wed, 18 January 2012 12:24]

Report message to a moderator

Re: Gemini JPA Getting Started Sample App [message #780540 is a reply to message #780514] Wed, 18 January 2012 14:17 Go to previous messageGo to next message
Michael Keith is currently offline Michael Keith
Messages: 215
Registered: July 2009
Senior Member
Hi Stijn,

The trace shows that in fact the sample ran fine Smile. Most of the output is the JPA provider stating the defaults that it is applying to the mappings, and then you see the SQL that it generates, and lastly the final line is the sample output.

The only error that shows up is from the sequence table creation, and that is quite normal when the sequence table already exists (i.e. if this was not the first time the app was run).

-Mike
Re: Gemini JPA Getting Started Sample App [message #780542 is a reply to message #780540] Wed, 18 January 2012 14:32 Go to previous messageGo to next message
Stijn Deroo is currently offline Stijn Deroo
Messages: 4
Registered: January 2012
Junior Member
Mike,

Thanks for your answer.

But why is following text shown in the beginning?
!SESSION 2012-01-18 13:23:30.509 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_23
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments:  -dev file:/home/stijn/workspace_jpatest/.metadata/.plugins/org.eclipse.pde.core/jpatest/dev.properties -os linux -ws gtk -arch x86 -consoleLog -console -clean

!ENTRY org.eclipse.osgi 2 0 2012-01-18 13:23:31.225
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-01-18 13:23:31.225
!MESSAGE Bundle org.eclipse.gemini.jpa.samples_1.2.0.RELEASE [2] was not resolved.


And why do I see twice the message
Gemini JPA Sample started
?

Kind regards,
Stijn.
Re: Gemini JPA Getting Started Sample App [message #780561 is a reply to message #780542] Wed, 18 January 2012 16:02 Go to previous messageGo to next message
Michael Keith is currently offline Michael Keith
Messages: 215
Registered: July 2009
Senior Member
The first part is, of course, just some Equinox printing out some of its config info.
If the samples bundle containing a persistence unit happens to be started before the Gemini JPA bundle then Gemini JPA will stop and restart it so that it can weave it. This could be what you are seeing. If you make sure that the samples bundle is started only after the Gemini JPA bundle then you should not see this occur.

-Mike
Re: Gemini JPA Getting Started Sample App [message #780562 is a reply to message #780561] Wed, 18 January 2012 16:04 Go to previous messageGo to next message
Michael Keith is currently offline Michael Keith
Messages: 215
Registered: July 2009
Senior Member
BTW, if you want to require the Gemini JPA bundle in the samples bundle then you would also guarantee the ordering, but that is often not what people see as a best practice...

-Mike
Re: Gemini JPA Getting Started Sample App [message #780567 is a reply to message #780562] Wed, 18 January 2012 16:20 Go to previous messageGo to next message
Stijn Deroo is currently offline Stijn Deroo
Messages: 4
Registered: January 2012
Junior Member
Thanks Mike,

It's more clear for me now.

KR,
Stijn.
Re: Gemini JPA Getting Started Sample App [message #783161 is a reply to message #780567] Wed, 25 January 2012 07:41 Go to previous messageGo to next message
Stijn Deroo is currently offline Stijn Deroo
Messages: 4
Registered: January 2012
Junior Member
Hi,

I'm still struggling with the run order of the different bundles. I can 't get rid of following message:


!ENTRY org.eclipse.osgi 2 0 2012-01-25 08:27:52.097
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-01-25 08:27:52.097
!MESSAGE Bundle org.eclipse.gemini.jpa.samples_1.2.0.RELEASE [9] was not resolved.
Gemini JPA Sample started


My run order can be seen in the attachment.

Someone any idea why this order is not respected? When I manually start the JPA Samples bundle, the message above is not printed, and everything runs fine.


osgi> Gemini DBAccess - MySQL JDBC starting
Gemini JPA Sample started
Gemini JPA Sample stopped
!SESSION 2012-01-25 08:27:51.382 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_23
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments:  -dev file:/home/stijn/workspace_jpatest (backup)/.metadata/.plugins/org.eclipse.pde.core/jpatest/dev.properties -os linux -ws gtk -arch x86 -consoleLog -console -clean

!ENTRY org.eclipse.osgi 2 0 2012-01-25 08:27:52.097
!MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists:
!SUBENTRY 1 org.eclipse.osgi 2 0 2012-01-25 08:27:52.097
!MESSAGE Bundle org.eclipse.gemini.jpa.samples_1.2.0.RELEASE [9] was not resolved.
Gemini JPA Sample started

*** Account Report ***
Account: Account(2, Chan, Balance: $100.0)



Kind regards,
Stijn.
Re: Gemini JPA Getting Started Sample App [message #788325 is a reply to message #783161] Wed, 01 February 2012 16:55 Go to previous messageGo to next message
Michael Keith is currently offline Michael Keith
Messages: 215
Registered: July 2009
Senior Member
Sorry, I was a little fast and loose with my language. I said start, but should have said resolve.
Resolving normally happens at install time, so the start level settings in Equinox are not necessarily going to affect the order in which the bundles are resolved.

On the other hand, start level will affect the sample bundle starting messages, so to make those go away you could make it start after all of the other bundles (set it to 10 or something instead of the default).
Re: Gemini JPA Getting Started Sample App [message #793734 is a reply to message #780514] Wed, 08 February 2012 13:44 Go to previous messageGo to next message
Rampal Missing name is currently offline Rampal Missing name
Messages: 3
Registered: December 2011
Junior Member
Hi,
I am trying to run the Gemini JPA Getting Started Sample App in oracle glassfish 3.1.1. But I am not able to run the Gemini JPA bundle itself. In the instructions , its mentioned that we should deploy the osgi enterprise jar prior to deploying the JPA gemini jar. However deploying the OSGI enterprise jar does not helps. The server throws the following exception :

[#|2012-02-08T19:04:29.218+0530|INFO|glassfish3.1.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=17;_ThreadName=fileinstall-D:\glassfish3\glassfish\domains\domain2/autodeploy/bundles/;|org.osgi.framework.BundleException: Unresolved constraint in bundle org.eclipse.gemini.jpa [327]: Unable to resolve 327.0: missing requirement [327.0] package; (&(package=org.osgi.framework)(version>=1.6.0))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3443)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1727)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:1175)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:1153)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.processAllBundles(DirectoryWatcher.java:1146)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:456)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:263)
|#]


However if i deploy the OSGI core jar, then the following exception is thrown :

[#|2012-02-08T19:05:57.375+0530|INFO|glassfish3.1.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=17;_ThreadName=fileinstall-D:\glassfish3\glassfish\domains\domain2/autodeploy/bundles/;|org.osgi.framework.BundleException: Activator start error in bundle org.eclipse.gemini.jpa [327].
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1882)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1752)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:1175)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:1153)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.processAllBundles(DirectoryWatcher.java:1146)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:456)
at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:263)
Caused by: java.lang.ClassCastException: org.eclipse.gemini.jpa.provider.EclipseLinkOSGiProvider cannot be cast to org.osgi.framework.BundleActivator
at org.apache.felix.framework.Felix.createBundleActivator(Felix.java:3693)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:1830)
... 7 more



I am running glassfish on felix platform. The following bundles are already running when i am deploying the Gemini JPA bundle:

javax.persistence 2.0.3

org.eclipse.persistence.antlr 2.3.1
org.eclipse.persistence.asm 2.3.1
org.eclipse.persistence.core 2.3.1
org.eclipse.persistence.jpa 2.3.1
osgi.enterprise 4.2
osgi.core 4.2

Please tell me if i have missed anything in deploying the bundles


Rampal


Re: Gemini JPA Getting Started Sample App [message #797768 is a reply to message #793734] Mon, 13 February 2012 21:56 Go to previous message
Michael Keith is currently offline Michael Keith
Messages: 215
Registered: July 2009
Senior Member
Gemini JPA requires v 4.3 of the OSGi Core spec (version 1.6 of the org.osgi.framework package). You will probably need to upgrade Felix in Glassfish to that version.

-Mike
Previous Topic:@ObjectTypeConverter + RCP = Error
Next Topic:Best Practices for Integration Testing OSGi (with Blueprint)?
Goto Forum:
  


Current Time: Wed Oct 01 18:21:35 GMT 2014

Powered by FUDForum. Page generated in 0.02570 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software