Using a jpa endpoint with no entityClassName

[fordm <fo...@gmail.com>]

Hi,

The URI format for a jpa endpoint is:

jpa:[entityClassName][?options]

and according to  Apache Camel:JPA <http://camel.apache.org/jpa.html>  , for
sending to the endpoint, the entityClassName is optional.

So I would expect the following route to successfully persist a message
(that contains a known entity):

<route>
    <from uri="activemq:my-queue" />
    <to uri="jpa:" />
</route>

Can someone tell me what I'm missing please?

Thanks


Martin



--
View this message in context: http://camel.465427.n5.nabble.com/Using-a-jpa-endpoint-with-no-entityClassName-tp5735854.html
Sent from the Camel - Users mailing list archive at Nabble.com.

RE: Using a jpa endpoint with no entityClassName

[cy...@barclays.com]

®®±³µ¥£¢Úàõøüÿ

-----Original Message-----
From: Bilgin Ibryam [mailto:bibryam@gmail.com] 
Sent: Thursday, July 18, 2013 3:22 PM
To: users@camel.apache.org
Subject: Re: Using a jpa endpoint with no entityClassName

Hi Martin,

just use dummy class name (like jpa://foo ) and make sure the message body contains one or many entity instances

Bilgin




On 18 July 2013 16:37, fordm <fo...@gmail.com> wrote:

> Hi,
>
> The URI format for a jpa endpoint is:
>
> jpa:[entityClassName][?options]
>
> and according to  Apache Camel:JPA <http://camel.apache.org/jpa.html>  
> , for sending to the endpoint, the entityClassName is optional.
>
> So I would expect the following route to successfully persist a 
> message (that contains a known entity):
>
> <route>
>     <from uri="activemq:my-queue" />
>     <to uri="jpa:" />
> </route>
>
> Can someone tell me what I'm missing please?
>
> Thanks
>
>
> Martin
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Using-a-jpa-endpoint-with-no-entityC
> lassName-tp5735854.html Sent from the Camel - Users mailing list 
> archive at Nabble.com.
>
_______________________________________________

This message is for information purposes only, it is not a recommendation, advice, offer or solicitation to buy or sell a product or service nor an official confirmation of any transaction. It is directed at persons who are professionals and is not intended for retail customer use. Intended for recipient only. This message is subject to the terms at: www.barclays.com/emaildisclaimer.

For important disclosures, please see: www.barclays.com/salesandtradingdisclaimer regarding market commentary from Barclays Sales and/or Trading, who are active market participants; and in respect of Barclays Research, including disclosures relating to specific issuers, please see http://publicresearch.barclays.com.

_______________________________________________

Re: Using a jpa endpoint with no entityClassName

[Bilgin Ibryam <bi...@gmail.com>]

Hi Martin,

just use dummy class name (like jpa://foo ) and make sure the message body
contains one or many entity instances

Bilgin




On 18 July 2013 16:37, fordm <fo...@gmail.com> wrote:

> Hi,
>
> The URI format for a jpa endpoint is:
>
> jpa:[entityClassName][?options]
>
> and according to  Apache Camel:JPA <http://camel.apache.org/jpa.html>  ,
> for
> sending to the endpoint, the entityClassName is optional.
>
> So I would expect the following route to successfully persist a message
> (that contains a known entity):
>
> <route>
>     <from uri="activemq:my-queue" />
>     <to uri="jpa:" />
> </route>
>
> Can someone tell me what I'm missing please?
>
> Thanks
>
>
> Martin
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Using-a-jpa-endpoint-with-no-entityClassName-tp5735854.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>