January 2009 - jboss-user - Jboss List Archives

[Microcontainer] - Re: Parsing Error run DZone_1_0 demos

by alesj

"Gary Marsh" wrote : | Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Failed to resolve schema nsURI=urn:jboss:spring-beans:2.0 location=beans | This means you're missing MC's spring-int lib in classpath. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200156#4200156 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200156

17 years, 3 months

1
0
0 / 0

[EJB 3.0] - Re: Looking up a PU from @PersistenceContext annotation

by wolfc

After injecting PersistenceUnitDependencyResolver, this piece of pseudo code should do the trick: String beanName = persistenceUnitDependencyResolver.resolvePersistenceUnitSupplier(deploymentUnit, persistenceUnitName); | PersistenceUnitDeployment deployment = lookup(beanName); | ManagedEntityManagerFactory managedFactory = deployment.getManagedFactory(); | return new InjectedEntityManagerFactory(managedFactory); Although PersistenceUnitDeployment is an internal. Maybe we should add a simple utility class to jpa-deployers. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200154#4200154 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200154

17 years, 3 months

1
0
0 / 0

[JBoss Messaging] - Re: Messaging gets stuck

by clebert.suconic＠jboss.com

anonymous wrote : Should we upgrade to Messaging-1.4.2? Yes.. I would suggest that... Followed by the upgrade on remoting as required by the installation section on 1.4.2 docs. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200152#4200152 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200152

17 years, 3 months

1
0
0 / 0

[EJB 3.0] - Re: Looking up a PU from @PersistenceContext annotation

by pete.muir＠jboss.org

Also, I have full access to MC at this point, so what I'm doing for @EJB injection is to lookup the EjbReferenceResolver MC bean and use it to get the JNDI name for the injection point. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200151#4200151 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200151

17 years, 3 months

1
0
0 / 0

[EJB 3.0] - Looking up a PU from @PersistenceContext annotation

by pete.muir＠jboss.org

I have a field/method annotated @PersistenceContext (not on an EJB) that I need to inject. I have full access to the field/method (declared type, annotation), and need a way to get the correct persistence unit from JBoss EJB3. This could be directly (return the correct object) or a JNDI reference. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200150#4200150 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200150

17 years, 3 months

1
0
0 / 0

[JBoss Messaging] - Re: MDBs failing to listen to remote topic/queues

by clebert.suconic＠jboss.com

The link you provided is for JBossMQ, right? Are you trying to connect to a remote JBossMQ? All you need to do is to change jms-ds.xml: <mbean code="org.jboss.jms.jndi.JMSProviderLoader" | name="jboss.jms:service=JMSProviderLoader,name=JMSProvider"> | <attribute name="ProviderName">DefaultJMSProvider</attribute> | <attribute name="ProviderAdapterClass"> | org.jboss.jms.jndi.JNDIProviderAdapter | </attribute> |  | <attribute name="FactoryRef">java:/XAConnectionFactory</attribute> |  | <attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute> |  | <attribute name="TopicFactoryRef">java:/XAConnectionFactory</attribute> |  | </mbean> | Assuming you are trying to use a remote JBossMessaging: The ConnectionFactory you use here should just be a remote CF (java:/ means local), and you should keep the properties accordingly to the remote node. If you also have MDBs connecting locally, you should duplicate the configs on jms-ds and make sure your MDB is using the correct adapter. For more question regarding this, you would be better on finding help at JCA forum or EJB forum. (MDB is an EJB/EJB3 component.. not JBossMessaging) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200149#4200149 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200149

17 years, 3 months

1
0
0 / 0

[JBoss Messaging] - Re: clientLeasePeriod for JMS clients (bisocket)

by gsanderson

Sorry, we're using whatever comes with JBoss 4.3.0EAP CP 03 I'm guessing that the ping requires a Java level response, so we should consider (potentially badly configured) GC pauses when setting this value ourselves. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200148#4200148 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200148

17 years, 3 months

1
0
0 / 0

[JBoss Cache: Core Edition] - Shunning

by lovelyliatroim

17 years, 3 months

1
0
0 / 0

[Microcontainer] - Re: Parsing Error run DZone_1_0 demos

by Gary Marsh

alesj; Just a Note: when I substitute the JBossAS library Jars for the MC Library jars in my classpath the error goes away. I last updated my MC 2.0.2GA download 12/04/08. Regards, GMarsh View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200145#4200145 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200145

17 years, 3 months

1
0
0 / 0

[Security & JAAS/JBoss] - Re: EJB3 and remote client EJB access

by danielen

Im using JBoss 4.3 EAP and have the same problem. Is there a solution for this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200144#4200144 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200144

17 years, 3 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 January 2009