On Jun 13, 2007, at 8:58 PM, Avorcor wrote:
Well, that sure did fix that in a hurry. Thank you.
Now, if I may, one final question. Now that my session bean is
deployed,
aren't I supposed to be able to access it as web service through
EJB? If
so, what do I need to do to make that happen?
sacrifice some chickens in the right order :-) ?
You need to do something to indicate what the interface it's exposing
as a web service is. There's a way to do this with annotations but
I'm not sure exactly what it is. I'm also not sure if you have to
provide a wsdl file or if it can be generated from the interface, nor
how to specify the wsdl file location. Hopefully someone who knows
will tell you more.
thanks
david jencks
Thank you again.
JP
djencks wrote:
You need a geronimo plan for your (ejb? ear? app) that includes the
jms module you have deployed as a parent, otherwise the references
won't be able to be resolved.
Also we ignore the mappedName, you should specify the name and make
sure it's the same as what's in the jms module plan.
Hope this helps
david jencks
On Jun 13, 2007, at 8:27 PM, Avorcor wrote:
Okay, I tried to find a similar situation as this on this forum and
on the
web, but have not had any luck.
I am using Geroimo 2.0M5
I have deployed a new ActiveMQ Resource Adapter with 2 queues and 1
topic.
The factory name is Factory1
I have a single session bean that publishes to a JMS queue. The
bean has
one method publishAsset(), which performs the publishing act to the
queue.
This is a stateless session bean.
it is declared with
@Stateless
@Remote( { AssetRecordRemote.class })
I have a connection factory object declared in my code:
@Resource(mappedName = "java:/comp/env/jms/Factory1")
ConnectionFactory
connectionFactory;
The package this is in is called com.avorcor.fm
The bean name is AssetSessionBean
I jar this up with my remote interface and call
deploy AssetSessionBean.jar
I get an error deploying:
Error: Unable to distribute AssetSessionBean.jar:
org.apache.geronimo.common.DeploymentException: Unable to
resolve
resource reference
com.avorcor.fm.AssetSessionBean/connectionFactory'
(Could not auto-map to resource. Try adding a resource-ref
mapping
to your Geronimo deployment plan.
If I remove all references to JMS, this will deploy just fine.
Although, it
deploys in the default package instead of com.avorcor.fm . I would
like to
hear thoughts on this as well if anyone knows, but my primary
concern is for
trying to understand why Geronimo cannot find the resource
reference and
what I could try to correct this situation.
Thank you.
--
View this message in context: http://www.nabble.com/Unable-to-
resolve-resource-reference-on-3.0-with-annotations-
tf3919298s134.html#a11113134
Sent from the Apache Geronimo - Users mailing list archive at
Nabble.com.
--
View this message in context: http://www.nabble.com/Unable-to-
resolve-resource-reference-on-3.0-with-annotations-
tf3919298s134.html#a11113427
Sent from the Apache Geronimo - Users mailing list archive at
Nabble.com.
