December 2006 - jboss-user - Jboss List Archives

by dviersel

I forgot to mention that I updated the dependencies list on the wiki. As with the ear-scoped libraries. Ant 1.7.0 now provides support for auto-generating the manifest entries. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995819#3995819 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995819

19 years, 4 months

1
0
0 / 0

[EJB 3.0] - Re: Queries work, persist does not work, in a Servlet

by SmokingAPipe

Ha, I figured this out. I need to do EntityTransaction transaction = entityManager.getTransaction(); | transaction.begin(); | entityManager.persist(...); | transaction.commit(); | entityManager.close(); Is that the right way to do it? It works! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995818#3995818 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995818

19 years, 4 months

1
0
0 / 0

[JBoss Seam] - Re: Vacation

by thejavafreak

Merry Christmas. Have a great break Thanks for all the hardwork for creating great products such as Seam and Hibernate View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995817#3995817 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995817

19 years, 4 months

1
0
0 / 0

[EJB 3.0] - Queries work, persist does not work, in a Servlet

by SmokingAPipe

Strange strange problem: I have a Servlet. Within this Servlet I get a hold of a EntityManager like this: Inside of init: entityManagerFactory = Persistence.createEntityManagerFactory(persistenceContextName); And then in the doPost() method, I get an actual EntityManager using the obvious entityManagerFactory method. Strange thing, every time I try to persist an object using this EntityManager, nothing happens. No error, nothing, but nothing is persisted. But I can do queries with it and get the expected results! Is there any explanation for this? This is all in JBoss 4.0.5. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995816#3995816 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995816

19 years, 4 months

1
0
0 / 0

[JBossCache] - Re: java.lang.RuntimeException: java.lang.NoSuchMethodExcept

by ben.wang＠jboss.com

Can you also please double check your jboss-aop-jdk50.jar and jboss-aspect-library-jdk50.jar version from manifest? (Or if you are using jdk1.5, why don't you try the ejb3 bundle of which pre-compiled in JDK5?) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995815#3995815 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995815

19 years, 4 months

1
0
0 / 0

[JBoss jBPM] - Re: jBPM 3.1 + Spring 2.0 + Tomcat 5 + TX demo app

by wanglg

Thank you! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995814#3995814 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995814

19 years, 4 months

1
0
0 / 0

[JBossCache] - Re: PojoCache 2.0: New tree structure, optimistic locking &

by ben.wang＠jboss.com

It is not that servere in 1.4 because __JBossInternal__ is used only for shared references. So if there is creation of shared reference POJO under concurrent tx, then it will rollback. Otherwise, thing as usual. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995811#3995811 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995811

19 years, 4 months

1
0
0 / 0

[JBoss jBPM] - Re: Sending Emails?

by Saviola

See jBPM 3.2 in the CVS. It has build-in functionality for sending emails. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995810#3995810 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995810

19 years, 4 months

1
0
0 / 0

[Messaging, JMS & JBossMQ] - Error persisting message in DB2

by kaobe

Hi there! I have a JBoss 4.0.3 SP1 that does JMS with MDBs. The persistance is done with DB2. There is a message sent to a topic, an MDB reacts and - as a result - sends another message to a Queue. The first message is being sent and received, it is being saved in the database (jms_messages). When the answer message should be saved it is being sent and JBoss tries to store it, but gets an SQL error from DB2, because the unique index defined in deploy/jms/-jdbc2-service.xml for the fields txop and txid is being violated. There is no transaction running, that's why the values are null and 'A' both for the already stored message for the topic and the new one for the queue. No my question: is this unique index neccessary? I have dropped it from the database for a test and it seemed to work. So I would like to know why there is such an index. The funny thing is, it worked with hsqldb (with the index). Does that mean hsqldb violates the index definition or is there some other reason for this behaviour? Thanks a lot for your help! I wish everyone of you merry christmas and a happy new year! Bye, Peter View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995808#3995808 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995808

19 years, 4 months

1
0
0 / 0

[Messaging, JMS & JBossMQ] - Howto connect a EJB3 MDB to a remote queue?

by estiedi

Hi, I need to make a EJB3 MDB that listens for messages coming from another JBoss server. I'm pretty new to JBoss and an intense googling for examples and tutorials wasn't very helpful for me. Especially the possibility of doing things several different ways is confusing. Also it looks like it changes quite a lot between minor versions? (I'm currently using JBoss 4.0.5) Anyway, so far I configured a JMSProviderLoader in jms-ds.xml: <mbean code="org.jboss.jms.jndi.JMSProviderLoader" | name="jboss.mq:service=JMSProviderLoader,name=RemoteMQProvider,server=192.168.100.10"> | <attribute name="ProviderName">ISJMSProvider</attribute> | <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute> | <attribute name="QueueFactoryRef">XAConnectionFactory</attribute> | <attribute name="TopicFactoryRef">XAConnectionFactory</attribute> | <attribute name="Properties"> | java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory | java.naming.factory.url.pkgs=org.jnp.interfaces | java.naming.provider.url=192.168.100.10:25199 | </attribute> | </mbean> and an invoker proxy in the ejb jboss.xml: | <message-driven> | <ejb-name>TestMDB</ejb-name> | <destination-jndi-name>queue/remotequeue</destination-jndi-name> | <invoker-bindings> | <invoker> | <invoker-proxy-binding-name>TextMDBInvoker</invoker-proxy-binding-name> | </invoker> | </invoker-bindings> | </message-driven> | </enterprise-beans> | | <invoker-proxy-bindings> | <invoker-proxy-binding> | <name>TextMDBInvoker</name> | <invoker-mbean>does-not-matter</invoker-mbean> | <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory> | <proxy-factory-config> | <JMSProviderAdapterJNDI>ISJMSProvider</JMSProviderAdapterJNDI> | <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI> | <MinimumSize>1</MinimumSize> | <MaximumSize>15</MaximumSize> | <KeepAliveMillis>30000</KeepAliveMillis> | <MaxMessages>1</MaxMessages> | <MDBConfig> | <ReconnectIntervalSec>5</ReconnectIntervalSec> | <DLQConfig> | <DestinationQueue>queue/DLQ</DestinationQueue> | <MaxTimesRedelivered>10</MaxTimesRedelivered> | <TimeToLive>0</TimeToLive> | </DLQConfig> | </MDBConfig> | </proxy-factory-config> | </invoker-proxy-binding> | </invoker-proxy-bindings> | But now, how do I configure my EJB3 MDB to connect to this remote queue? Also the remote JBoss server is version 3. I have been told that this should be no problem. But is it really no problem when using EJB3? All tips and hints are greatly appreciated. D. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3995806#3995806 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3995806

19 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user December 2006