Re: Grid, generating conduit, unable to add method java.lang.Object get() to class
Thanks Lenny - I'm sure this will come in handy and has given me a few hours head start on myself, Cheers Chris On 24/09/2011, at 2:26 AM, Lenny Primak wrote: > Yes indeed. The relationships between JPA, tap-JPA, and entities themselves > isn't clearly documented. > It took me a while to figure out what the relationship was. > > tap-jpa and EJB packaging can coexist and must coexist peacefully. > The key to understanding this is how annotation processing works. > tapestry-jpa implements annotations via tapestry-ioc, while glassfish does > this via JEE annotation processing methods. > > For example, @PersistenceContext and @EntityManager annotations are processed > by tapestyr-jpa in tapestry packages only, > while they are processed by JEE/EJB code in glassfish in @Stateless/@Stateful > EJBs only. > > If you put @Stateless session bean, for example inside a tapestry package > (xxx.components, for example) > and declare a @PersistenceContext there, > then you will have a clash because both tapestry and glassfish will both try > to process the annotation. > > Hoep this helps > > On Sep 23, 2011, at 9:24 AM, Chris Mylonas wrote: > >> This is my lack of having not tested tapestry-jpa at all!!! >> If tap-jpa reads the same persistence.xml as my ejb-jar omg `kin rad!! >> >> otherwise - don't worry - this takes it to [OT] off topic. >> >> i don't understand the j2ee packaging that well - so take my knowledge with >> a grain of salt for now re: java packaging and how that works. i'm into >> protocol analysis on network stuff cos I like to connect things together >> (like most of us). >> >> i do not understand the relationship betweeen: >> 1.. persistence.xml in an ejb-jar; and, >> 2... persistence.xml in tapestry-jpa jar >> and whether the two can co-exist in the same ear project (i.e. how an entity >> manager works in both cases) >> >> which is beyond this mailing lists purpose. >> >> >> This is stuff I'll hammer out with some testing in due course :) >> >> >> Tapestry enables me to do web stuff "IN JAVA" much easier than mangling bits >> of non-UI java database stuff (e.g. EJB) than with php (ie. drupal cos it's >> easily hackable in the spaghetti code sense because that's the nature of the >> language IMO) >> >> which for me enables me to be a more productive/better progammer which >> I've been waiting for, for years!!! >> Hope that makes sense, both in my lack of understanding of java stuff - and >> where I expect tapestry to take things for me :) >> >> The rate at which stuff happens in this tapestry community is incredible to >> say the least, I just hope I can catch up - economically, socially, >> engineer-ily, glue-ily, technically etc.. >> >> >> Cheers >> Chris >> >> >> On 23/09/2011, at 4:22 PM, Lenny Primak wrote: >> >>> I don't understand this last message. >>> Tapestry-jpa module reads the same persistense.xml file as the JPA in >>> glassfish. >>> The only thing that's different is that glassfish does annotation >>> processing inside JEE-annotated classes (session beans) >>> and the tapestry-jpa module does the same within tapestry-ioc packages. >>> >>> On Sep 23, 2011, at 2:18 AM, Chris Mylonas wrote: >>> Good to know - my understanding of entity managers is low, so I was thinking the two lots of persistence.xml files would mean 2 entity managers, one for tapestry-jpa and one for EJB, unless tapestry-jpa can get the EJB's persistence.xml through java packaging magic. Stuff for me to learn unless someone can give a definitive "this is how it works" Have a good weekend, Chris On 23/09/2011, at 4:14 PM, Lenny Primak wrote: > I am using JPA module from 5.3 no problems, not sure about 5.2, but I > don't think that it should be an issue > I don't see any issues of mixing JPA module with EJB3 because I use it > myself > On Sep 22, 2011, at 6:12 PM, Chris Mylonas wrote: > >> Thanks Lenny >> I'm on GF 3.1.1 + tapestry 5.2.5 no JPA module, just using the jumpstart >> stuff from the EJB3 sample. >> >> >> Can I mix tapestry-jpa with EJB3 stuff without causing problems for >> entity manager? Or would the web stuff be safer to be read-only? >> >> >> >> On 22/09/2011, at 11:55 PM, Lenny Primak wrote: >> >>> Just to let you know, I am using GF 3.1.1 and tapestry 5.3 beta 5 with >>> built in JPA module and I have no such issue. >>> >>> >>> >>> On Sep 22, 2011, at 6:12 AM, Chris Mylonas wrote: >>> OMG!! - That did the trick!! The magic is in persistence.xml Thank you Geoff you champion I wonder what it will do to "performance, caching and change tracking" because according to that page, that's what weaving is for. PID USE
Re: Grid, generating conduit, unable to add method java.lang.Object get() to class
Yes indeed. The relationships between JPA, tap-JPA, and entities themselves isn't clearly documented. It took me a while to figure out what the relationship was. tap-jpa and EJB packaging can coexist and must coexist peacefully. The key to understanding this is how annotation processing works. tapestry-jpa implements annotations via tapestry-ioc, while glassfish does this via JEE annotation processing methods. For example, @PersistenceContext and @EntityManager annotations are processed by tapestyr-jpa in tapestry packages only, while they are processed by JEE/EJB code in glassfish in @Stateless/@Stateful EJBs only. If you put @Stateless session bean, for example inside a tapestry package (xxx.components, for example) and declare a @PersistenceContext there, then you will have a clash because both tapestry and glassfish will both try to process the annotation. Hoep this helps On Sep 23, 2011, at 9:24 AM, Chris Mylonas wrote: > This is my lack of having not tested tapestry-jpa at all!!! > If tap-jpa reads the same persistence.xml as my ejb-jar omg `kin rad!! > > otherwise - don't worry - this takes it to [OT] off topic. > > i don't understand the j2ee packaging that well - so take my knowledge with a > grain of salt for now re: java packaging and how that works. i'm into > protocol analysis on network stuff cos I like to connect things together > (like most of us). > > i do not understand the relationship betweeen: > 1.. persistence.xml in an ejb-jar; and, > 2... persistence.xml in tapestry-jpa jar > and whether the two can co-exist in the same ear project (i.e. how an entity > manager works in both cases) > > which is beyond this mailing lists purpose. > > > This is stuff I'll hammer out with some testing in due course :) > > > Tapestry enables me to do web stuff "IN JAVA" much easier than mangling bits > of non-UI java database stuff (e.g. EJB) than with php (ie. drupal cos it's > easily hackable in the spaghetti code sense because that's the nature of the > language IMO) > > which for me enables me to be a more productive/better progammer which > I've been waiting for, for years!!! > Hope that makes sense, both in my lack of understanding of java stuff - and > where I expect tapestry to take things for me :) > > The rate at which stuff happens in this tapestry community is incredible to > say the least, I just hope I can catch up - economically, socially, > engineer-ily, glue-ily, technically etc.. > > > Cheers > Chris > > > On 23/09/2011, at 4:22 PM, Lenny Primak wrote: > >> I don't understand this last message. >> Tapestry-jpa module reads the same persistense.xml file as the JPA in >> glassfish. >> The only thing that's different is that glassfish does annotation processing >> inside JEE-annotated classes (session beans) >> and the tapestry-jpa module does the same within tapestry-ioc packages. >> >> On Sep 23, 2011, at 2:18 AM, Chris Mylonas wrote: >> >>> Good to know - my understanding of entity managers is low, so I was >>> thinking the two lots of persistence.xml files would mean 2 entity >>> managers, one for tapestry-jpa and one for EJB, unless tapestry-jpa can get >>> the EJB's persistence.xml through java packaging magic. >>> >>> Stuff for me to learn unless someone can give a definitive "this is how it >>> works" >>> >>> Have a good weekend, >>> Chris >>> >>> >>> On 23/09/2011, at 4:14 PM, Lenny Primak wrote: >>> I am using JPA module from 5.3 no problems, not sure about 5.2, but I don't think that it should be an issue I don't see any issues of mixing JPA module with EJB3 because I use it myself On Sep 22, 2011, at 6:12 PM, Chris Mylonas wrote: > Thanks Lenny > I'm on GF 3.1.1 + tapestry 5.2.5 no JPA module, just using the jumpstart > stuff from the EJB3 sample. > > > Can I mix tapestry-jpa with EJB3 stuff without causing problems for > entity manager? Or would the web stuff be safer to be read-only? > > > > On 22/09/2011, at 11:55 PM, Lenny Primak wrote: > >> Just to let you know, I am using GF 3.1.1 and tapestry 5.3 beta 5 with >> built in JPA module and I have no such issue. >> >> >> >> On Sep 22, 2011, at 6:12 AM, Chris Mylonas wrote: >> >>> OMG!! - That did the trick!! >>> >>> The magic is in persistence.xml >>> >>> >>> >>> Thank you Geoff you champion >>> >>> >>> I wonder what it will do to "performance, caching and change tracking" >>> because according to that page, that's what weaving is for. >>> >>> PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND >>> >>> 7484 root 20 0 827m 372m 13m S 93.3 18.4 38:09.77 java >>> >>> 2258 mysq
Re: Grid, generating conduit, unable to add method java.lang.Object get() to class
This is my lack of having not tested tapestry-jpa at all!!! If tap-jpa reads the same persistence.xml as my ejb-jar omg `kin rad!! otherwise - don't worry - this takes it to [OT] off topic. i don't understand the j2ee packaging that well - so take my knowledge with a grain of salt for now re: java packaging and how that works. i'm into protocol analysis on network stuff cos I like to connect things together (like most of us). i do not understand the relationship betweeen: 1.. persistence.xml in an ejb-jar; and, 2... persistence.xml in tapestry-jpa jar and whether the two can co-exist in the same ear project (i.e. how an entity manager works in both cases) which is beyond this mailing lists purpose. This is stuff I'll hammer out with some testing in due course :) Tapestry enables me to do web stuff "IN JAVA" much easier than mangling bits of non-UI java database stuff (e.g. EJB) than with php (ie. drupal cos it's easily hackable in the spaghetti code sense because that's the nature of the language IMO) which for me enables me to be a more productive/better progammer which I've been waiting for, for years!!! Hope that makes sense, both in my lack of understanding of java stuff - and where I expect tapestry to take things for me :) The rate at which stuff happens in this tapestry community is incredible to say the least, I just hope I can catch up - economically, socially, engineer-ily, glue-ily, technically etc.. Cheers Chris On 23/09/2011, at 4:22 PM, Lenny Primak wrote: > I don't understand this last message. > Tapestry-jpa module reads the same persistense.xml file as the JPA in > glassfish. > The only thing that's different is that glassfish does annotation processing > inside JEE-annotated classes (session beans) > and the tapestry-jpa module does the same within tapestry-ioc packages. > > On Sep 23, 2011, at 2:18 AM, Chris Mylonas wrote: > >> Good to know - my understanding of entity managers is low, so I was thinking >> the two lots of persistence.xml files would mean 2 entity managers, one for >> tapestry-jpa and one for EJB, unless tapestry-jpa can get the EJB's >> persistence.xml through java packaging magic. >> >> Stuff for me to learn unless someone can give a definitive "this is how it >> works" >> >> Have a good weekend, >> Chris >> >> >> On 23/09/2011, at 4:14 PM, Lenny Primak wrote: >> >>> I am using JPA module from 5.3 no problems, not sure about 5.2, but I don't >>> think that it should be an issue >>> I don't see any issues of mixing JPA module with EJB3 because I use it >>> myself >>> On Sep 22, 2011, at 6:12 PM, Chris Mylonas wrote: >>> Thanks Lenny I'm on GF 3.1.1 + tapestry 5.2.5 no JPA module, just using the jumpstart stuff from the EJB3 sample. Can I mix tapestry-jpa with EJB3 stuff without causing problems for entity manager? Or would the web stuff be safer to be read-only? On 22/09/2011, at 11:55 PM, Lenny Primak wrote: > Just to let you know, I am using GF 3.1.1 and tapestry 5.3 beta 5 with > built in JPA module and I have no such issue. > > > > On Sep 22, 2011, at 6:12 AM, Chris Mylonas wrote: > >> OMG!! - That did the trick!! >> >> The magic is in persistence.xml >> >> >> >> Thank you Geoff you champion >> >> >> I wonder what it will do to "performance, caching and change tracking" >> because according to that page, that's what weaving is for. >> >> PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND >> >> 7484 root 20 0 827m 372m 13m S 93.3 18.4 38:09.77 java >> >> 2258 mysql 15 0 140m 30m 5000 S 34.9 1.5 13:07.30 mysqld >> >> 8168 root 15 0 10436 6304 2336 S 0.3 0.3 0:09.03 ssh >> >> 8497 chrismyl 15 0 2416 1084 820 R 0.3 0.1 0:01.69 top >> >> 1 root 15 0 2160 680 584 S 0.0 0.0 0:00.60 init >> >> Load average is at 0.7, but I'm monitoring systems during off-peak time. >> I'll definitely have to check JBoss out against Glassfish for this type >> of work I think. >> >> Anyway - I'm off to play with some Grid components :D >> >> Cheers >> Chris >> >> >> On 22/09/2011, at 7:45 PM, Geoff Callender wrote: >> >>> According to the following thread _persistence_shouldRefreshFetchGroup >>> was removed in Sep 2009, and a workaround for now might be to partially >>> disable "weaving". >>>
Re: Grid, generating conduit, unable to add method java.lang.Object get() to class
I don't understand this last message.
Tapestry-jpa module reads the same persistense.xml file as the JPA in glassfish.
The only thing that's different is that glassfish does annotation processing
inside JEE-annotated classes (session beans)
and the tapestry-jpa module does the same within tapestry-ioc packages.
On Sep 23, 2011, at 2:18 AM, Chris Mylonas wrote:
> Good to know - my understanding of entity managers is low, so I was thinking
> the two lots of persistence.xml files would mean 2 entity managers, one for
> tapestry-jpa and one for EJB, unless tapestry-jpa can get the EJB's
> persistence.xml through java packaging magic.
>
> Stuff for me to learn unless someone can give a definitive "this is how it
> works"
>
> Have a good weekend,
> Chris
>
>
> On 23/09/2011, at 4:14 PM, Lenny Primak wrote:
>
>> I am using JPA module from 5.3 no problems, not sure about 5.2, but I don't
>> think that it should be an issue
>> I don't see any issues of mixing JPA module with EJB3 because I use it
>> myself
>> On Sep 22, 2011, at 6:12 PM, Chris Mylonas wrote:
>>
>>> Thanks Lenny
>>> I'm on GF 3.1.1 + tapestry 5.2.5 no JPA module, just using the jumpstart
>>> stuff from the EJB3 sample.
>>>
>>>
>>> Can I mix tapestry-jpa with EJB3 stuff without causing problems for entity
>>> manager? Or would the web stuff be safer to be read-only?
>>>
>>>
>>>
>>> On 22/09/2011, at 11:55 PM, Lenny Primak wrote:
>>>
Just to let you know, I am using GF 3.1.1 and tapestry 5.3 beta 5 with
built in JPA module and I have no such issue.
On Sep 22, 2011, at 6:12 AM, Chris Mylonas wrote:
> OMG!! - That did the trick!!
>
> The magic is in persistence.xml
>
>
>
> Thank you Geoff you champion
>
>
> I wonder what it will do to "performance, caching and change tracking"
> because according to that page, that's what weaving is for.
>
> PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
>
> 7484 root 20 0 827m 372m 13m S 93.3 18.4 38:09.77 java
>
> 2258 mysql 15 0 140m 30m 5000 S 34.9 1.5 13:07.30 mysqld
>
> 8168 root 15 0 10436 6304 2336 S 0.3 0.3 0:09.03 ssh
>
> 8497 chrismyl 15 0 2416 1084 820 R 0.3 0.1 0:01.69 top
>
> 1 root 15 0 2160 680 584 S 0.0 0.0 0:00.60 init
>
> Load average is at 0.7, but I'm monitoring systems during off-peak time.
> I'll definitely have to check JBoss out against Glassfish for this type
> of work I think.
>
> Anyway - I'm off to play with some Grid components :D
>
> Cheers
> Chris
>
>
> On 22/09/2011, at 7:45 PM, Geoff Callender wrote:
>
>> According to the following thread _persistence_shouldRefreshFetchGroup
>> was removed in Sep 2009, and a workaround for now might be to partially
>> disable "weaving".
>>
>> http://forums.terracotta.org/forums/posts/list/2227.page
>>
>> On 22/09/2011, at 3:54 PM, Chris Mylonas wrote:
>>
>>> Hi Lenny & Tapestry Users,
>>>
>>> Yep I tried exclude in the template. No such luck. The thing errors
>>> out in setupRender - I might do the fetching of the List
>>> in onActivate (even though it's in the wrong place to put such stuff).
>>>
>>> I tried a few things, like the other suggestion to use @Inject
>>> BeanModelSource and also what is on the jumpstart page using
>>>
>>> myModel = beanModelSource.createDisplayModel(CalledEvent.class,
>>> componentResources.getMessages()).exclude("_persistence_shouldRefreshFetchGroup");
>>>
>>> But it still didn't work. Not exactly sure where the problem is, in
>>> EclipseLink or somewhere in Tapestry's use of BeanModel - I'll just
>>> use a Loop for now whilst I'm still deving.
>>>
>>> When I find some time next week I'll create a simple
>>> tapestry-jpa/tapestry-hibernate to see if that will work on Glassfish
>>> with the Grid component.
>>>
>>> Otherwise, I might go back to testing on JBoss so I can use Grid.
>>> It'll be a toss up whether the gains in getting easy webservices
>>> RS/SOAP on glassfish is worth not having use of BeanModel stuff.
>>>
>>> This is my persistence.xml in case you can see something I'm missing to
>>> make it work.
>>>
>>>
>>>
>>> http://java.sun.com/xml/ns/persistence";
>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>> xsi:schemaLocation="http:/
Re: Grid, generating conduit, unable to add method java.lang.Object get() to class
Good to know - my understanding of entity managers is low, so I was thinking
the two lots of persistence.xml files would mean 2 entity managers, one for
tapestry-jpa and one for EJB, unless tapestry-jpa can get the EJB's
persistence.xml through java packaging magic.
Stuff for me to learn unless someone can give a definitive "this is how it
works"
Have a good weekend,
Chris
On 23/09/2011, at 4:14 PM, Lenny Primak wrote:
> I am using JPA module from 5.3 no problems, not sure about 5.2, but I don't
> think that it should be an issue
> I don't see any issues of mixing JPA module with EJB3 because I use it myself
> On Sep 22, 2011, at 6:12 PM, Chris Mylonas wrote:
>
>> Thanks Lenny
>> I'm on GF 3.1.1 + tapestry 5.2.5 no JPA module, just using the jumpstart
>> stuff from the EJB3 sample.
>>
>>
>> Can I mix tapestry-jpa with EJB3 stuff without causing problems for entity
>> manager? Or would the web stuff be safer to be read-only?
>>
>>
>>
>> On 22/09/2011, at 11:55 PM, Lenny Primak wrote:
>>
>>> Just to let you know, I am using GF 3.1.1 and tapestry 5.3 beta 5 with
>>> built in JPA module and I have no such issue.
>>>
>>>
>>>
>>> On Sep 22, 2011, at 6:12 AM, Chris Mylonas wrote:
>>>
OMG!! - That did the trick!!
The magic is in persistence.xml
Thank you Geoff you champion
I wonder what it will do to "performance, caching and change tracking"
because according to that page, that's what weaving is for.
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
7484 root 20 0 827m 372m 13m S 93.3 18.4 38:09.77 java
2258 mysql 15 0 140m 30m 5000 S 34.9 1.5 13:07.30 mysqld
8168 root 15 0 10436 6304 2336 S 0.3 0.3 0:09.03 ssh
8497 chrismyl 15 0 2416 1084 820 R 0.3 0.1 0:01.69 top
1 root 15 0 2160 680 584 S 0.0 0.0 0:00.60 init
Load average is at 0.7, but I'm monitoring systems during off-peak time.
I'll definitely have to check JBoss out against Glassfish for this type of
work I think.
Anyway - I'm off to play with some Grid components :D
Cheers
Chris
On 22/09/2011, at 7:45 PM, Geoff Callender wrote:
> According to the following thread _persistence_shouldRefreshFetchGroup
> was removed in Sep 2009, and a workaround for now might be to partially
> disable "weaving".
>
> http://forums.terracotta.org/forums/posts/list/2227.page
>
> On 22/09/2011, at 3:54 PM, Chris Mylonas wrote:
>
>> Hi Lenny & Tapestry Users,
>>
>> Yep I tried exclude in the template. No such luck. The thing errors
>> out in setupRender - I might do the fetching of the List in
>> onActivate (even though it's in the wrong place to put such stuff).
>>
>> I tried a few things, like the other suggestion to use @Inject
>> BeanModelSource and also what is on the jumpstart page using
>>
>> myModel = beanModelSource.createDisplayModel(CalledEvent.class,
>> componentResources.getMessages()).exclude("_persistence_shouldRefreshFetchGroup");
>>
>> But it still didn't work. Not exactly sure where the problem is, in
>> EclipseLink or somewhere in Tapestry's use of BeanModel - I'll just use
>> a Loop for now whilst I'm still deving.
>>
>> When I find some time next week I'll create a simple
>> tapestry-jpa/tapestry-hibernate to see if that will work on Glassfish
>> with the Grid component.
>>
>> Otherwise, I might go back to testing on JBoss so I can use Grid. It'll
>> be a toss up whether the gains in getting easy webservices RS/SOAP on
>> glassfish is worth not having use of BeanModel stuff.
>>
>> This is my persistence.xml in case you can see something I'm missing to
>> make it work.
>>
>>
>>
>> http://java.sun.com/xml/ns/persistence";
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>> xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
>> http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd";
>> version="1.0">
>>
>>
>> org.eclipse.persistence.jpa.PersistenceProvider
>> jdbc/fullcti1DS
>>
>> org.opencsta.ctiserver.business.callservices.model.BasicEvent
>>
>> org.opencsta.ctiserver.business.callevents.model.CalledEvent
>>
>>
>> > value="create-tables" />
>>
>>
>>
>>
Re: Grid, generating conduit, unable to add method java.lang.Object get() to class
I am using JPA module from 5.3 no problems, not sure about 5.2, but I don't
think that it should be an issue
I don't see any issues of mixing JPA module with EJB3 because I use it myself
On Sep 22, 2011, at 6:12 PM, Chris Mylonas wrote:
> Thanks Lenny
> I'm on GF 3.1.1 + tapestry 5.2.5 no JPA module, just using the jumpstart
> stuff from the EJB3 sample.
>
>
> Can I mix tapestry-jpa with EJB3 stuff without causing problems for entity
> manager? Or would the web stuff be safer to be read-only?
>
>
>
> On 22/09/2011, at 11:55 PM, Lenny Primak wrote:
>
>> Just to let you know, I am using GF 3.1.1 and tapestry 5.3 beta 5 with built
>> in JPA module and I have no such issue.
>>
>>
>>
>> On Sep 22, 2011, at 6:12 AM, Chris Mylonas wrote:
>>
>>> OMG!! - That did the trick!!
>>>
>>> The magic is in persistence.xml
>>>
>>>
>>>
>>> Thank you Geoff you champion
>>>
>>>
>>> I wonder what it will do to "performance, caching and change tracking"
>>> because according to that page, that's what weaving is for.
>>>
>>> PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
>>>
>>> 7484 root 20 0 827m 372m 13m S 93.3 18.4 38:09.77 java
>>>
>>> 2258 mysql 15 0 140m 30m 5000 S 34.9 1.5 13:07.30 mysqld
>>>
>>> 8168 root 15 0 10436 6304 2336 S 0.3 0.3 0:09.03 ssh
>>>
>>> 8497 chrismyl 15 0 2416 1084 820 R 0.3 0.1 0:01.69 top
>>>
>>> 1 root 15 0 2160 680 584 S 0.0 0.0 0:00.60 init
>>>
>>> Load average is at 0.7, but I'm monitoring systems during off-peak time.
>>> I'll definitely have to check JBoss out against Glassfish for this type of
>>> work I think.
>>>
>>> Anyway - I'm off to play with some Grid components :D
>>>
>>> Cheers
>>> Chris
>>>
>>>
>>> On 22/09/2011, at 7:45 PM, Geoff Callender wrote:
>>>
According to the following thread _persistence_shouldRefreshFetchGroup was
removed in Sep 2009, and a workaround for now might be to partially
disable "weaving".
http://forums.terracotta.org/forums/posts/list/2227.page
On 22/09/2011, at 3:54 PM, Chris Mylonas wrote:
> Hi Lenny & Tapestry Users,
>
> Yep I tried exclude in the template. No such luck. The thing errors out
> in setupRender - I might do the fetching of the List in
> onActivate (even though it's in the wrong place to put such stuff).
>
> I tried a few things, like the other suggestion to use @Inject
> BeanModelSource and also what is on the jumpstart page using
>
> myModel = beanModelSource.createDisplayModel(CalledEvent.class,
> componentResources.getMessages()).exclude("_persistence_shouldRefreshFetchGroup");
>
> But it still didn't work. Not exactly sure where the problem is, in
> EclipseLink or somewhere in Tapestry's use of BeanModel - I'll just use
> a Loop for now whilst I'm still deving.
>
> When I find some time next week I'll create a simple
> tapestry-jpa/tapestry-hibernate to see if that will work on Glassfish
> with the Grid component.
>
> Otherwise, I might go back to testing on JBoss so I can use Grid. It'll
> be a toss up whether the gains in getting easy webservices RS/SOAP on
> glassfish is worth not having use of BeanModel stuff.
>
> This is my persistence.xml in case you can see something I'm missing to
> make it work.
>
>
>
> http://java.sun.com/xml/ns/persistence";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
> http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd";
> version="1.0">
>
>
> org.eclipse.persistence.jpa.PersistenceProvider
> jdbc/fullcti1DS
>
> org.opencsta.ctiserver.business.callservices.model.BasicEvent
>
> org.opencsta.ctiserver.business.callevents.model.CalledEvent
>
>
> value="create-tables" />
>
>
>
> transaction-type="JTA">
> org.eclipse.persistence.jpa.PersistenceProvider
> jdbc/d6alerteetestDS
> com.alertee.contacts.model.CustomAlerteeContacts
> com.alertee.contacts.model.CustomAlerteeNumbers
>
>
>
>
>
>
>
>
>
> Thanks for your suggestions!
>
> Chris
>
> On 22/09/2011, at 1:24 AM, Lenny Primak wrote:
>
>> Have you tried exclude= in your template? That worked for m
Re: Grid, generating conduit, unable to add method java.lang.Object get() to class
Thanks Lenny
I'm on GF 3.1.1 + tapestry 5.2.5 no JPA module, just using the jumpstart stuff
from the EJB3 sample.
Can I mix tapestry-jpa with EJB3 stuff without causing problems for entity
manager? Or would the web stuff be safer to be read-only?
On 22/09/2011, at 11:55 PM, Lenny Primak wrote:
> Just to let you know, I am using GF 3.1.1 and tapestry 5.3 beta 5 with built
> in JPA module and I have no such issue.
>
>
>
> On Sep 22, 2011, at 6:12 AM, Chris Mylonas wrote:
>
>> OMG!! - That did the trick!!
>>
>> The magic is in persistence.xml
>>
>>
>>
>> Thank you Geoff you champion
>>
>>
>> I wonder what it will do to "performance, caching and change tracking"
>> because according to that page, that's what weaving is for.
>>
>> PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
>>
>> 7484 root 20 0 827m 372m 13m S 93.3 18.4 38:09.77 java
>>
>> 2258 mysql 15 0 140m 30m 5000 S 34.9 1.5 13:07.30 mysqld
>>
>> 8168 root 15 0 10436 6304 2336 S 0.3 0.3 0:09.03 ssh
>>
>> 8497 chrismyl 15 0 2416 1084 820 R 0.3 0.1 0:01.69 top
>>
>> 1 root 15 0 2160 680 584 S 0.0 0.0 0:00.60 init
>>
>> Load average is at 0.7, but I'm monitoring systems during off-peak time.
>> I'll definitely have to check JBoss out against Glassfish for this type of
>> work I think.
>>
>> Anyway - I'm off to play with some Grid components :D
>>
>> Cheers
>> Chris
>>
>>
>> On 22/09/2011, at 7:45 PM, Geoff Callender wrote:
>>
>>> According to the following thread _persistence_shouldRefreshFetchGroup was
>>> removed in Sep 2009, and a workaround for now might be to partially disable
>>> "weaving".
>>>
>>> http://forums.terracotta.org/forums/posts/list/2227.page
>>>
>>> On 22/09/2011, at 3:54 PM, Chris Mylonas wrote:
>>>
Hi Lenny & Tapestry Users,
Yep I tried exclude in the template. No such luck. The thing errors out
in setupRender - I might do the fetching of the List in
onActivate (even though it's in the wrong place to put such stuff).
I tried a few things, like the other suggestion to use @Inject
BeanModelSource and also what is on the jumpstart page using
myModel = beanModelSource.createDisplayModel(CalledEvent.class,
componentResources.getMessages()).exclude("_persistence_shouldRefreshFetchGroup");
But it still didn't work. Not exactly sure where the problem is, in
EclipseLink or somewhere in Tapestry's use of BeanModel - I'll just use a
Loop for now whilst I'm still deving.
When I find some time next week I'll create a simple
tapestry-jpa/tapestry-hibernate to see if that will work on Glassfish with
the Grid component.
Otherwise, I might go back to testing on JBoss so I can use Grid. It'll
be a toss up whether the gains in getting easy webservices RS/SOAP on
glassfish is worth not having use of BeanModel stuff.
This is my persistence.xml in case you can see something I'm missing to
make it work.
http://java.sun.com/xml/ns/persistence";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd";
version="1.0">
org.eclipse.persistence.jpa.PersistenceProvider
jdbc/fullcti1DS
org.opencsta.ctiserver.business.callservices.model.BasicEvent
org.opencsta.ctiserver.business.callevents.model.CalledEvent
>>> value="create-tables" />
>>> transaction-type="JTA">
org.eclipse.persistence.jpa.PersistenceProvider
jdbc/d6alerteetestDS
com.alertee.contacts.model.CustomAlerteeContacts
com.alertee.contacts.model.CustomAlerteeNumbers
Thanks for your suggestions!
Chris
On 22/09/2011, at 1:24 AM, Lenny Primak wrote:
> Have you tried exclude= in your template? That worked for me and is
> simple.
>
>
>
> On Sep 21, 2011, at 11:18 AM, Chris Mylonas wrote:
>
>> Hi!!
>>
>> It is EclipseLink (glassfish 3.1.1), I've just tried the first time now
>> and it failed again (same reason) but I'll try a few other things based
>> on Thiago's response earlier (re: BeanModel).
>>
>>
Re: Grid, generating conduit, unable to add method java.lang.Object get() to class
Just to let you know, I am using GF 3.1.1 and tapestry 5.3 beta 5 with built in
JPA module and I have no such issue.
On Sep 22, 2011, at 6:12 AM, Chris Mylonas wrote:
> OMG!! - That did the trick!!
>
> The magic is in persistence.xml
>
>
>
> Thank you Geoff you champion
>
>
> I wonder what it will do to "performance, caching and change tracking"
> because according to that page, that's what weaving is for.
>
> PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
>
> 7484 root 20 0 827m 372m 13m S 93.3 18.4 38:09.77 java
>
> 2258 mysql 15 0 140m 30m 5000 S 34.9 1.5 13:07.30 mysqld
>
> 8168 root 15 0 10436 6304 2336 S 0.3 0.3 0:09.03 ssh
>
> 8497 chrismyl 15 0 2416 1084 820 R 0.3 0.1 0:01.69 top
>
>1 root 15 0 2160 680 584 S 0.0 0.0 0:00.60 init
>
> Load average is at 0.7, but I'm monitoring systems during off-peak time.
> I'll definitely have to check JBoss out against Glassfish for this type of
> work I think.
>
> Anyway - I'm off to play with some Grid components :D
>
> Cheers
> Chris
>
>
> On 22/09/2011, at 7:45 PM, Geoff Callender wrote:
>
>> According to the following thread _persistence_shouldRefreshFetchGroup was
>> removed in Sep 2009, and a workaround for now might be to partially disable
>> "weaving".
>>
>>http://forums.terracotta.org/forums/posts/list/2227.page
>>
>> On 22/09/2011, at 3:54 PM, Chris Mylonas wrote:
>>
>>> Hi Lenny & Tapestry Users,
>>>
>>> Yep I tried exclude in the template. No such luck. The thing errors out
>>> in setupRender - I might do the fetching of the List in
>>> onActivate (even though it's in the wrong place to put such stuff).
>>>
>>> I tried a few things, like the other suggestion to use @Inject
>>> BeanModelSource and also what is on the jumpstart page using
>>>
>>> myModel = beanModelSource.createDisplayModel(CalledEvent.class,
>>> componentResources.getMessages()).exclude("_persistence_shouldRefreshFetchGroup");
>>>
>>> But it still didn't work. Not exactly sure where the problem is, in
>>> EclipseLink or somewhere in Tapestry's use of BeanModel - I'll just use a
>>> Loop for now whilst I'm still deving.
>>>
>>> When I find some time next week I'll create a simple
>>> tapestry-jpa/tapestry-hibernate to see if that will work on Glassfish with
>>> the Grid component.
>>>
>>> Otherwise, I might go back to testing on JBoss so I can use Grid. It'll be
>>> a toss up whether the gains in getting easy webservices RS/SOAP on
>>> glassfish is worth not having use of BeanModel stuff.
>>>
>>> This is my persistence.xml in case you can see something I'm missing to
>>> make it work.
>>>
>>>
>>>
>>> http://java.sun.com/xml/ns/persistence";
>>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>>>xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
>>> http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd";
>>>version="1.0">
>>>
>>>
>>>org.eclipse.persistence.jpa.PersistenceProvider
>>>jdbc/fullcti1DS
>>>
>>> org.opencsta.ctiserver.business.callservices.model.BasicEvent
>>>
>>> org.opencsta.ctiserver.business.callevents.model.CalledEvent
>>>
>>>
>>>>> value="create-tables" />
>>>
>>>
>>>
>>>>>transaction-type="JTA">
>>>org.eclipse.persistence.jpa.PersistenceProvider
>>>jdbc/d6alerteetestDS
>>>com.alertee.contacts.model.CustomAlerteeContacts
>>>com.alertee.contacts.model.CustomAlerteeNumbers
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Thanks for your suggestions!
>>>
>>> Chris
>>>
>>> On 22/09/2011, at 1:24 AM, Lenny Primak wrote:
>>>
Have you tried exclude= in your template? That worked for me and is
simple.
On Sep 21, 2011, at 11:18 AM, Chris Mylonas wrote:
> Hi!!
>
> It is EclipseLink (glassfish 3.1.1), I've just tried the first time now
> and it failed again (same reason) but I'll try a few other things based
> on Thiago's response earlier (re: BeanModel).
>
> Here is CalledEvent which the error comes from if you can see anything
> strange, apologies Thiago for sending it to you directly earlier!!
>
> package org.opencsta.ctiserver.business.callevents.model;
>
> import java.io.Serializable;
>
> import javax.persistence.Entity;
> import javax.persistence.GeneratedValue;
> import javax.persistence.GenerationType;
> import javax
Re: Grid, generating conduit, unable to add method java.lang.Object get() to class
OMG!! - That did the trick!!
The magic is in persistence.xml
Thank you Geoff you champion
I wonder what it will do to "performance, caching and change tracking"
because according to that page, that's what weaving is for.
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
7484 root 20 0 827m 372m 13m S 93.3 18.4 38:09.77 java
2258 mysql 15 0 140m 30m 5000 S 34.9 1.5 13:07.30 mysqld
8168 root 15 0 10436 6304 2336 S 0.3 0.3 0:09.03 ssh
8497 chrismyl 15 0 2416 1084 820 R 0.3 0.1 0:01.69 top
1 root 15 0 2160 680 584 S 0.0 0.0 0:00.60 init
Load average is at 0.7, but I'm monitoring systems during off-peak time.
I'll definitely have to check JBoss out against Glassfish for this type of work
I think.
Anyway - I'm off to play with some Grid components :D
Cheers
Chris
On 22/09/2011, at 7:45 PM, Geoff Callender wrote:
> According to the following thread _persistence_shouldRefreshFetchGroup was
> removed in Sep 2009, and a workaround for now might be to partially disable
> "weaving".
>
> http://forums.terracotta.org/forums/posts/list/2227.page
>
> On 22/09/2011, at 3:54 PM, Chris Mylonas wrote:
>
>> Hi Lenny & Tapestry Users,
>>
>> Yep I tried exclude in the template. No such luck. The thing errors out in
>> setupRender - I might do the fetching of the List in onActivate
>> (even though it's in the wrong place to put such stuff).
>>
>> I tried a few things, like the other suggestion to use @Inject
>> BeanModelSource and also what is on the jumpstart page using
>>
>> myModel = beanModelSource.createDisplayModel(CalledEvent.class,
>> componentResources.getMessages()).exclude("_persistence_shouldRefreshFetchGroup");
>>
>> But it still didn't work. Not exactly sure where the problem is, in
>> EclipseLink or somewhere in Tapestry's use of BeanModel - I'll just use a
>> Loop for now whilst I'm still deving.
>>
>> When I find some time next week I'll create a simple
>> tapestry-jpa/tapestry-hibernate to see if that will work on Glassfish with
>> the Grid component.
>>
>> Otherwise, I might go back to testing on JBoss so I can use Grid. It'll be
>> a toss up whether the gains in getting easy webservices RS/SOAP on glassfish
>> is worth not having use of BeanModel stuff.
>>
>> This is my persistence.xml in case you can see something I'm missing to make
>> it work.
>>
>>
>>
>> http://java.sun.com/xml/ns/persistence";
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>> xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
>> http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd";
>> version="1.0">
>>
>>
>>
>> org.eclipse.persistence.jpa.PersistenceProvider
>> jdbc/fullcti1DS
>>
>> org.opencsta.ctiserver.business.callservices.model.BasicEvent
>>
>> org.opencsta.ctiserver.business.callevents.model.CalledEvent
>>
>>
>> > value="create-tables" />
>> > />
>>
>>
>> > transaction-type="JTA">
>>
>> org.eclipse.persistence.jpa.PersistenceProvider
>> jdbc/d6alerteetestDS
>> com.alertee.contacts.model.CustomAlerteeContacts
>> com.alertee.contacts.model.CustomAlerteeNumbers
>>
>> > value="none" />
>> > />
>>
>>
>>
>>
>>
>>
>> Thanks for your suggestions!
>>
>> Chris
>>
>> On 22/09/2011, at 1:24 AM, Lenny Primak wrote:
>>
>>> Have you tried exclude= in your template? That worked for me and is
>>> simple.
>>>
>>>
>>>
>>> On Sep 21, 2011, at 11:18 AM, Chris Mylonas wrote:
>>>
Hi!!
It is EclipseLink (glassfish 3.1.1), I've just tried the first time now
and it failed again (same reason) but I'll try a few other things based on
Thiago's response earlier (re: BeanModel).
Here is CalledEvent which the error comes from if you can see anything
strange, apologies Thiago for sending it to you directly earlier!!
package org.opencsta.ctiserver.business.callevents.model;
import java.io.Serializable;
import javax.persistence.Entity;
import javax.persistence.GeneratedValue;
import javax.persistence.GenerationType;
import javax.persistence.Id;
import javax.persistence.NamedQueries;
import javax.persistence.NamedQuery;
import javax.persistence.Transient;
>>>
Re: Grid, generating conduit, unable to add method java.lang.Object get() to class
According to the following thread _persistence_shouldRefreshFetchGroup was
removed in Sep 2009, and a workaround for now might be to partially disable
"weaving".
http://forums.terracotta.org/forums/posts/list/2227.page
On 22/09/2011, at 3:54 PM, Chris Mylonas wrote:
> Hi Lenny & Tapestry Users,
>
> Yep I tried exclude in the template. No such luck. The thing errors out in
> setupRender - I might do the fetching of the List in onActivate
> (even though it's in the wrong place to put such stuff).
>
> I tried a few things, like the other suggestion to use @Inject
> BeanModelSource and also what is on the jumpstart page using
>
> myModel = beanModelSource.createDisplayModel(CalledEvent.class,
> componentResources.getMessages()).exclude("_persistence_shouldRefreshFetchGroup");
>
> But it still didn't work. Not exactly sure where the problem is, in
> EclipseLink or somewhere in Tapestry's use of BeanModel - I'll just use a
> Loop for now whilst I'm still deving.
>
> When I find some time next week I'll create a simple
> tapestry-jpa/tapestry-hibernate to see if that will work on Glassfish with
> the Grid component.
>
> Otherwise, I might go back to testing on JBoss so I can use Grid. It'll be a
> toss up whether the gains in getting easy webservices RS/SOAP on glassfish is
> worth not having use of BeanModel stuff.
>
> This is my persistence.xml in case you can see something I'm missing to make
> it work.
>
>
>
> http://java.sun.com/xml/ns/persistence";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
> http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd";
> version="1.0">
>
>
>
> org.eclipse.persistence.jpa.PersistenceProvider
> jdbc/fullcti1DS
>
> org.opencsta.ctiserver.business.callservices.model.BasicEvent
>
> org.opencsta.ctiserver.business.callevents.model.CalledEvent
>
>
>value="create-tables" />
>/>
>
>
> transaction-type="JTA">
>
> org.eclipse.persistence.jpa.PersistenceProvider
> jdbc/d6alerteetestDS
> com.alertee.contacts.model.CustomAlerteeContacts
> com.alertee.contacts.model.CustomAlerteeNumbers
>
>value="none" />
>/>
>
>
>
>
>
>
> Thanks for your suggestions!
>
> Chris
>
> On 22/09/2011, at 1:24 AM, Lenny Primak wrote:
>
>> Have you tried exclude= in your template? That worked for me and is simple.
>>
>>
>>
>> On Sep 21, 2011, at 11:18 AM, Chris Mylonas wrote:
>>
>>> Hi!!
>>>
>>> It is EclipseLink (glassfish 3.1.1), I've just tried the first time now and
>>> it failed again (same reason) but I'll try a few other things based on
>>> Thiago's response earlier (re: BeanModel).
>>>
>>> Here is CalledEvent which the error comes from if you can see anything
>>> strange, apologies Thiago for sending it to you directly earlier!!
>>>
>>> package org.opencsta.ctiserver.business.callevents.model;
>>>
>>> import java.io.Serializable;
>>>
>>> import javax.persistence.Entity;
>>> import javax.persistence.GeneratedValue;
>>> import javax.persistence.GenerationType;
>>> import javax.persistence.Id;
>>> import javax.persistence.NamedQueries;
>>> import javax.persistence.NamedQuery;
>>> import javax.persistence.Transient;
>>>
>>> /**
>>> * @author chrismylonas
>>> *
>>> */
>>> @Entity
>>> @NamedQueries({ @NamedQuery(name
>>> =org.opencsta.ctiserver.business.callevents.model.CalledEvent.QUERY_GETALL,
>>> query ="select c FROM CalledEvent c") })
>>> public class CalledEvent implements Serializable {
>>>
>>> /**
>>> *
>>> */
>>> private static final long serialVersionUID =-35384297244606697L;
>>>
>>> /**
>>> *
>>> */
>>> public static final String QUERY_GETALL
>>> ="org.opencsta.ctiserver.business.callevents.model.CalledEvent.QUERY_GETALL";
>>>
>>> /**
>>> *
>>> */
>>> @Id
>>> @GeneratedValue(strategy =GenerationType.IDENTITY)
>>> private Long id;
>>>
>>> /**
>>> *
>>> */
>>> private String name;
>>>
>>> /**
>>> *
>>> */
>>> private String callingParty;
>>>
>>> /**
>>> *
>>> */
>>> private String calledParty;
>>>
>>> /**
>>> *
>>> */
>>> private String dialedNumber;
>>>
>>> /**
>>> *
>>> */
>>> private String trunk;
>>>
>>> /**
>>> *
>>> */
>>> private String server;
>>>
>>> /**
>>> * @return
>>> */
>>> public Long getId() {
>>> return id;
>>> }
>>>
>>> /**
>>> * @param id
>>> */
>>> public void setId(Long id) {
>>> this.id =id;
>>> }
>>>
>>> /**
>>> * @return
>>> */
>>> public String getName() {
>>> return name;
>>> }
>>>
>>> /**
>>> * @param name
>>> */
>>> public void setName(String n
Re: Grid, generating conduit, unable to add method java.lang.Object get() to class
Hi Lenny & Tapestry Users,
Yep I tried exclude in the template. No such luck. The thing errors out in
setupRender - I might do the fetching of the List in onActivate
(even though it's in the wrong place to put such stuff).
I tried a few things, like the other suggestion to use @Inject BeanModelSource
and also what is on the jumpstart page using
myModel = beanModelSource.createDisplayModel(CalledEvent.class,
componentResources.getMessages()).exclude("_persistence_shouldRefreshFetchGroup");
But it still didn't work. Not exactly sure where the problem is, in
EclipseLink or somewhere in Tapestry's use of BeanModel - I'll just use a Loop
for now whilst I'm still deving.
When I find some time next week I'll create a simple
tapestry-jpa/tapestry-hibernate to see if that will work on Glassfish with the
Grid component.
Otherwise, I might go back to testing on JBoss so I can use Grid. It'll be a
toss up whether the gains in getting easy webservices RS/SOAP on glassfish is
worth not having use of BeanModel stuff.
This is my persistence.xml in case you can see something I'm missing to make it
work.
http://java.sun.com/xml/ns/persistence";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd";
version="1.0">
org.eclipse.persistence.jpa.PersistenceProvider
jdbc/fullcti1DS
org.opencsta.ctiserver.business.callservices.model.BasicEvent
org.opencsta.ctiserver.business.callevents.model.CalledEvent
org.eclipse.persistence.jpa.PersistenceProvider
jdbc/d6alerteetestDS
com.alertee.contacts.model.CustomAlerteeContacts
com.alertee.contacts.model.CustomAlerteeNumbers
Thanks for your suggestions!
Chris
On 22/09/2011, at 1:24 AM, Lenny Primak wrote:
> Have you tried exclude= in your template? That worked for me and is simple.
>
>
>
> On Sep 21, 2011, at 11:18 AM, Chris Mylonas wrote:
>
>> Hi!!
>>
>> It is EclipseLink (glassfish 3.1.1), I've just tried the first time now and
>> it failed again (same reason) but I'll try a few other things based on
>> Thiago's response earlier (re: BeanModel).
>>
>> Here is CalledEvent which the error comes from if you can see anything
>> strange, apologies Thiago for sending it to you directly earlier!!
>>
>> package org.opencsta.ctiserver.business.callevents.model;
>>
>> import java.io.Serializable;
>>
>> import javax.persistence.Entity;
>> import javax.persistence.GeneratedValue;
>> import javax.persistence.GenerationType;
>> import javax.persistence.Id;
>> import javax.persistence.NamedQueries;
>> import javax.persistence.NamedQuery;
>> import javax.persistence.Transient;
>>
>> /**
>> * @author chrismylonas
>> *
>> */
>> @Entity
>> @NamedQueries({ @NamedQuery(name
>> =org.opencsta.ctiserver.business.callevents.model.CalledEvent.QUERY_GETALL,
>> query ="select c FROM CalledEvent c") })
>> public class CalledEvent implements Serializable {
>>
>> /**
>>*
>>*/
>> private static final long serialVersionUID =-35384297244606697L;
>>
>> /**
>>*
>>*/
>> public static final String QUERY_GETALL
>> ="org.opencsta.ctiserver.business.callevents.model.CalledEvent.QUERY_GETALL";
>>
>> /**
>>*
>>*/
>> @Id
>> @GeneratedValue(strategy =GenerationType.IDENTITY)
>> private Long id;
>>
>> /**
>>*
>>*/
>> private String name;
>>
>> /**
>>*
>>*/
>> private String callingParty;
>>
>> /**
>>*
>>*/
>> private String calledParty;
>>
>> /**
>>*
>>*/
>> private String dialedNumber;
>>
>> /**
>>*
>>*/
>> private String trunk;
>>
>> /**
>>*
>>*/
>> private String server;
>>
>> /**
>>* @return
>>*/
>> public Long getId() {
>> return id;
>> }
>>
>> /**
>>* @param id
>>*/
>> public void setId(Long id) {
>> this.id =id;
>> }
>>
>> /**
>>* @return
>>*/
>> public String getName() {
>> return name;
>> }
>>
>> /**
>>* @param name
>>*/
>> public void setName(String name) {
>> this.name =name;
>> }
>>
>> /**
>>* @return
>>*/
>> public String getCallingParty() {
>> return callingParty;
>> }
>>
>> /**
>>* @param callingParty
>>*/
>> public void setCallingParty(String callingParty) {
>> this.callingParty ÊllingParty;
>> }
>>
>> /**
>>* @return
>>*/
>> public String getCalledParty() {
>> return calledParty;
>> }
>>
>> /**
>>* @param calledParty
>>*/
>> public void setCalledParty(Stri
Re: Grid, generating conduit, unable to add method java.lang.Object get() to class
Yes - but I'm going to restart the app server because I don't trust it (cache
wise, it's probably still got something in there)
Still yields the same errors :(
With this added to the original for providing the model,
@Inject
private BeanModelSource bms;
@Inject
private Messages messages;
public BeanModel getMyGridModel() {
return bms.createDisplayModel(CalledEvent.class, messages);
}
location
classpath:org/opencsta/eventviewer/pages/Index.tml, line 30
org.apache.tapestry5.internal.services.PropertyExpressionException
Exception generating conduit for expression
'_persistence_shouldRefreshFetchGroup': Unable to add method java.lang.Object
get(java.lang.Object) to class $PropertyConduit_1328c9eca52: [source error]
_persistence_shouldRefreshFetchGroup() not found in
org.opencsta.ctiserver.business.callevents.model.CalledEvent
expression
_persistence_shouldRefreshFetchGroup
javassist.CannotCompileException
[source error] _persistence_shouldRefreshFetchGroup() not found in
org.opencsta.ctiserver.business.callevents.model.CalledEvent
reason
[source error] _persistence_shouldRefreshFetchGroup() not found in
org.opencsta.ctiserver.business.callevents.model.CalledEvent
javassist.compiler.CompileError
_persistence_shouldRefreshFetchGroup() not found in
org.opencsta.ctiserver.business.callevents.model.CalledEvent
On 22/09/2011, at 1:24 AM, Lenny Primak wrote:
> Have you tried exclude= in your template? That worked for me and is simple.
>
>
>
> On Sep 21, 2011, at 11:18 AM, Chris Mylonas wrote:
>
>> Hi!!
>>
>> It is EclipseLink (glassfish 3.1.1), I've just tried the first time now and
>> it failed again (same reason) but I'll try a few other things based on
>> Thiago's response earlier (re: BeanModel).
>>
>> Here is CalledEvent which the error comes from if you can see anything
>> strange, apologies Thiago for sending it to you directly earlier!!
>>
>> package org.opencsta.ctiserver.business.callevents.model;
>>
>> import java.io.Serializable;
>>
>> import javax.persistence.Entity;
>> import javax.persistence.GeneratedValue;
>> import javax.persistence.GenerationType;
>> import javax.persistence.Id;
>> import javax.persistence.NamedQueries;
>> import javax.persistence.NamedQuery;
>> import javax.persistence.Transient;
>>
>> /**
>> * @author chrismylonas
>> *
>> */
>> @Entity
>> @NamedQueries({ @NamedQuery(name
>> =org.opencsta.ctiserver.business.callevents.model.CalledEvent.QUERY_GETALL,
>> query ="select c FROM CalledEvent c") })
>> public class CalledEvent implements Serializable {
>>
>> /**
>>*
>>*/
>> private static final long serialVersionUID =-35384297244606697L;
>>
>> /**
>>*
>>*/
>> public static final String QUERY_GETALL
>> ="org.opencsta.ctiserver.business.callevents.model.CalledEvent.QUERY_GETALL";
>>
>> /**
>>*
>>*/
>> @Id
>> @GeneratedValue(strategy =GenerationType.IDENTITY)
>> private Long id;
>>
>> /**
>>*
>>*/
>> private String name;
>>
>> /**
>>*
>>*/
>> private String callingParty;
>>
>> /**
>>*
>>*/
>> private String calledParty;
>>
>> /**
>>*
>>*/
>> private String dialedNumber;
>>
>> /**
>>*
>>*/
>> private String trunk;
>>
>> /**
>>*
>>*/
>> private String server;
>>
>> /**
>>* @return
>>*/
>> public Long getId() {
>> return id;
>> }
>>
>> /**
>>* @param id
>>*/
>> public void setId(Long id) {
>> this.id =id;
>> }
>>
>> /**
>>* @return
>>*/
>> public String getName() {
>> return name;
>> }
>>
>> /**
>>* @param name
>>*/
>> public void setName(String name) {
>> this.name =name;
>> }
>>
>> /**
>>* @return
>>*/
>> public String getCallingParty() {
>> return callingParty;
>> }
>>
>> /**
>>* @param callingParty
>>*/
>> public void setCallingParty(String callingParty) {
>> this.callingParty ÊllingParty;
>> }
>>
>> /**
>>* @return
>>*/
>> public String getCalledParty() {
>> return calledParty;
>> }
>>
>> /**
>>* @param calledParty
>>*/
>> public void setCalledParty(String calledParty) {
>> this.calledParty ÊlledParty;
>> }
>>
>> /**
>>* @return
>>*/
>> public String getDialedNumber() {
>> return dialedNumber;
>> }
>>
>> /**
>>* @param dialedNumber
>>*/
>> public void setDialedNumber(String dialedNumber) {
>> this.dialedNumber =dialedNumber;
>> }
>>
>> /**
>>* @return
>>*/
>> public String getTrunk() {
>> return trunk;
>> }
>>
>> /**
>>* @param trunk
>>*/
>> public void setTrunk(String trunk) {
>> this.trunk =trunk;
>> }
>>
>> /**
>>* @return
>>*/
>> public String getServer() {
>> return server;
>> }
>>
>> /**
>>* @param server
>>*/
>> public void setServer(String server) {
>>
Re: Grid, generating conduit, unable to add method java.lang.Object get() to class
Have you tried exclude= in your template? That worked for me and is simple.
On Sep 21, 2011, at 11:18 AM, Chris Mylonas wrote:
> Hi!!
>
> It is EclipseLink (glassfish 3.1.1), I've just tried the first time now and
> it failed again (same reason) but I'll try a few other things based on
> Thiago's response earlier (re: BeanModel).
>
> Here is CalledEvent which the error comes from if you can see anything
> strange, apologies Thiago for sending it to you directly earlier!!
>
> package org.opencsta.ctiserver.business.callevents.model;
>
> import java.io.Serializable;
>
> import javax.persistence.Entity;
> import javax.persistence.GeneratedValue;
> import javax.persistence.GenerationType;
> import javax.persistence.Id;
> import javax.persistence.NamedQueries;
> import javax.persistence.NamedQuery;
> import javax.persistence.Transient;
>
> /**
> * @author chrismylonas
> *
> */
> @Entity
> @NamedQueries({ @NamedQuery(name
> =org.opencsta.ctiserver.business.callevents.model.CalledEvent.QUERY_GETALL,
> query ="select c FROM CalledEvent c") })
> public class CalledEvent implements Serializable {
>
>/**
> *
> */
>private static final long serialVersionUID =-35384297244606697L;
>
>/**
> *
> */
>public static final String QUERY_GETALL
> ="org.opencsta.ctiserver.business.callevents.model.CalledEvent.QUERY_GETALL";
>
>/**
> *
> */
>@Id
>@GeneratedValue(strategy =GenerationType.IDENTITY)
>private Long id;
>
>/**
> *
> */
>private String name;
>
>/**
> *
> */
>private String callingParty;
>
>/**
> *
> */
>private String calledParty;
>
>/**
> *
> */
>private String dialedNumber;
>
>/**
> *
> */
>private String trunk;
>
>/**
> *
> */
>private String server;
>
>/**
> * @return
> */
>public Long getId() {
>return id;
>}
>
>/**
> * @param id
> */
>public void setId(Long id) {
>this.id =id;
>}
>
>/**
> * @return
> */
>public String getName() {
>return name;
>}
>
>/**
> * @param name
> */
>public void setName(String name) {
>this.name =name;
>}
>
>/**
> * @return
> */
>public String getCallingParty() {
>return callingParty;
>}
>
>/**
> * @param callingParty
> */
>public void setCallingParty(String callingParty) {
>this.callingParty ÊllingParty;
>}
>
>/**
> * @return
> */
>public String getCalledParty() {
>return calledParty;
>}
>
>/**
> * @param calledParty
> */
>public void setCalledParty(String calledParty) {
>this.calledParty ÊlledParty;
>}
>
>/**
> * @return
> */
>public String getDialedNumber() {
>return dialedNumber;
>}
>
>/**
> * @param dialedNumber
> */
>public void setDialedNumber(String dialedNumber) {
>this.dialedNumber =dialedNumber;
>}
>
>/**
> * @return
> */
>public String getTrunk() {
>return trunk;
>}
>
>/**
> * @param trunk
> */
>public void setTrunk(String trunk) {
>this.trunk =trunk;
>}
>
>/**
> * @return
> */
>public String getServer() {
>return server;
>}
>
>/**
> * @param server
> */
>public void setServer(String server) {
>this.server =server;
>}
> }
>
>
>
> On 22/09/2011, at 12:53 AM, Lenny Primak wrote:
>
>> This is EclipseLink. I use it and ran into the same problem.
>>
>> On Sep 21, 2011, at 10:28 AM, Lenny Primak wrote:
>>
>>> If you add exclude="_persistence_shouldRefreshFetchGroup"
>>> to your grid definition, this should resolve the problem.
>>>
>>> On Sep 21, 2011, at 3:10 AM, Chris Mylonas wrote:
>>>
Hello Tapestry Users,
I've got a problem with the grid element.
It doesn't happen if I put my List into a Loop element and
build the table.
${calledEvent.id}
${calledEvent.calledParty}
${calledEvent.callingParty}
${calledEvent.dialedNumber}
I'm getting this error when using the grid
Render queue error in SetupRender[Index:grid.columns]: Failure reading
parameter 'model' of component Index:grid: Exception generating conduit
for expression '_persistence_shouldRefreshFetchGroup': Unable to add
method java.lang.Object get(java.lang.Object) to class
$PropertyConduit_1328ac84ee8: [source error]
_persistence_shouldRefreshFetchGroup() not found in
org.opencsta.ctiserver.business.callevents.model.CalledEvent
What does this mean?
I'm using Geoff's @EJB stuff from jumpstart's EJBAnnotationWorker example
I'd really like to use the grid because then I can use the
Re: Grid, generating conduit, unable to add method java.lang.Object get() to class
Hi!!
It is EclipseLink (glassfish 3.1.1), I've just tried the first time now and it
failed again (same reason) but I'll try a few other things based on Thiago's
response earlier (re: BeanModel).
Here is CalledEvent which the error comes from if you can see anything strange,
apologies Thiago for sending it to you directly earlier!!
package org.opencsta.ctiserver.business.callevents.model;
import java.io.Serializable;
import javax.persistence.Entity;
import javax.persistence.GeneratedValue;
import javax.persistence.GenerationType;
import javax.persistence.Id;
import javax.persistence.NamedQueries;
import javax.persistence.NamedQuery;
import javax.persistence.Transient;
/**
* @author chrismylonas
*
*/
@Entity
@NamedQueries({ @NamedQuery(name =
org.opencsta.ctiserver.business.callevents.model.CalledEvent.QUERY_GETALL,
query = "select c FROM CalledEvent c") })
public class CalledEvent implements Serializable {
/**
*
*/
private static final long serialVersionUID = -35384297244606697L;
/**
*
*/
public static final String QUERY_GETALL =
"org.opencsta.ctiserver.business.callevents.model.CalledEvent.QUERY_GETALL";
/**
*
*/
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;
/**
*
*/
private String name;
/**
*
*/
private String callingParty;
/**
*
*/
private String calledParty;
/**
*
*/
private String dialedNumber;
/**
*
*/
private String trunk;
/**
*
*/
private String server;
/**
* @return
*/
public Long getId() {
return id;
}
/**
* @param id
*/
public void setId(Long id) {
this.id = id;
}
/**
* @return
*/
public String getName() {
return name;
}
/**
* @param name
*/
public void setName(String name) {
this.name = name;
}
/**
* @return
*/
public String getCallingParty() {
return callingParty;
}
/**
* @param callingParty
*/
public void setCallingParty(String callingParty) {
this.callingParty = callingParty;
}
/**
* @return
*/
public String getCalledParty() {
return calledParty;
}
/**
* @param calledParty
*/
public void setCalledParty(String calledParty) {
this.calledParty = calledParty;
}
/**
* @return
*/
public String getDialedNumber() {
return dialedNumber;
}
/**
* @param dialedNumber
*/
public void setDialedNumber(String dialedNumber) {
this.dialedNumber = dialedNumber;
}
/**
* @return
*/
public String getTrunk() {
return trunk;
}
/**
* @param trunk
*/
public void setTrunk(String trunk) {
this.trunk = trunk;
}
/**
* @return
*/
public String getServer() {
return server;
}
/**
* @param server
*/
public void setServer(String server) {
this.server = server;
}
}
On 22/09/2011, at 12:53 AM, Lenny Primak wrote:
> This is EclipseLink. I use it and ran into the same problem.
>
> On Sep 21, 2011, at 10:28 AM, Lenny Primak wrote:
>
>> If you add exclude="_persistence_shouldRefreshFetchGroup"
>> to your grid definition, this should resolve the problem.
>>
>> On Sep 21, 2011, at 3:10 AM, Chris Mylonas wrote:
>>
>>> Hello Tapestry Users,
>>>
>>> I've got a problem with the grid element.
>>>
>>>
>>>
>>> It doesn't happen if I put my List into a Loop element and
>>> build the table.
>>>
>>>
>>>
>>> ${calledEvent.id}
>>> ${calledEvent.calledParty}
>>> ${calledEvent.callingParty}
>>> ${calledEvent.dialedNumber}
>>>
>>>
>>>
>>> I'm getting this error when using the grid
>>>
>>> Render queue error in SetupRender[Index:grid.columns]: Failure reading
>>> parameter 'model' of component Index:grid: Exception generating conduit for
>>> expression '_persistence_shouldRefreshFetchGroup': Unable to add method
>>> java.lang.Object get(java.lang.Object) to class
>>> $PropertyConduit_1328ac84ee8: [source error]
>>> _persistence_shouldRefreshFetchGroup() not found in
>>> org.opencsta.ctiserver.business.callevents.model.CalledEvent
Re: Grid, generating conduit, unable to add method java.lang.Object get() to class
Try explicitly providing your own model generated using BeanModelSource.
@Inject
private BeanModelSource bms;
@Inject
private Messages messages;
public BeanModel getMyGridModel(){
return bms.createDisplayModel(CalledEvent.class, messages);
}
On Wed, Sep 21, 2011 at 3:10 AM, Chris Mylonas wrote:
> Hello Tapestry Users,
>
> I've got a problem with the grid element.
>
>
>
> It doesn't happen if I put my List into a Loop element and
> build the table.
>
>
>
>${calledEvent.id}
>${calledEvent.calledParty}
>${calledEvent.callingParty}
>${calledEvent.dialedNumber}
>
>
>
> I'm getting this error when using the grid
>
> Render queue error in SetupRender[Index:grid.columns]: Failure reading
> parameter 'model' of component Index:grid: Exception generating conduit for
> expression '_persistence_shouldRefreshFetchGroup': Unable to add method
> java.lang.Object get(java.lang.Object) to class
> $PropertyConduit_1328ac84ee8: [source error]
> _persistence_shouldRefreshFetchGroup() not found in
> org.opencsta.ctiserver.business.callevents.model.CalledEvent
>
>
> What does this mean?
>
> I'm using Geoff's @EJB stuff from jumpstart's EJBAnnotationWorker example
>
>
> I'd really like to use the grid because then I can use the rowsPerPage
> parameter for "developer productivity" :P
>
> Thanks for any help,
> Chris
--
Jonathan Barker
ITStrategic
Re: Grid, generating conduit, unable to add method java.lang.Object get() to class
This is EclipseLink. I use it and ran into the same problem.
On Sep 21, 2011, at 10:28 AM, Lenny Primak wrote:
> If you add exclude="_persistence_shouldRefreshFetchGroup"
> to your grid definition, this should resolve the problem.
>
> On Sep 21, 2011, at 3:10 AM, Chris Mylonas wrote:
>
>> Hello Tapestry Users,
>>
>> I've got a problem with the grid element.
>>
>>
>>
>> It doesn't happen if I put my List into a Loop element and
>> build the table.
>>
>>
>>
>> ${calledEvent.id}
>> ${calledEvent.calledParty}
>> ${calledEvent.callingParty}
>> ${calledEvent.dialedNumber}
>>
>>
>>
>> I'm getting this error when using the grid
>>
>> Render queue error in SetupRender[Index:grid.columns]: Failure reading
>> parameter 'model' of component Index:grid: Exception generating conduit for
>> expression '_persistence_shouldRefreshFetchGroup': Unable to add method
>> java.lang.Object get(java.lang.Object) to class
>> $PropertyConduit_1328ac84ee8: [source error]
>> _persistence_shouldRefreshFetchGroup() not found in
>> org.opencsta.ctiserver.business.callevents.model.CalledEvent
>>
>>
>> What does this mean?
>>
>> I'm using Geoff's @EJB stuff from jumpstart's EJBAnnotationWorker example
>>
>>
>> I'd really like to use the grid because then I can use the rowsPerPage
>> parameter for "developer productivity" :P
>>
>> Thanks for any help,
>> Chris
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Grid, generating conduit, unable to add method java.lang.Object get() to class
On Wed, 21 Sep 2011 11:28:47 -0300, Lenny Primak wrote: If you add exclude="_persistence_shouldRefreshFetchGroup" to your grid definition, this should resolve the problem. Which JPA implementation are you using? As Lenny noted, it seems it's adding stuff to your entity classes and BeanModelSource is tripping on it. -- Thiago H. de Paula Figueiredo Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor Owner, Ars Machina Tecnologia da Informação Ltda. http://www.arsmachina.com.br - To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
Re: Grid, generating conduit, unable to add method java.lang.Object get() to class
If you add exclude="_persistence_shouldRefreshFetchGroup"
to your grid definition, this should resolve the problem.
On Sep 21, 2011, at 3:10 AM, Chris Mylonas wrote:
> Hello Tapestry Users,
>
> I've got a problem with the grid element.
>
>
>
> It doesn't happen if I put my List into a Loop element and build
> the table.
>
>
>
> ${calledEvent.id}
> ${calledEvent.calledParty}
> ${calledEvent.callingParty}
> ${calledEvent.dialedNumber}
>
>
>
> I'm getting this error when using the grid
>
> Render queue error in SetupRender[Index:grid.columns]: Failure reading
> parameter 'model' of component Index:grid: Exception generating conduit for
> expression '_persistence_shouldRefreshFetchGroup': Unable to add method
> java.lang.Object get(java.lang.Object) to class $PropertyConduit_1328ac84ee8:
> [source error] _persistence_shouldRefreshFetchGroup() not found in
> org.opencsta.ctiserver.business.callevents.model.CalledEvent
>
>
> What does this mean?
>
> I'm using Geoff's @EJB stuff from jumpstart's EJBAnnotationWorker example
>
>
> I'd really like to use the grid because then I can use the rowsPerPage
> parameter for "developer productivity" :P
>
> Thanks for any help,
> Chris
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
