No, neither tapestry-jpa nor tynamo-jpa have special logic for weaving.
Please check out the weaving section here:
http://wiki.eclipse.org/Using_EclipseLink_JPA_Extensions_(ELUG)#Using_EclipseLink_JPA_Weaving
Looks like you need to configure EclipseLink weaving.
On Sat, Oct 22, 2011 at 5:21 AM,
Are you using single or multiple datasources in persistence.xml?
Are you putting your entity classes in entities package?
tapestry-jpa is more sensitive about these thing then Tynamo is.
On Oct 22, 2011, at 6:54 AM, Dimitris Zenios wrote:
> there regarding weaving.So there must be something else
Jesse i have looked at tynamo-jpa source code and there is nothing in
there regarding weaving.So there must be something else.Maybe igor
(Creator of tapestry-jpa) can help us.
On Sat, Oct 22, 2011 at 6:21 AM, jesse wrote:
> Maybe tynamo does something to get weaving working that tapestry-jpa does
Maybe tynamo does something to get weaving working that tapestry-jpa doesn't
do?
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/Problems-using-JPA-with-5-3-tp6898469p6919297.html
Sent from the Tapestry Users mailing list archive at Nabble.com.
--
Nope, still cant get around it. This is part of the error I get
"The class was not weaved properly - for EE deployments, check the module
order in the application.xml deployment descriptor and verify that the
module containing the persistence unit is ahead of any other module that
uses it."
Doe
Jesse.Did you manage to find the cause of the problem?From the bug
that you reported there is nothing that indicated that its t5 fault.
On Thu, Oct 20, 2011 at 10:29 PM, Lenny Primak wrote:
> I don't understand what this has anything to do with Tapestry.
> Doesn't seem like Tapestry bug at all.
I don't understand what this has anything to do with Tapestry.
Doesn't seem like Tapestry bug at all.
On Oct 20, 2011, at 3:09 PM, jesse wrote:
> Here's some explanation about this from eclipselink:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=323403
>
> Can a commiter please tell me how
On Thu, 20 Oct 2011 17:09:14 -0200, jesse wrote:
Here's some explanation about this from eclipselink:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=323403
Can a commiter please tell me how and where I can report a T5 bug?
Here: https://issues.apache.org/jira/browse/TAP5
--
Thiago H. de Paul
Here's some explanation about this from eclipselink:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=323403
Can a commiter please tell me how and where I can report a T5 bug?
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/Problems-using-JPA-with-5-3-tp6898469p6914456.htm
I am running inside Glassfish (3.1.1) and everything works 100%,
including weaving.
On Oct 20, 2011, at 1:05 PM, Dimitris Zenios wrote:
> I tried using eclipselink with tapestry-jpa and i had the same errors
> as you with jetty.I though that the problem was that i was not doing
> weaving so i sto
I tried using eclipselink with tapestry-jpa and i had the same errors
as you with jetty.I though that the problem was that i was not doing
weaving so i stopped there and revert back to hibernate.If what you
are saying is correct (When you run your app in a j2ee container (like
tomcat and jetty, bot
I really appreciate your quick response, and thanks for trying to help!
Yes, my app uses weaving - otherwise it wouldn't work with lazy loaded
entities. Eclipselink uses weaving by default. When you run your app in a
j2ee container (like tomcat and jetty, both of which I'm using) you don't
need
Jesse most probably t5 is not doing anything.Are you doing static
weaving?And if yes can you post maven plug in that weaves your
classes?Maybe you are not doing weaving at all.Thats why eclipselink
complains
On Thu, Oct 20, 2011 at 6:36 PM, jesse wrote:
> Yes, I agree that the problem is with wea
Yes, I agree that the problem is with weaving, but the question I have is:
what in T5 is causing eclipselink to have the problem with weaving.
--
View this message in context:
http://tapestry-users.832.n2.nabble.com/Problems-using-JPA-with-5-3-tp6898469p6913386.html
Sent from the Tapestry Users
Thanks for the suggestion but the symbol in my persistence.xml gets replaced
by mvn when it filters my resources. I've set it up that way in my pom, and
as I've said previously, this works fine using tynamo jpa, so if it's a
problem with my persistence.xml it's not going to be an obvious one like
Jess i think you problem is with weaving.Try adding in your persistence.xml
and see if it works.Have in mind though that disabling weaving is not
a good option.but you can try just to see if this is the problem
On Thu, Oct 20, 2011 at 11:25 AM, Igor Drobiazko
wrote:
> Might it be a Glassfish iss
Might it be a Glassfish issue? Check this out:
http://java.net/jira/browse/GLASSFISH-13688
I would also use the 2.0 as persistence version. Apart from that you are
using a tapestry symbol inside persistence.xml. This is not going to work.
On Thu, Oct 20, 2011 at 3:58 AM, jesse wrote:
> So here's
I don't see anything weird with your configuration.
I do not have adviseTransactionally() method in my code,
and I am using Glassfish, so no EclipseLink or javax.persistence in my pom.xml,
and JPA stuff works perfectly.
On Oct 19, 2011, at 9:58 PM, jesse wrote:
> So here's my configuration (thoug
So here's my configuration (though there's not much to it):
In addition to the T5 and tapestry-jpa dependencies in my pom, I also have
these:
org.eclipse.persistence
javax.persistence
2.0.3
org.eclipse.persistence
There must be something wrong either with your configuration or your
environment. You need to provide more details in order to get help.
On Sun, Oct 16, 2011 at 9:54 PM, jesse wrote:
> Hi, I've run in to a couple of JPA related issues that are keeping me from
> moving to 5.3. My app previously
Jesse i am using tapestry-jpa with hibernate and it works great except
the problem of value encoder.Maybe you did something wrong in the
persistence.xml or you didn't place it in the correct location.
On Mon, Oct 17, 2011 at 8:07 PM, jesse wrote:
> Thanks Thiago,
>
> I have read the documentation
Thanks Thiago,
I have read the documentation on the new JPA stuff in Tapestry. I'm pretty
sure I have it set up correctly. I did everything the documentation
suggests and I'm still having the issue. The only reason I mentioned tynamo
was just to make it clear that I did at one point have JPA wo
Sorry wrong reply :).I though it was for a previous mail
On Mon, Oct 17, 2011 at 2:38 PM, Dimitris Zenios
wrote:
> Thiago i am using tapestry-jpa.I haven’t tested tynamo-jpa.From what i
> can see at the source code of JpaModule.java there is a method
>
>
> @Contribute(ValueEncoderSource.class)
Thiago i am using tapestry-jpa.I haven’t tested tynamo-jpa.From what i
can see at the source code of JpaModule.java there is a method
@Contribute(ValueEncoderSource.class)
public static void provideValueEncoders(final
MappedConfiguration configuration,
@Symbol(JpaSymbols.PROVIDE_ENTITY_V
On Sun, 16 Oct 2011 17:54:29 -0200, jesse wrote:
My app works great with tynamo JPA, tynamo resteasy, eclipselink (2.2.1),
and Tapestry 5.2.6. I had to do one small hack due to the fact that the
tynamo code relies on Defense. No big deal though, and it's all working.
I've tried to switch to
Hi, I've run in to a couple of JPA related issues that are keeping me from
moving to 5.3. My app previously worked fine with tynamo jpa, but now
throws eclipselink exceptions and won't start with Tapestry 5.3
(5.3-beta-22).
My app works great with tynamo JPA, tynamo resteasy, eclipselink (2.2.1),
26 matches
Mail list logo
