Nabble - EasyBeans-user

Re: please provide a name property to EZBContainer services

2008-12-02T07:06:50Z

Guillaume Sauthier schrieb:

> ekke a écrit :
>> Guillaume Sauthier schrieb:
>>> ekke a écrit :
>>>> Guillaume,
>>>>
>>>> if you're working on properties for use by DS -
>>>> I'm having another question, where I got a problem to use DS instead
>>>> of ServiceTracker. Buts its not so important - in this case I can
>>>> live with the Tracker.
>>>>
>>>> EZB registers each BusinessInterface of EJBs as Service (and also as
>>>> ManagedService).
>>>> this works great and in my serviceTracker I got all those Services
>>>> using a filter
>>>>
>>>> final String filterDataManager = "("
>>>> +"service.pid"
>>>> + "="
>>>> + "*RemoteManagerI*Bean"
>>>> +")";
>>>>
>>>> then I'm getting the ManagedServices as I want
>>>>
>>>> using DS I tried different ways to get references to these
>>>> BusinessInterface - Services, but they aren't resolved by DS
>>>>
>>>> <reference name="fooEasybansBusinessInterface"
>>>> interface="org.ekkehard.foo.BlaBlaRemoteInterface"
>>>> bind="bindBlaBla"
>>>> unbind="unbindBlaBla"
>>>> cardinality="1..1"
>>>> />
>>>>
>>>> but listing the services from console I can see service
>>>> ManagedService, BlaBlaRemoteInterface
>>>>
>>>> any idea ?
>>>
>>> Hmmm, did you try with another SCR implementation ?
>> perhaps an idea ;-)
>>
>> ...or I made a mistake and will try it again in another separate bundle
>>
>> all done with eclipse 3.4.1 + equinox
>> (in 3.5M3 its easier because PDE tooling then supports DS)
>>
>> so you think too, that it should work ;-)
>
> there was some discussion on november on the osgi-dev list about DS/SCR
> implementations (felix / equinox) differences:
> https://mail.osgi.org/pipermail/osgi-dev/2008-November/001511.html
> Are you using Configuration admin to create new instance of your
> component ? Seems the guy was having problems with that...
>

thx for the info...
I'm only using equinox.ds which should find the Service registered from EZB

I'll let you know if I find it out...

ekke

> --G
>
>>
>> ekke
>>> --G
>>>
>>>>
>>>> ekke
>>>>
>>>> ekke schrieb:
>>>>> I'm just in the process to refactor my easybeans-riena-equinox
>>>>> enterprise server to use Declarative Services instead ServiceTracker
>>>>> and I run into a shopw-stopper:
>>>>>
>>>>> EZBContainer doesn't provide a name property,
>>>>> so couldn't create a target filter like
>>>>>
>>>>> <reference name="fooEZBContainer"
>>>>> interface="org.ow2.easybeans.api.EZBContainer"
>>>>> cardinality="1..1"
>>>>> target="(name=org.ekkehard.foo.datamanager.bean)"
>>>>> />
>>>>> in a ServiceTracker I can use the getName() method, but I found
>>>>> no way to access the name from a Filter
>>>>>
>>>>> if I list the services from OSGI console I only get:
>>>>>
>>>>> {org.ow2.easybeans.api.EZBContainer}={service.id=249}
>>>>> Registered by bundle:
>>>>> initial@reference:file:../../../ekkehard/plugins/org.ekkehard.foo.datamanager.bean_1.0.0.jar/
>>>>>
>>>>> Bundles using service:
>>>>> initial@reference:file:../../../easyBeans/bundles/easybeans-core_1.1.0-M3-SNAPSHOT.jar/
>>>>>
>>>>>
>>>>> because I also dont find a way to get the name of the registering
>>>>> bundle from filter in target, it would be really great if you can
>>>>> provide an information to the service registry
>>>>>
>>>>> I opened JIRA EZB-324
>>>>>
>>>>> THX
>>>>>
>>>>> ekke
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>

Re: Re: please provide a name property to EZBContainer services

2008-12-02T06:59:05Z

ekke a écrit :

> Guillaume Sauthier schrieb:
>> ekke a écrit :
>>> Guillaume,
>>>
>>> if you're working on properties for use by DS -
>>> I'm having another question, where I got a problem to use DS instead
>>> of ServiceTracker. Buts its not so important - in this case I can
>>> live with the Tracker.
>>>
>>> EZB registers each BusinessInterface of EJBs as Service (and also as
>>> ManagedService).
>>> this works great and in my serviceTracker I got all those Services
>>> using a filter
>>>
>>> final String filterDataManager = "("
>>> +"service.pid"
>>> + "="
>>> + "*RemoteManagerI*Bean"
>>> +")";
>>>
>>> then I'm getting the ManagedServices as I want
>>>
>>> using DS I tried different ways to get references to these
>>> BusinessInterface - Services, but they aren't resolved by DS
>>>
>>> <reference name="fooEasybansBusinessInterface"
>>> interface="org.ekkehard.foo.BlaBlaRemoteInterface"
>>> bind="bindBlaBla"
>>> unbind="unbindBlaBla"
>>> cardinality="1..1"
>>> />
>>>
>>> but listing the services from console I can see service
>>> ManagedService, BlaBlaRemoteInterface
>>>
>>> any idea ?
>>
>> Hmmm, did you try with another SCR implementation ?
> perhaps an idea ;-)
>
> ...or I made a mistake and will try it again in another separate bundle
>
> all done with eclipse 3.4.1 + equinox
> (in 3.5M3 its easier because PDE tooling then supports DS)
>
> so you think too, that it should work ;-)

there was some discussion on november on the osgi-dev list about DS/SCR
implementations (felix / equinox) differences:
https://mail.osgi.org/pipermail/osgi-dev/2008-November/001511.html
Are you using Configuration admin to create new instance of your
component ? Seems the guy was having problems with that...

--G

>
> ekke
>> --G
>>
>>>
>>> ekke
>>>
>>> ekke schrieb:
>>>> I'm just in the process to refactor my easybeans-riena-equinox
>>>> enterprise server to use Declarative Services instead ServiceTracker
>>>> and I run into a shopw-stopper:
>>>>
>>>> EZBContainer doesn't provide a name property,
>>>> so couldn't create a target filter like
>>>>
>>>> <reference name="fooEZBContainer"
>>>> interface="org.ow2.easybeans.api.EZBContainer"
>>>> cardinality="1..1"
>>>> target="(name=org.ekkehard.foo.datamanager.bean)"
>>>> />
>>>> in a ServiceTracker I can use the getName() method, but I found
>>>> no way to access the name from a Filter
>>>>
>>>> if I list the services from OSGI console I only get:
>>>>
>>>> {org.ow2.easybeans.api.EZBContainer}={service.id=249}
>>>> Registered by bundle:
>>>> initial@reference:file:../../../ekkehard/plugins/org.ekkehard.foo.datamanager.bean_1.0.0.jar/
>>>>
>>>> Bundles using service:
>>>> initial@reference:file:../../../easyBeans/bundles/easybeans-core_1.1.0-M3-SNAPSHOT.jar/
>>>>
>>>>
>>>> because I also dont find a way to get the name of the registering
>>>> bundle from filter in target, it would be really great if you can
>>>> provide an information to the service registry
>>>>
>>>> I opened JIRA EZB-324
>>>>
>>>> THX
>>>>
>>>> ekke
>>>>
>>>>
>>>
>>>
>>>
>>
>
>
>

[Guillaume_Sauthier.vcf]

begin:vcard fn:Guillaume Sauthier n:Sauthier;Guillaume org:<a href="http://www.ow2.org"><img title="OW2" alt="OW2 Consortium" border="0" src="http://www.ow2.org/xwiki/bin/skin/XWiki/DefaultSkin/logoOW2.png" /></a> adr:;;;;;;France email;internet:guillaume.sauthier@... title:<a href="http://jonas.ow2.org">JOnAS Application Server</a> x-mozilla-html:TRUE url:http://jonas.ow2.org version:2.1 end:vcard

Re: [OSGI] unbundeling EZB core

2008-12-02T06:53:11Z

Guillaume Sauthier schrieb:

> ekke a écrit :
>> hi,
>>
>> I wanted to ask if you still are working on unbundling the
>> ezb-core-monster-bundle ;-)
>
> Not at the moment, but it's definitely the way we want to go.
> there will probably be some discussion before refactoring on this list,
> so stay in touch :)
>

sure ;-)

I know how hard it is - already spent some time trying to refactor this,
but gave up - was too hard without EZB - insider knowledge ;-)

ekke

> --G
>
>>
>> we talked about this some time ago and got the information,
>> that you have the vision to do this.
>> I spent some time to try it, but without success
>>
>> EZB is the best way at the momoent to integrate EJB3 into
>> an OSGI application - in contrast to ther solutions based
>> on OSGI where you already have to deploy to the server
>>
>> only really hard to manage is the ezb-core-bundle where
>> so many jar files are included.
>> this in no good OSGI practice
>>
>> ...only wanted to remember ;-)
>> I can imagine that this is no easy work
>>
>> ekke
>>
>>
>>
>

Re: please provide a name property to EZBContainer services

2008-12-02T06:47:18Z

Guillaume Sauthier schrieb:

> ekke a écrit :
>> Guillaume,
>>
>> if you're working on properties for use by DS -
>> I'm having another question, where I got a problem to use DS instead
>> of ServiceTracker. Buts its not so important - in this case I can live
>> with the Tracker.
>>
>> EZB registers each BusinessInterface of EJBs as Service (and also as
>> ManagedService).
>> this works great and in my serviceTracker I got all those Services
>> using a filter
>>
>> final String filterDataManager = "("
>> +"service.pid"
>> + "="
>> + "*RemoteManagerI*Bean"
>> +")";
>>
>> then I'm getting the ManagedServices as I want
>>
>> using DS I tried different ways to get references to these
>> BusinessInterface - Services, but they aren't resolved by DS
>>
>> <reference name="fooEasybansBusinessInterface"
>> interface="org.ekkehard.foo.BlaBlaRemoteInterface"
>> bind="bindBlaBla"
>> unbind="unbindBlaBla"
>> cardinality="1..1"
>> />
>>
>> but listing the services from console I can see service
>> ManagedService, BlaBlaRemoteInterface
>>
>> any idea ?
>
> Hmmm, did you try with another SCR implementation ?

perhaps an idea ;-)

...or I made a mistake and will try it again in another separate bundle

all done with eclipse 3.4.1 + equinox
(in 3.5M3 its easier because PDE tooling then supports DS)

so you think too, that it should work ;-)

ekke

> --G
>
>>
>> ekke
>>
>> ekke schrieb:
>>> I'm just in the process to refactor my easybeans-riena-equinox
>>> enterprise server to use Declarative Services instead ServiceTracker
>>> and I run into a shopw-stopper:
>>>
>>> EZBContainer doesn't provide a name property,
>>> so couldn't create a target filter like
>>>
>>> <reference name="fooEZBContainer"
>>> interface="org.ow2.easybeans.api.EZBContainer"
>>> cardinality="1..1"
>>> target="(name=org.ekkehard.foo.datamanager.bean)"
>>> />
>>> in a ServiceTracker I can use the getName() method, but I found
>>> no way to access the name from a Filter
>>>
>>> if I list the services from OSGI console I only get:
>>>
>>> {org.ow2.easybeans.api.EZBContainer}={service.id=249}
>>> Registered by bundle:
>>> initial@reference:file:../../../ekkehard/plugins/org.ekkehard.foo.datamanager.bean_1.0.0.jar/
>>>
>>> Bundles using service:
>>> initial@reference:file:../../../easyBeans/bundles/easybeans-core_1.1.0-M3-SNAPSHOT.jar/
>>>
>>>
>>> because I also dont find a way to get the name of the registering
>>> bundle from filter in target, it would be really great if you can
>>> provide an information to the service registry
>>>
>>> I opened JIRA EZB-324
>>>
>>> THX
>>>
>>> ekke
>>>
>>>
>>
>>
>>
>

Re: [OSGI] unbundeling EZB core

2008-12-02T06:43:41Z

ekke a écrit :
> hi,
>
> I wanted to ask if you still are working on unbundling the
> ezb-core-monster-bundle ;-)

Not at the moment, but it's definitely the way we want to go.
there will probably be some discussion before refactoring on this list,
so stay in touch :)

--G

>
> we talked about this some time ago and got the information,
> that you have the vision to do this.
> I spent some time to try it, but without success
>
> EZB is the best way at the momoent to integrate EJB3 into
> an OSGI application - in contrast to ther solutions based
> on OSGI where you already have to deploy to the server
>
> only really hard to manage is the ezb-core-bundle where
> so many jar files are included.
> this in no good OSGI practice
>
> ...only wanted to remember ;-)
> I can imagine that this is no easy work
>
> ekke
>
>
>

[Guillaume_Sauthier.vcf]

Re: Re: please provide a name property to EZBContainer services

2008-12-02T06:41:59Z

ekke a écrit :

> Guillaume,
>
> if you're working on properties for use by DS -
> I'm having another question, where I got a problem to use DS instead
> of ServiceTracker. Buts its not so important - in this case I can live
> with the Tracker.
>
> EZB registers each BusinessInterface of EJBs as Service (and also as
> ManagedService).
> this works great and in my serviceTracker I got all those Services
> using a filter
>
> final String filterDataManager = "("
> +"service.pid"
> + "="
> + "*RemoteManagerI*Bean"
> +")";
>
> then I'm getting the ManagedServices as I want
>
> using DS I tried different ways to get references to these
> BusinessInterface - Services, but they aren't resolved by DS
>
> <reference name="fooEasybansBusinessInterface"
> interface="org.ekkehard.foo.BlaBlaRemoteInterface"
> bind="bindBlaBla"
> unbind="unbindBlaBla"
> cardinality="1..1"
> />
>
> but listing the services from console I can see service
> ManagedService, BlaBlaRemoteInterface
>
> any idea ?

Hmmm, did you try with another SCR implementation ?
--G

>
> ekke
>
> ekke schrieb:
>> I'm just in the process to refactor my easybeans-riena-equinox
>> enterprise server to use Declarative Services instead ServiceTracker
>> and I run into a shopw-stopper:
>>
>> EZBContainer doesn't provide a name property,
>> so couldn't create a target filter like
>>
>> <reference name="fooEZBContainer"
>> interface="org.ow2.easybeans.api.EZBContainer"
>> cardinality="1..1"
>> target="(name=org.ekkehard.foo.datamanager.bean)"
>> />
>> in a ServiceTracker I can use the getName() method, but I found
>> no way to access the name from a Filter
>>
>> if I list the services from OSGI console I only get:
>>
>> {org.ow2.easybeans.api.EZBContainer}={service.id=249}
>> Registered by bundle:
>> initial@reference:file:../../../ekkehard/plugins/org.ekkehard.foo.datamanager.bean_1.0.0.jar/
>>
>> Bundles using service:
>> initial@reference:file:../../../easyBeans/bundles/easybeans-core_1.1.0-M3-SNAPSHOT.jar/
>>
>>
>> because I also dont find a way to get the name of the registering
>> bundle from filter in target, it would be really great if you can
>> provide an information to the service registry
>>
>> I opened JIRA EZB-324
>>
>> THX
>>
>> ekke
>>
>>
>
>
>

[Guillaume_Sauthier.vcf]

Re: please provide a name property to EZBContainer services

2008-12-02T03:22:47Z

Guillaume,

if you're working on properties for use by DS -
I'm having another question, where I got a problem to use DS instead of
ServiceTracker. Buts its not so important - in this case I can live with
the Tracker.

EZB registers each BusinessInterface of EJBs as Service (and also as
ManagedService).
this works great and in my serviceTracker I got all those Services
using a filter

final String filterDataManager = "("
+"service.pid"
+ "="
+ "*RemoteManagerI*Bean"
+")";

then I'm getting the ManagedServices as I want

using DS I tried different ways to get references to these
BusinessInterface - Services, but they aren't resolved by DS

<reference name="fooEasybansBusinessInterface"
interface="org.ekkehard.foo.BlaBlaRemoteInterface"
bind="bindBlaBla"
unbind="unbindBlaBla"
cardinality="1..1"
/>

but listing the services from console I can see service
ManagedService, BlaBlaRemoteInterface

any idea ?

ekke

ekke schrieb:

> I'm just in the process to refactor my easybeans-riena-equinox
> enterprise server to use Declarative Services instead ServiceTracker
> and I run into a shopw-stopper:
>
> EZBContainer doesn't provide a name property,
> so couldn't create a target filter like
>
> <reference name="fooEZBContainer"
> interface="org.ow2.easybeans.api.EZBContainer"
> cardinality="1..1"
> target="(name=org.ekkehard.foo.datamanager.bean)"
> />
>
> in a ServiceTracker I can use the getName() method, but I found no way
> to access the name from a Filter
>
> if I list the services from OSGI console I only get:
>
> {org.ow2.easybeans.api.EZBContainer}={service.id=249}
> Registered by bundle:
> initial@reference:file:../../../ekkehard/plugins/org.ekkehard.foo.datamanager.bean_1.0.0.jar/
>
> Bundles using service:
> initial@reference:file:../../../easyBeans/bundles/easybeans-core_1.1.0-M3-SNAPSHOT.jar/
>
>
> because I also dont find a way to get the name of the registering bundle
> from filter in target, it would be really great if you can provide an
> information to the service registry
>
> I opened JIRA EZB-324
>
> THX
>
> ekke
>
>

please provide a name property to EZBContainer services

2008-11-30T07:19:26Z

I'm just in the process to refactor my easybeans-riena-equinox
enterprise server to use Declarative Services instead ServiceTracker
and I run into a shopw-stopper:

EZBContainer doesn't provide a name property,
so couldn't create a target filter like

<reference name="fooEZBContainer"
interface="org.ow2.easybeans.api.EZBContainer"
cardinality="1..1"
target="(name=org.ekkehard.foo.datamanager.bean)"
/>

in a ServiceTracker I can use the getName() method, but I found no way
to access the name from a Filter

if I list the services from OSGI console I only get:

{org.ow2.easybeans.api.EZBContainer}={service.id=249}
Registered by bundle:
initial@reference:file:../../../ekkehard/plugins/org.ekkehard.foo.datamanager.bean_1.0.0.jar/

Bundles using service:
initial@reference:file:../../../easyBeans/bundles/easybeans-core_1.1.0-M3-SNAPSHOT.jar/

because I also dont find a way to get the name of the registering bundle
from filter in target, it would be really great if you can provide an
information to the service registry

I opened JIRA EZB-324

THX

ekke

Re: Re: Re: Re: Generate ID automatic

2008-11-27T05:02:22Z

Hi ,

You were right, Pedro. I change the entity field and all is working , now!

1) What should I do to alter the int field to a Long field? Since my database, at the moment, is recreated every time I start my application.

Thanks and Regards
Fernando

2008/11/26 Pedro Vieira da Silva <pedro.s.silva@...>

You have defined your field as long but the matching field in the database is an integer.

Either change the entity filed to int or change the column of the database table to be a long.

Pedro Silva
Software Engineer

Critical Software, S.A.
www.criticalsoftware.com

Fernando Freitas wrote:

I tried , but occurs this error... Follow Below:

Provided id of the wrong type. Expected: class java.lang.Long, got class java.lang.Integer

My code

private Long id;
@Id @GeneratedValue
public Long getId() {
return id;
}

1) Can you help me? What is this error?

Thanks

2008/11/26 ekke <ekkehard@... <mailto:ekkehard@...>>

so here's another one
working with Hibernate && (DB2 || HSQLDB || Oracle)

@Id
@GeneratedValue(strategy = GenerationType.TABLE)
@Column(name = "ADR_PK")
private long uPK;

you should read carefully the documentation about ID generation
from TopLink or Hibernate AND from your Database
and then decide

ekke

CSW - Sérgio Silva schrieb:

I Think this is what you are looking for:

….

private Long id;

@Id

@TableGenerator(name = "keyDFW", allocationSize = 1,
initialValue = 1)

@GeneratedValue(strategy = GenerationType.TABLE, generator =
"keyDFW")

public Long getId() {

…..

This is one approach of what you are looking for.

You can use a table or a sequence to auto generate the id!

A simple explanation (on TopLink JPA Implementation):
http://www.oracle.com/technology/products/ias/toplink/jpa/howto/id-generation.html

------------------------------------------------------------------------

*From:* Fernando Freitas [mailto:nandows@...
<mailto:nandows@...>]
*Sent:* quarta-feira, 26 de Novembro de 2008 13:53
*To:* easybeans@... <mailto:easybeans@...>

*Subject:* [easybeans] Generate ID automatic

Hi everybody,
Someone knows....
1) How Can I do to generate "ID automatically " using
easybeans with osgi?

Thanks and best Regards
Fernando Freitas

Re: Re: Re: Generate ID automatic

2008-11-26T12:00:34Z

You have defined your field as long but the matching field in the database is an
integer.

Either change the entity filed to int or change the column of the database table
to be a long.

Pedro Silva
Software Engineer

Critical Software, S.A.
www.criticalsoftware.com

Fernando Freitas wrote:

> I tried , but occurs this error... Follow Below:
>
>
>
> Provided id of the wrong type. Expected: class java.lang.Long, got class
> java.lang.Integer
>
>
> My code
>
> private Long id;
>
> @Id
> @GeneratedValue
> public Long getId() {
> return id;
> }
>
>
> 1) Can you help me? What is this error?
>
>
> Thanks
>
>
>
>
>
>
>
> 2008/11/26 ekke <ekkehard@...
> <mailto:ekkehard@...>>
>
> so here's another one
> working with Hibernate && (DB2 || HSQLDB || Oracle)
>
> @Id
> @GeneratedValue(strategy = GenerationType.TABLE)
> @Column(name = "ADR_PK")
> private long uPK;
>
> you should read carefully the documentation about ID generation
> from TopLink or Hibernate AND from your Database
> and then decide
>
> ekke
>
> CSW - Sérgio Silva schrieb:
>
> I Think this is what you are looking for:
>
>
> ….
>
>
> private Long id;
>
>
>
> @Id
>
> @TableGenerator(name = "keyDFW", allocationSize = 1,
> initialValue = 1)
>
> @GeneratedValue(strategy = GenerationType.TABLE, generator =
> "keyDFW")
>
> public Long getId() {
>
> …..
>
>
> This is one approach of what you are looking for.
>
>
> You can use a table or a sequence to auto generate the id!
>
>
> A simple explanation (on TopLink JPA Implementation):
> http://www.oracle.com/technology/products/ias/toplink/jpa/howto/id-generation.html
>
>
> ------------------------------------------------------------------------
>
> *From:* Fernando Freitas [mailto:nandows@...
> <mailto:nandows@...>]
> *Sent:* quarta-feira, 26 de Novembro de 2008 13:53
> *To:* easybeans@... <mailto:easybeans@...>
> *Subject:* [easybeans] Generate ID automatic
>
>
> Hi everybody,
> Someone knows....
> 1) How Can I do to generate "ID automatically " using
> easybeans with osgi?
>
>
> Thanks and best Regards
> Fernando Freitas
>
>
>

Re: Re: Generate ID automatic

2008-11-26T11:53:39Z

I tried , but occurs this error... Follow Below:

Provided id of the wrong type. Expected: class java.lang.Long, got class java.lang.Integer

My code

private Long id;

    @Id
    @GeneratedValue
    public Long getId() {
        return id;
    }

1) Can you help me? What is this error?

Thanks

2008/11/26 ekke <ekkehard@...>

so here's another one
working with Hibernate && (DB2 || HSQLDB || Oracle)

@Id
@GeneratedValue(strategy = GenerationType.TABLE)
@Column(name = "ADR_PK")
private long uPK;

you should read carefully the documentation about ID generation
from TopLink or Hibernate AND from your Database
and then decide

ekke

CSW - Sérgio Silva schrieb:

I Think this is what you are looking for:

….

private Long id;

@Id

@TableGenerator(name = "keyDFW", allocationSize = 1, initialValue = 1)

@GeneratedValue(strategy = GenerationType.TABLE, generator = "keyDFW")

public Long getId() {

…..

This is one approach of what you are looking for.

You can use a table or a sequence to auto generate the id!

A simple explanation (on TopLink JPA Implementation): http://www.oracle.com/technology/products/ias/toplink/jpa/howto/id-generation.html

------------------------------------------------------------------------

*From:* Fernando Freitas [mailto:nandows@...]
*Sent:* quarta-feira, 26 de Novembro de 2008 13:53
*To:* easybeans@...
*Subject:* [easybeans] Generate ID automatic

Hi everybody,
Someone knows....
1) How Can I do to generate "ID automatically " using easybeans with osgi?

Thanks and best Regards
Fernando Freitas

Re: Generate ID automatic

2008-11-26T06:59:55Z

so here's another one
working with Hibernate && (DB2 || HSQLDB || Oracle)

@Id
@GeneratedValue(strategy = GenerationType.TABLE)
@Column(name = "ADR_PK")
private long uPK;

you should read carefully the documentation about ID generation
from TopLink or Hibernate AND from your Database
and then decide

ekke

CSW - Sérgio Silva schrieb:

> I Think this is what you are looking for:
>
>
>
> ….
>
>
>
> private Long id;
>
>
>
>
>
> @Id
>
> @TableGenerator(name = "keyDFW", allocationSize = 1, initialValue = 1)
>
> @GeneratedValue(strategy = GenerationType.TABLE, generator = "keyDFW")
>
> public Long getId() {
>
> …..
>
>
>
> This is one approach of what you are looking for.
>
>
>
> You can use a table or a sequence to auto generate the id!
>
>
>
> A simple explanation (on TopLink JPA Implementation):
> http://www.oracle.com/technology/products/ias/toplink/jpa/howto/id-generation.html
>
>
>
> ------------------------------------------------------------------------
>
> *From:* Fernando Freitas [mailto:nandows@...]
> *Sent:* quarta-feira, 26 de Novembro de 2008 13:53
> *To:* easybeans@...
> *Subject:* [easybeans] Generate ID automatic
>
>
>
> Hi everybody,
>
> Someone knows....
>
> 1) How Can I do to generate "ID automatically " using easybeans with
> osgi?
>
>
> Thanks and best Regards
> Fernando Freitas
>

Re: Re: Re: Re: Still problems with connetion timeout

2008-11-26T06:39:14Z

An update: SQlState 8003 seems to relate to the connection trying to be used when the close() method was already called somewhere.

So we have a set of connections running for a while and at some point in time they'r close() method is called failing all subsequent calls to hibernate.

I sent this to the list (instead or hibernate or even the mysql folks) because I thought it might be something with jotm, or some configuration issue.

Any ideas?

Regards

David Alves

On Nov 26, 2008, at 2:27 PM, David Alves wrote:

Hi again

Sorry again, just rechecked the code, really using M2 (the lastest on the non snapshot repo) :).

Regards
David Alves

On Nov 26, 2008, at 2:25 PM, David Alves wrote:

Hi

Made a mistake really using M3 sorry.
It is not possible for me to change the database, it is maintained and used also by by other parties (that interact with my data).
Any other ideas?

Regards
David Alves
On Nov 26, 2008, at 2:21 PM, ekkehard wrote:

David Alves schrieb:

Hi

I recently upgraded easybeans osgi to the latest version (1.1.0-M2)

1.1.0M3 is the latest ;-)

and still the connections problem persists.

A little context: We'r using EZB osgi integrated in an search engine project, as a means of integrating it with other J2EE applications.

When we start the server all is well easybeans functions as it should and this goes on for a while. After a while though, any call to EZB that needs to interact with the database (through JPA and hibernate) fails.

The full error stack is presented at the end of this message.

The easybeans configuration regarding tm and db is as follows:

   

  <tm />

  

  <jdbcpool jndiName="jdbc_1" username="XXX" password="XXX"

  url="jdbc:mysql://127.0.0.1/XXX" driver="com.mysql.jdbc.Driver" />´



We even though that it might be a long runnong transaction problem so we placed:

@TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED) at the class level in all remote accessible classes and that didn't solve the problem.

We would really appreciate some help.

at first I would change the db to see if its something with the mysql ?

ekke

Re: Still problems with connetion timeout

2008-11-26T06:32:30Z

David Alves schrieb:
> Hi
>
> Made a mistake really using M3 sorry.
> It is not possible for me to change the database, it is maintained and
> used also by by other parties (that interact with my data).
> Any other ideas?
>
those things are always difficult to find out

in my application I have placed many logging-output
and if there's a problem I try to find out what happens after
logging some bundles or classes in DEBUG mode

ekke
perhaps some of the EZB experts have an idea

> Regards
> David Alves
> On Nov 26, 2008, at 2:21 PM, ekkehard wrote:
>
>> David Alves schrieb:
>>> Hi
>>>
>>> I recently upgraded easybeans osgi to the latest version (1.1.0-M2)
>> 1.1.0M3 is the latest ;-)
>>> and still the connections problem persists.
>>> A little context: We'r using EZB osgi integrated in an search engine
>>> project, as a means of integrating it with other J2EE applications.
>>> When we start the server all is well easybeans functions as it should
>>> and this goes on for a while. After a while though, any call to EZB
>>> that needs to interact with the database (through JPA and hibernate)
>>> fails.
>>> The full error stack is presented at the end of this message.
>>> The easybeans configuration regarding tm and db is as follows:
>>>
>>> 
>>> <tm />
>>> 
>>> <jdbcpool jndiName="jdbc_1" username="XXX" password="XXX"
>>> url="jdbc:mysql://127.0.0.1/XXX" driver="com.mysql.jdbc.Driver" />´
>>>
>>>
>>> We even though that it might be a long runnong transaction problem so
>>> we placed:
>>> @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED) at the
>>> class level in all remote accessible classes and that didn't solve
>>> the problem.
>>> We would really appreciate some help.
>>>
>> at first I would change the db to see if its something with the mysql ?
>>
>> ekke
>

Re: Re: Re: Still problems with connetion timeout

2008-11-26T06:27:40Z

Hi again

Sorry again, just rechecked the code, really using M2 (the lastest on the non snapshot repo) :).

Regards

David Alves

On Nov 26, 2008, at 2:25 PM, David Alves wrote:

Hi

Made a mistake really using M3 sorry.
It is not possible for me to change the database, it is maintained and used also by by other parties (that interact with my data).
Any other ideas?

Regards
David Alves
On Nov 26, 2008, at 2:21 PM, ekkehard wrote:

David Alves schrieb:

Hi

I recently upgraded easybeans osgi to the latest version (1.1.0-M2)

1.1.0M3 is the latest ;-)

and still the connections problem persists.

A little context: We'r using EZB osgi integrated in an search engine project, as a means of integrating it with other J2EE applications.

When we start the server all is well easybeans functions as it should and this goes on for a while. After a while though, any call to EZB that needs to interact with the database (through JPA and hibernate) fails.

The full error stack is presented at the end of this message.

The easybeans configuration regarding tm and db is as follows:

   

  <tm />

  

  <jdbcpool jndiName="jdbc_1" username="XXX" password="XXX"

  url="jdbc:mysql://127.0.0.1/XXX" driver="com.mysql.jdbc.Driver" />´



We even though that it might be a long runnong transaction problem so we placed:

@TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED) at the class level in all remote accessible classes and that didn't solve the problem.

We would really appreciate some help.

at first I would change the db to see if its something with the mysql ?

ekke

Re: Re: Still problems with connetion timeout

2008-11-26T06:25:39Z

Made a mistake really using M3 sorry.

It is not possible for me to change the database, it is maintained and used also by by other parties (that interact with my data).

Any other ideas?

Regards

David Alves

On Nov 26, 2008, at 2:21 PM, ekkehard wrote:

David Alves schrieb:

Hi

I recently upgraded easybeans osgi to the latest version (1.1.0-M2)

1.1.0M3 is the latest ;-)

and still the connections problem persists.

A little context: We'r using EZB osgi integrated in an search engine project, as a means of integrating it with other J2EE applications.

When we start the server all is well easybeans functions as it should and this goes on for a while. After a while though, any call to EZB that needs to interact with the database (through JPA and hibernate) fails.

The full error stack is presented at the end of this message.

The easybeans configuration regarding tm and db is as follows:

   

  <tm />

  

  <jdbcpool jndiName="jdbc_1" username="XXX" password="XXX"

  url="jdbc:mysql://127.0.0.1/XXX" driver="com.mysql.jdbc.Driver" />´



We even though that it might be a long runnong transaction problem so we placed:

@TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED) at the class level in all remote accessible classes and that didn't solve the problem.

We would really appreciate some help.

at first I would change the db to see if its something with the mysql ?

ekke

Re: Still problems with connetion timeout

2008-11-26T06:21:58Z

David Alves schrieb:

Hi

I recently upgraded easybeans osgi to the latest version (1.1.0-M2)

1.1.0M3 is the latest ;-)

and still the connections problem persists.

A little context: We'r using EZB osgi integrated in an search engine project, as a means of integrating it with other J2EE applications.

When we start the server all is well easybeans functions as it should and this goes on for a while. After a while though, any call to EZB that needs to interact with the database (through JPA and hibernate) fails.

The full error stack is presented at the end of this message.

The easybeans configuration regarding tm and db is as follows:

   

  <tm />

  

  <jdbcpool jndiName="jdbc_1" username="XXX" password="XXX"

  url="jdbc:mysql://127.0.0.1/XXX" driver="com.mysql.jdbc.Driver" />´



We even though that it might be a long runnong transaction problem so we placed:

@TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED) at the class level in all remote accessible classes and that didn't solve the problem.

We would really appreciate some help.

at first I would change the db to see if its something with the mysql ?

ekke

Re: Generate ID automatic

2008-11-26T06:17:51Z

Hi Fernando

Do you mean generate ID for a JPA entity?

That depends a little on the database and there are multiple strategies.

For instance with mysql and hibernate (and easybeans oegi, of course) I use:

@Id

@GeneratedValue

Placed over the field or getter of the Id property of the entity.

Hope this answers your question.

Regards

David Alves

On Nov 26, 2008, at 1:53 PM, Fernando Freitas wrote:

Hi everybody,

Someone knows....

1) How Can I do to generate "ID automatically " using easybeans with osgi?

Thanks and best Regards
Fernando Freitas

RE: Generate ID automatic

2008-11-26T06:17:19Z

I Think this is what you are looking for:

….

private Long id;

@Id

@TableGenerator(name = "keyDFW", allocationSize = 1, initialValue = 1)

@GeneratedValue(strategy = GenerationType.TABLE, generator = "keyDFW")

public Long getId() {

…..

This is one approach of what you are looking for.

You can use a table or a sequence to auto generate the id!

A simple explanation (on TopLink JPA Implementation): http://www.oracle.com/technology/products/ias/toplink/jpa/howto/id-generation.html

From: Fernando Freitas [mailto:nandows@...]
Sent: quarta-feira, 26 de Novembro de 2008 13:53
To: easybeans@...
Subject: [easybeans] Generate ID automatic

Hi everybody,

Someone knows....

1) How Can I do to generate "ID automatically " using easybeans with osgi?

Thanks and best Regards
Fernando Freitas

Re: Generate ID automatic

2008-11-26T06:17:06Z

Fernando Freitas schrieb:

> Hi everybody,
>
> Someone knows....
>
> 1) How Can I do to generate "ID automatically " using easybeans with
> osgi?
>
>
> Thanks and best Regards
> Fernando Freitas
>
>

this isn't easybeans responsibility

look at documentation from Hibernate and JPA
there are different strategies possible hot to generate ID

ekke