[JBoss and NetBeans] - Re: Netbeans 6, Java Persistence API, Web Service using Anno
by jsolderitsch
"phejl" wrote : I some did more investigation with jboss 4.2.2 and jboss 5 beta2, here is what I observed (don't take it as an unchangeable fact).
| With jboss 4 it seems to me that PersistentContext in servlet or webservice is ignored completely (jboss 4 is not ee 5 certified - provides ejb3 and ee5 web apps, however not sure if wired properly).
| When using jboss 5 server noticed the annotation however wasn't able to load the proper context (maybe really problem with wiring jpa and web, since it is still beta).
|
| Maybe somebody from jboss could tell you more...
| P.
Thanks for doing some checking.
I have been trying some of the Seam 2.0.0 demos (deploying to my 4.2.2 JBoss) and tutorials and ran seam-gen using my database.
I got this to work. And in the set of generated files I see a persistence.xml and a components.xml.
I think I see some interesting bits:
In the generated persistence.xml I see:
<persistence-unit name="AfmsttModernizationSeam">
| <provider>org.hibernate.ejb.HibernatePersistence</provider>
| <jta-data-source>java:/AfmsttModernizationSeamDatasource</jta-data-source>
| <properties>
| <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>
| <property name="hibernate.hbm2ddl.auto" value="validate"/>
| <property name="hibernate.show_sql" value="true"/>
| <property name="hibernate.format_sql" value="true"/>
| <property name="jboss.entity.manager.factory.jndi.name" value="java:/AfmsttModernizationSeamEntityManagerFactory"/>
| </properties>
| </persistence-unit>
and in components.xml I see:
<persistence:managed-persistence-context name="entityManager"
| auto-create="true"
| persistence-unit-jndi-name="java:/AfmsttModernizationSeamEntityManagerFactory"/>
|
These seem like config options that may help the wiring to complete the circuit if I add them in the right place in my war file.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109438#4109438
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109438
18 years, 4 months
[JBoss Seam] - Re: Activation of SFSB and removal of it by Seam question
by asookazian
"pete.muir(a)jboss.org" wrote : "asookazian" wrote : Is it safe to assume, then, that @In(create=true) will only instantiate a session-scoped SFSB once per session from a conversation-scoped SFSB as long as it is not destroyed somehow or nulled after the first instantiation?
|
| Yes.
|
| Post the *whole* source of the SecurityAuditAction, I think there must be something funny about your use of Seam logging.
A couple weeks back I tried removing all references to the Seam logger in both SFSB's (there are no other POJO's other than entity beans) and the exception still occurred... I have no clue what it is but maybe it's the instance variable objects that can't be serialized b/c they're not marked transient and do not implement Serializable??
I posted a question on the java sun EJB3 forum asking what happens if the ejb container tries to passivate/serialize a SFSB with instance variables that are not marked transient and are not serializable and no response...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109436#4109436
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109436
18 years, 4 months
[JCA/JBoss] - Re: MSSQL XA datasource throws RollbackException on cluster
by vickyk
anonymous wrote : Could not create table
| with SQL: CREATE TABLE JMS_MESSAGES (MESSAGEID INTEGER NOT NULL, DESTINATION VARCHAR(150) NOT NULL,
| TXID INTEGER, TXOP CHAR(1), MESSAGEBLOB IMAGE)
| com.microsoft.sqlserver.jdbc.SQLServerException: There is already an object named 'JMS_MESSAGES' in
| the database.
Looks like the table has already been created earlier , can you check this form the Jboss messaging forums ?
BTW , you can delete the tables manually from the MSSQL and then try restarting the Jboss ... that might work .
anonymous wrote : Is there something that I am doing wrong?
You should understand that with Jboss4.2 version the older TM has been replaced with new Arjuna TM that supports RecoveryManager feature which was missing in earlier old TM .
So TM related logging should be done on com.arjuna.ats.internal.jta .
Ronald , why don't you test a simple jsp and get it verified first that datasource is configured properly , the DS seems to be configured properly .
I don't see the issue here with Jboss JCA , the configurations seems to be ok ... let us get it verified from the test jsp .
Alternatively you can use in the ds configuration and see from the logs if it doesn't show errors .
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4109429#4109429
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4109429
18 years, 4 months