[jira] Updated: (OPENJPA-217) query param value issue in select query

2007-04-13 Thread sharath.h (JIRA) 

 [ 
https://issues.apache.org/jira/browse/OPENJPA-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

sharath.h updated OPENJPA-217:
--

Description: 
Consider a scenario where we have an entity class as shown below:
class A
{
 long id;
String str1;
String str2;
}
Say for str2 attribute there will be length constraint something like 

  
 

Now say i have a jpql select query as shown below :
Query q = em.createQuery("select t from A t where t.str2:paramvalue");
q.setParameter("paramvalue", "23");

The above query return empty result set even though the records are present in 
table.
But when i set the value from "23" to "23  " (i.e. with trailing 2 spaces) it 
works.


Can the padding of additional empty spaces be taken care default by jpa itself 
for select kind of queries.



  was:
Consider a scenario where we have an entity class as shown below:
class A
{
 long id;
String str1;
String str2;
}
Say for str2 attribute there will be length constraint something like 

  
 

Now say i have a jpql select query as shown below :
Query q = em.createQuery("select t from A t where t.str2:paramvalue");
q.setParameter("paramvalue", "23");

The above query return empty result set even though the records are present in 
table.
But when i set the value from "23" to "23  " (i.e. with trailing 2 spaces).


Can the padding of additional empty spaces be taken care default by jpa itself 
for select kind of queries.




> query param value issue in select query
> ---
>
> Key: OPENJPA-217
> URL: https://issues.apache.org/jira/browse/OPENJPA-217
> Project: OpenJPA
>  Issue Type: Bug
>  Components: jpa, query
>Affects Versions: 0.9.6
>Reporter: sharath.h
>Priority: Minor
>
> Consider a scenario where we have an entity class as shown below:
> class A
> {
>  long id;
> String str1;
> String str2;
> }
> Say for str2 attribute there will be length constraint something like 
> 
>   
>  
> Now say i have a jpql select query as shown below :
> Query q = em.createQuery("select t from A t where t.str2:paramvalue");
> q.setParameter("paramvalue", "23");
> The above query return empty result set even though the records are present 
> in table.
> But when i set the value from "23" to "23  " (i.e. with trailing 2 spaces) it 
> works.
> Can the padding of additional empty spaces be taken care default by jpa 
> itself for select kind of queries.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (OPENJPA-217) query param value issue in select query

2007-04-13 Thread sharath.h (JIRA) 
query param value issue in select query
---

 Key: OPENJPA-217
 URL: https://issues.apache.org/jira/browse/OPENJPA-217
 Project: OpenJPA
  Issue Type: Bug
  Components: jpa, query
Affects Versions: 0.9.6
Reporter: sharath.h
Priority: Minor


Consider a scenario where we have an entity class as shown below:
class A
{
 long id;
String str1;
String str2;
}
Say for str2 attribute there will be length constraint something like 

  
 

Now say i have a jpql select query as shown below :
Query q = em.createQuery("select t from A t where t.str2:paramvalue");
q.setParameter("paramvalue", "23");

The above query return empty result set even though the records are present in 
table.
But when i set the value from "23" to "23  " (i.e. with trailing 2 spaces).


Can the padding of additional empty spaces be taken care default by jpa itself 
for select kind of queries.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: (No)existing table in SQL server

2007-04-13 Thread armad 


Jacek Laskowski-4 wrote:
> 
> On 4/13/07, armad <[EMAIL PROTECTED]> wrote:
> 
>> I can't send you the application :(
> 
> Is there a way to trim the application so that the issue still exists,
> but you don't need to share the whole app? It would be of great help
> if we reproduced the issue.
> 
> 

Ok, below is my Operator class :


---
...
@Entity
public class Operator implements Serializable {

static final long serialVersionUID = 0L;

@Id
@GeneratedValue(strategy = GenerationType.AUTO)
private long id;

private String firstName;
private String secondName;
private String surname;
private String pesel;
@Temporal(value = TemporalType.DATE)
private Date beginDate;
@Temporal(value = TemporalType.DATE)
private Date endDate;
@Temporal(value = TemporalType.DATE)
private Date entryDate;
...
---


If You would like to see other files please inform me.

regards,
armad
-- 
View this message in context: 
http://www.nabble.com/%28No%29existing-table-in-SQL-server-tf3565587.html#a9987621
Sent from the open-jpa-dev mailing list archive at Nabble.com.

Re: [VOTE] publish openjpa 0.9.7-incubating release

2007-04-13 Thread Craig L Russell 

Hi Mike,

I now understand that your message only mentioned a subset of the  
artifacts that we're planning on publishing for the release of 0.9.7.


On Apr 13, 2007, at 1:54 PM, Michael Dick wrote:

Marc beat me to it, but in case this helps here's the xml that can  
be used

to access the staging repository  :

   
   
   staging-repository
   mikedd's staging repository
   

http://people.apache.org/~mikedd/staging-repositorypeople.apache.org/%7Emikedd/staging-repository>

   
   
   . . .
   


All the OpenJPA artifacts can be accessed this way (at least I was  
able to
download them). If there are other artifacts that we need to  
publish then
I'll go ahead and put them on people.apache.org/~mikedd too.  Maybe  
we just
need to include these instructions in the email that we send out  
for the

vote?


Yes, I think this would make it clear that we're not releasing just  
the binary and source zip files but the binary maven jar and pom  
artifacts as well. It was the message not the staging of the  
artifacts that threw me off.


Thanks!

Craig


Thanks,


On 4/13/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote:


Craig-

> I'm really asking that the 0.9.7 release that we plan to put into
> the incubating repository needs to be put to a vote at the same
> time as we release the other artifacts. The pom.xml and the  
openjpa-

> all.0.9.7-incubating.jar should be part of the vote and available
> in the staging repository.

I'm not sure I completely understand your issue, but I am guessing
you are either asking whether other maven-friendly jar artifacts were
created for the release, or else whether those jar artifacts need to
be listed and voted on.

In the previous release, we just voted on the final binary (http://
people.apache.org/~mikedd/staging-repository/org/apache/openjpa/
openjpa-project/0.9.7-incubating/openjpa-project-0.9.7-incubating-
binary.zip). The deploy process does also deploy the other module
jars (e.g., see  http://people.apache.org/~mikedd/staging-repository/
org/apache/openjpa/openjpa-all/0.9.7-incubating/), so you should be
able access them in a pom.xml just like any repository.

AFAIK, this is how all the other projects that use Maven have done it
(e.g., ActiveMQ). Since the other deployed artifacts are either
identical to, or derivative from, the binary assembly, it seems to me
that listing every uploaded artifact might be needlessly cumbersome.


Please let me know if I have mis-understood your issue.





On Apr 13, 2007, at 12:40 PM, Craig L Russell wrote:

> Hi Marc,
>
> Artifacts need to be approved (voted on by the PMC) before they are
> put into repositories. The 0.9.6 release was put into the
> incubating repository only after it was approved by the IPMC.
>
> I'm really asking that the 0.9.7 release that we plan to put into
> the incubating repository needs to be put to a vote at the same
> time as we release the other artifacts. The pom.xml and the  
openjpa-

> all.0.9.7-incubating.jar should be part of the vote and available
> in the staging repository.
>
> Craig
>
> On Apr 13, 2007, at 12:09 PM, Marc Prud'hommeaux wrote:
>
>> Craig-
>>
>>> I thought we were going to also release a maven download for the
>>> jar file containing all the openjpa stuff and a pom that contains
>>> the dependencies. This would enable folks using maven to simply
>>> put the five lines of code naming the dependency into their pom
>>> and put the incubating repository into their maven repositories
>>> list and they would be done.
>>
>> Note that they can do that already with the existing artifacts,
>> since Maven downloads transitive dependencies. For example, this
>> pom.xml works fine for me in that it downloads and uses all of the
>> OpenJPA libraries and dependencies:
>>
>> 
>> 
>> 4.0.0
>> some-project
>> some-artifact
>> jar
>> My Project
>> 1.0.0
>> 
>> 
>> apache-snapshots
>> http://people.apache.org/repo/m2-incubating-
>> repository
>> 
>> 
>> 
>> 
>> org.apache.openjpa
>> openjpa-all
>> 0.9.6-incubating
>> 
>> 
>> 
>>
>>
>> There might be some other good reasons to make a separate
>> distribution that bundles all of the jars into a single uber-jar,
>> but, as I mentioned before, I personally don't think it is worth
>> the effort, especially for a project that is so component- 
oriented.

>>
>>
>>
>>
>>
>> On Apr 13, 2007, at 11:55 AM, Craig L Russell wrote:
>>
>>> Hi Michael,
>>>
>>> Thanks for all the work.
>>>
>>> I thought we were going to also release a maven download for the
>>> jar file containing all the openjpa stuff and a pom that contains
>>> the dependencies. This would enable folks using maven to simply
>>> put the five lines of code naming the dependency into their pom
>>> and put the incubating repository into their maven repositories
>>> list and they would be done.
>>>
>>> Was I just dreaming

Re: [VOTE] publish openjpa 0.9.7-incubating release

2007-04-13 Thread Michael Dick 

Marc beat me to it, but in case this helps here's the xml that can be used
to access the staging repository  :

   
   
   staging-repository
   mikedd's staging repository
   

http://people.apache.org/~mikedd/staging-repository
   
   
   . . .
   


All the OpenJPA artifacts can be accessed this way (at least I was able to
download them). If there are other artifacts that we need to publish then
I'll go ahead and put them on people.apache.org/~mikedd too.  Maybe we just
need to include these instructions in the email that we send out for the
vote?

Thanks,


On 4/13/07, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote:


Craig-

> I'm really asking that the 0.9.7 release that we plan to put into
> the incubating repository needs to be put to a vote at the same
> time as we release the other artifacts. The pom.xml and the openjpa-
> all.0.9.7-incubating.jar should be part of the vote and available
> in the staging repository.

I'm not sure I completely understand your issue, but I am guessing
you are either asking whether other maven-friendly jar artifacts were
created for the release, or else whether those jar artifacts need to
be listed and voted on.

In the previous release, we just voted on the final binary (http://
people.apache.org/~mikedd/staging-repository/org/apache/openjpa/
openjpa-project/0.9.7-incubating/openjpa-project-0.9.7-incubating-
binary.zip). The deploy process does also deploy the other module
jars (e.g., see  http://people.apache.org/~mikedd/staging-repository/
org/apache/openjpa/openjpa-all/0.9.7-incubating/), so you should be
able access them in a pom.xml just like any repository.

AFAIK, this is how all the other projects that use Maven have done it
(e.g., ActiveMQ). Since the other deployed artifacts are either
identical to, or derivative from, the binary assembly, it seems to me
that listing every uploaded artifact might be needlessly cumbersome.


Please let me know if I have mis-understood your issue.





On Apr 13, 2007, at 12:40 PM, Craig L Russell wrote:

> Hi Marc,
>
> Artifacts need to be approved (voted on by the PMC) before they are
> put into repositories. The 0.9.6 release was put into the
> incubating repository only after it was approved by the IPMC.
>
> I'm really asking that the 0.9.7 release that we plan to put into
> the incubating repository needs to be put to a vote at the same
> time as we release the other artifacts. The pom.xml and the openjpa-
> all.0.9.7-incubating.jar should be part of the vote and available
> in the staging repository.
>
> Craig
>
> On Apr 13, 2007, at 12:09 PM, Marc Prud'hommeaux wrote:
>
>> Craig-
>>
>>> I thought we were going to also release a maven download for the
>>> jar file containing all the openjpa stuff and a pom that contains
>>> the dependencies. This would enable folks using maven to simply
>>> put the five lines of code naming the dependency into their pom
>>> and put the incubating repository into their maven repositories
>>> list and they would be done.
>>
>> Note that they can do that already with the existing artifacts,
>> since Maven downloads transitive dependencies. For example, this
>> pom.xml works fine for me in that it downloads and uses all of the
>> OpenJPA libraries and dependencies:
>>
>> 
>> 
>> 4.0.0
>> some-project
>> some-artifact
>> jar
>> My Project
>> 1.0.0
>> 
>> 
>> apache-snapshots
>> http://people.apache.org/repo/m2-incubating-
>> repository
>> 
>> 
>> 
>> 
>> org.apache.openjpa
>> openjpa-all
>> 0.9.6-incubating
>> 
>> 
>> 
>>
>>
>> There might be some other good reasons to make a separate
>> distribution that bundles all of the jars into a single uber-jar,
>> but, as I mentioned before, I personally don't think it is worth
>> the effort, especially for a project that is so component-oriented.
>>
>>
>>
>>
>>
>> On Apr 13, 2007, at 11:55 AM, Craig L Russell wrote:
>>
>>> Hi Michael,
>>>
>>> Thanks for all the work.
>>>
>>> I thought we were going to also release a maven download for the
>>> jar file containing all the openjpa stuff and a pom that contains
>>> the dependencies. This would enable folks using maven to simply
>>> put the five lines of code naming the dependency into their pom
>>> and put the incubating repository into their maven repositories
>>> list and they would be done.
>>>
>>> Was I just dreaming this up?
>>>
>>> Thanks,
>>>
>>> Craig
>>>
>>> On Apr 12, 2007, at 3:20 PM, Michael Dick wrote:
>>>
 OpenJPA People-

 In accordance with the Incubating Releases guidelines at
 http://incubator.apache.org/incubation/
 Incubation_Policy.html#Releases ,
 I've taken a shot at making a release and start a vote on
 publishing a "
 0.9.7-incubating" release of OpenJPA.

 The release candidate is at:
 http://people.apache.

Re: (No)existing table in SQL server

2007-04-13 Thread Jacek Laskowski 

On 4/13/07, armad <[EMAIL PROTECTED]> wrote:


I can't send you the application :(


Is there a way to trim the application so that the issue still exists,
but you don't need to share the whole app? It would be of great help
if we reproduced the issue.

Jacek

--
Jacek Laskowski
http://www.JacekLaskowski.pl

Re: (No)existing table in SQL server

2007-04-13 Thread armad 


Jacek Laskowski-4 wrote:
> 
> If it's possible, send the application to me so I could take a look at it.
> 

Hi,

I can't send you the application :(


Jacek Laskowski-4 wrote:
> 
> BTW, I wouldn't call your application ok for it's running smoothly
> with TopLink and Hibernate. They're quite a few differences between
> these JPA providers yet they (are to) support the same spec.
> 

Yes, I know it :) 
I will try use OpenJPA with other database. If I will find a answer for my
question, I will post it on this list and polish mailing list too.

regards and thanks,
armad



-- 
View this message in context: 
http://www.nabble.com/%28No%29existing-table-in-SQL-server-tf3565587.html#a9986199
Sent from the open-jpa-dev mailing list archive at Nabble.com.

Re: [VOTE] publish openjpa 0.9.7-incubating release

2007-04-13 Thread Marc Prud'hommeaux 

Craig-

I'm really asking that the 0.9.7 release that we plan to put into  
the incubating repository needs to be put to a vote at the same  
time as we release the other artifacts. The pom.xml and the openjpa- 
all.0.9.7-incubating.jar should be part of the vote and available  
in the staging repository.


I'm not sure I completely understand your issue, but I am guessing  
you are either asking whether other maven-friendly jar artifacts were  
created for the release, or else whether those jar artifacts need to  
be listed and voted on.


In the previous release, we just voted on the final binary (http:// 
people.apache.org/~mikedd/staging-repository/org/apache/openjpa/ 
openjpa-project/0.9.7-incubating/openjpa-project-0.9.7-incubating- 
binary.zip). The deploy process does also deploy the other module  
jars (e.g., see  http://people.apache.org/~mikedd/staging-repository/ 
org/apache/openjpa/openjpa-all/0.9.7-incubating/), so you should be  
able access them in a pom.xml just like any repository.


AFAIK, this is how all the other projects that use Maven have done it  
(e.g., ActiveMQ). Since the other deployed artifacts are either  
identical to, or derivative from, the binary assembly, it seems to me  
that listing every uploaded artifact might be needlessly cumbersome.



Please let me know if I have mis-understood your issue.





On Apr 13, 2007, at 12:40 PM, Craig L Russell wrote:


Hi Marc,

Artifacts need to be approved (voted on by the PMC) before they are  
put into repositories. The 0.9.6 release was put into the  
incubating repository only after it was approved by the IPMC.


I'm really asking that the 0.9.7 release that we plan to put into  
the incubating repository needs to be put to a vote at the same  
time as we release the other artifacts. The pom.xml and the openjpa- 
all.0.9.7-incubating.jar should be part of the vote and available  
in the staging repository.


Craig

On Apr 13, 2007, at 12:09 PM, Marc Prud'hommeaux wrote:


Craig-

I thought we were going to also release a maven download for the  
jar file containing all the openjpa stuff and a pom that contains  
the dependencies. This would enable folks using maven to simply  
put the five lines of code naming the dependency into their pom  
and put the incubating repository into their maven repositories  
list and they would be done.


Note that they can do that already with the existing artifacts,  
since Maven downloads transitive dependencies. For example, this  
pom.xml works fine for me in that it downloads and uses all of the  
OpenJPA libraries and dependencies:




4.0.0
some-project
some-artifact
jar
My Project
1.0.0


apache-snapshots
http://people.apache.org/repo/m2-incubating- 
repository





org.apache.openjpa
openjpa-all
0.9.6-incubating





There might be some other good reasons to make a separate  
distribution that bundles all of the jars into a single uber-jar,  
but, as I mentioned before, I personally don't think it is worth  
the effort, especially for a project that is so component-oriented.






On Apr 13, 2007, at 11:55 AM, Craig L Russell wrote:


Hi Michael,

Thanks for all the work.

I thought we were going to also release a maven download for the  
jar file containing all the openjpa stuff and a pom that contains  
the dependencies. This would enable folks using maven to simply  
put the five lines of code naming the dependency into their pom  
and put the incubating repository into their maven repositories  
list and they would be done.


Was I just dreaming this up?

Thanks,

Craig

On Apr 12, 2007, at 3:20 PM, Michael Dick wrote:


OpenJPA People-

In accordance with the Incubating Releases guidelines at
http://incubator.apache.org/incubation/ 
Incubation_Policy.html#Releases ,
I've taken a shot at making a release and start a vote on  
publishing a "

0.9.7-incubating" release of OpenJPA.

The release candidate is at:
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-binary.zip


The GPG signature and MD5 checksums are at:
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-binary.zip.asc
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-binary.zip.md5


The sources, sources GPG signature and sources MD5 checksum are  
available

at:
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-source.zip
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-source.zip.asc
http://people.apache.org/~mikedd/staging-repository/org/apach

Re: [VOTE] publish openjpa 0.9.7-incubating release

2007-04-13 Thread Craig L Russell 

Hi Marc,

Artifacts need to be approved (voted on by the PMC) before they are  
put into repositories. The 0.9.6 release was put into the incubating  
repository only after it was approved by the IPMC.


I'm really asking that the 0.9.7 release that we plan to put into the  
incubating repository needs to be put to a vote at the same time as  
we release the other artifacts. The pom.xml and the openjpa-all.0.9.7- 
incubating.jar should be part of the vote and available in the  
staging repository.


Craig

On Apr 13, 2007, at 12:09 PM, Marc Prud'hommeaux wrote:


Craig-

I thought we were going to also release a maven download for the  
jar file containing all the openjpa stuff and a pom that contains  
the dependencies. This would enable folks using maven to simply  
put the five lines of code naming the dependency into their pom  
and put the incubating repository into their maven repositories  
list and they would be done.


Note that they can do that already with the existing artifacts,  
since Maven downloads transitive dependencies. For example, this  
pom.xml works fine for me in that it downloads and uses all of the  
OpenJPA libraries and dependencies:




4.0.0
some-project
some-artifact
jar
My Project
1.0.0


apache-snapshots
http://people.apache.org/repo/m2-incubating- 
repository





org.apache.openjpa
openjpa-all
0.9.6-incubating





There might be some other good reasons to make a separate  
distribution that bundles all of the jars into a single uber-jar,  
but, as I mentioned before, I personally don't think it is worth  
the effort, especially for a project that is so component-oriented.






On Apr 13, 2007, at 11:55 AM, Craig L Russell wrote:


Hi Michael,

Thanks for all the work.

I thought we were going to also release a maven download for the  
jar file containing all the openjpa stuff and a pom that contains  
the dependencies. This would enable folks using maven to simply  
put the five lines of code naming the dependency into their pom  
and put the incubating repository into their maven repositories  
list and they would be done.


Was I just dreaming this up?

Thanks,

Craig

On Apr 12, 2007, at 3:20 PM, Michael Dick wrote:


OpenJPA People-

In accordance with the Incubating Releases guidelines at
http://incubator.apache.org/incubation/ 
Incubation_Policy.html#Releases ,
I've taken a shot at making a release and start a vote on  
publishing a "

0.9.7-incubating" release of OpenJPA.

The release candidate is at:
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-binary.zip


The GPG signature and MD5 checksums are at:
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-binary.zip.asc
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-binary.zip.md5


The sources, sources GPG signature and sources MD5 checksum are  
available

at:
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-source.zip
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-source.zip.asc
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-source.zip.md5


I have tagged the sources at:
https://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.7- 
incubating/


Please vote to publish this incubating release on the project Web  
page:


  http://cwiki.apache.org/openjpa/downloads.html

This vote will remain open until 5:20 CST on Tuesday April 17th  
(three

business days).
A "+1" indicates that you approve of the release, a "-1" indicates a
vote against making a release

--
-Michael Dick


Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/ 
jdo

408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!





Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!



smime.p7s
Description: S/MIME cryptographic signature

Re: [VOTE] publish openjpa 0.9.7-incubating release

2007-04-13 Thread Marc Prud'hommeaux 

Craig-

I thought we were going to also release a maven download for the  
jar file containing all the openjpa stuff and a pom that contains  
the dependencies. This would enable folks using maven to simply put  
the five lines of code naming the dependency into their pom and put  
the incubating repository into their maven repositories list and  
they would be done.


Note that they can do that already with the existing artifacts, since  
Maven downloads transitive dependencies. For example, this pom.xml  
works fine for me in that it downloads and uses all of the OpenJPA  
libraries and dependencies:




4.0.0
some-project
some-artifact
jar
My Project
1.0.0


apache-snapshots
http://people.apache.org/repo/m2-incubating- 
repository





org.apache.openjpa
openjpa-all
0.9.6-incubating





There might be some other good reasons to make a separate  
distribution that bundles all of the jars into a single uber-jar,  
but, as I mentioned before, I personally don't think it is worth the  
effort, especially for a project that is so component-oriented.






On Apr 13, 2007, at 11:55 AM, Craig L Russell wrote:


Hi Michael,

Thanks for all the work.

I thought we were going to also release a maven download for the  
jar file containing all the openjpa stuff and a pom that contains  
the dependencies. This would enable folks using maven to simply put  
the five lines of code naming the dependency into their pom and put  
the incubating repository into their maven repositories list and  
they would be done.


Was I just dreaming this up?

Thanks,

Craig

On Apr 12, 2007, at 3:20 PM, Michael Dick wrote:


OpenJPA People-

In accordance with the Incubating Releases guidelines at
http://incubator.apache.org/incubation/ 
Incubation_Policy.html#Releases ,
I've taken a shot at making a release and start a vote on  
publishing a "

0.9.7-incubating" release of OpenJPA.

The release candidate is at:
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-binary.zip


The GPG signature and MD5 checksums are at:
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-binary.zip.asc
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-binary.zip.md5


The sources, sources GPG signature and sources MD5 checksum are  
available

at:
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-source.zip
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-source.zip.asc
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-source.zip.md5


I have tagged the sources at:
https://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.7- 
incubating/


Please vote to publish this incubating release on the project Web  
page:


  http://cwiki.apache.org/openjpa/downloads.html

This vote will remain open until 5:20 CST on Tuesday April 17th  
(three

business days).
A "+1" indicates that you approve of the release, a "-1" indicates a
vote against making a release

--
-Michael Dick


Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!

Re: [VOTE] publish openjpa 0.9.7-incubating release

2007-04-13 Thread Craig L Russell 

Hi Michael,

Thanks for all the work.

I thought we were going to also release a maven download for the jar  
file containing all the openjpa stuff and a pom that contains the  
dependencies. This would enable folks using maven to simply put the  
five lines of code naming the dependency into their pom and put the  
incubating repository into their maven repositories list and they  
would be done.


Was I just dreaming this up?

Thanks,

Craig

On Apr 12, 2007, at 3:20 PM, Michael Dick wrote:


OpenJPA People-

In accordance with the Incubating Releases guidelines at
http://incubator.apache.org/incubation/ 
Incubation_Policy.html#Releases ,
I've taken a shot at making a release and start a vote on  
publishing a "

0.9.7-incubating" release of OpenJPA.

The release candidate is at:
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-binary.zip


The GPG signature and MD5 checksums are at:
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-binary.zip.asc
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-binary.zip.md5


The sources, sources GPG signature and sources MD5 checksum are  
available

at:
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-source.zip
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-source.zip.asc
http://people.apache.org/~mikedd/staging-repository/org/apache/ 
openjpa/openjpa-project/0.9.7-incubating/openjpa-project-0.9.7- 
incubating-source.zip.md5


I have tagged the sources at:
https://svn.apache.org/repos/asf/incubator/openjpa/tags/0.9.7- 
incubating/


Please vote to publish this incubating release on the project Web  
page:


  http://cwiki.apache.org/openjpa/downloads.html

This vote will remain open until 5:20 CST on Tuesday April 17th (three
business days).
A "+1" indicates that you approve of the release, a "-1" indicates a
vote against making a release

--
-Michael Dick


Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!



smime.p7s
Description: S/MIME cryptographic signature

Re: Problem trying to persist an entity into Derby from a Web App deployed to Geronimo

2007-04-13 Thread Jay D. McHugh 

Thanks Abe.

Yeah, I figured that out (that I needed a transaction to get it to post).

But I then I was having problems creating a transaction within Geronimo.

I ended up having to change my persistence unit from being a 'JTA' 
transaction type to being a 'RESOURCE_LOCAL'.


Thanks,


Jay

Abe White wrote:
It sounds like you're never starting or committing a transaction.  
You're persisting outside of a transaction, which just means that the 
object will be cached until the next transaction, waiting for a 
flush/commit to be inserted into the database.

___
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

Re: Problem trying to persist an entity into Derby from a Web App deployed to Geronimo

2007-04-13 Thread Abe White 
It sounds like you're never starting or committing a transaction.   
You're persisting outside of a transaction, which just means that the  
object will be cached until the next transaction, waiting for a flush/ 
commit to be inserted into the database.

___
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

[jira] Commented: (OPENJPA-211) CLONE -java.lang.VerifyError on websphere 6.1 with Spring 2.0.3 and OpenJpa 0.96/0.97

2007-04-13 Thread david zhang (JIRA) 

[ 
https://issues.apache.org/jira/browse/OPENJPA-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488681
 ] 

david zhang commented on OPENJPA-211:
-

By the way, I'm using openjpa code enhancer during development time, not using 
Spring for the code enhance at deployment time. I think this may be the 
problem. But how configure Spring to enhance code, I haven't got succeed. Do 
you have some sample configuration for this?

> CLONE -java.lang.VerifyError on websphere 6.1 with Spring 2.0.3 and OpenJpa 
> 0.96/0.97
> -
>
> Key: OPENJPA-211
> URL: https://issues.apache.org/jira/browse/OPENJPA-211
> Project: OpenJPA
>  Issue Type: Bug
>  Components: kernel
>Affects Versions: 0.9.6
> Environment: Using OpenJPA (openjpa-all-0.9.6-incubating.jar) in 
> Rational Developer 7 ( Websphere 6.1 test environment ) connected to DB2 V9.1.
> OS: WinXP SP2
>Reporter: david zhang
>Priority: Blocker
> Fix For: 0.9.8
>
> Attachments: applicationContext.xml, applicationContext.xml, 
> mytestdata.jar, persistence.xml, persistence.xml
>
>
> Hi, if I use the OpenJPA shipped with Spring 2.0.3, I got the following error 
> when start application:
> org.springframework.beans.factory.BeanCreationException: Error creating bean 
> with name 'entityManagerFactory' defined in ServletContext resource 
> [/WEB-INF/applicationContext.xml]: Invocation of init method failed; nested 
> exception is java.lang.VerifyError: class loading constraint violated (class: 
> org/apache/openjpa/kernel/BrokerImpl method: 
> newQueryImpl(Ljava/lang/String;Lorg/apache/openjpa/kernel/StoreQuery;)Lorg/apache/openjpa/kernel/QueryImpl;)
>  at pc: 0
> Caused by: 
> java.lang.VerifyError: class loading constraint violated (class: 
> org/apache/openjpa/kernel/BrokerImpl method: 
> newQueryImpl(Ljava/lang/String;Lorg/apache/openjpa/kernel/StoreQuery;)Lorg/apache/openjpa/kernel/QueryImpl;)
>  at pc: 0
>   at java.lang.J9VMInternals.verifyImpl(Native Method)
>   at java.lang.J9VMInternals.verify(J9VMInternals.java:59)
>   at java.lang.J9VMInternals.initialize(J9VMInternals.java:120)
>   at java.lang.Class.forNameImpl(Native Method)
>   at java.lang.Class.forName(Class.java:131)
>   at 
> org.apache.openjpa.conf.OpenJPAConfigurationImpl.class$(OpenJPAConfigurationImpl.java:65)
>   at 
> org.apache.openjpa.conf.OpenJPAConfigurationImpl.(OpenJPAConfigurationImpl.java:182)
>   at 
> org.apache.openjpa.conf.OpenJPAConfigurationImpl.(OpenJPAConfigurationImpl.java:154)
>   at 
> org.apache.openjpa.conf.OpenJPAConfigurationImpl.(OpenJPAConfigurationImpl.java:145)
>   at 
> org.apache.openjpa.persistence.PersistenceProviderImpl$ClassTransformerImpl.(PersistenceProviderImpl.java:114)
>   at 
> org.apache.openjpa.persistence.PersistenceProviderImpl$ClassTransformerImpl.(PersistenceProviderImpl.java:106)
>   at 
> org.apache.openjpa.persistence.PersistenceProviderImpl.createContainerEntityManagerFactory(PersistenceProviderImpl.java:92)
>   at 
> org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:214)
>   at 
> org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:251)
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1143)
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1110)
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:431)
>   at 
> org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:254)
>   at 
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:144)
>   at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:251)
>   at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:163)
>   at 
> org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeansOfType(DefaultListableBeanFactory.java:244)
>   at 
> org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeansOfType(DefaultListableBeanFactory.java:233)
>   at 
> org.springframework.beans.factory.BeanFactoryUtils.beansOfTypeIncludingAncestors(BeanFactoryUtils.java:205)
>   at 
> org.springframework.beans.factory.BeanFactoryUtils.beanOfTypeIncludingAncestors(BeanFactoryUtils.java:292)
>   at

Re: [jira] Commented: (OPENJPA-134) Extra unneeded SQL joins for OneToMany relationship with fetch type EAGER

2007-04-13 Thread Abe White 
I did notice that my lazy scenarios are almost 50% slower now, but  
looking at the sql dumps it appears that we were fetching eagerly  
even in those scenarios and this (or another JIRA?) seems to have  
fixed that functional error.  Does that seem like something your  
changes would resolve?  Did you run into anything that would cause  
an eager fetch even when lazy was specified?


I had no intention of "fixing" any lazy loading behavior.  The fact  
that you're seeing different behavior makes me nervous.  Can you post  
details on the entities and the test case so we can determine for  
sure whether the new or old behavior is correct?


___
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

[jira] Created: (OPENJPA-216) ArgumentException when no identification variable given in UPDATE clause

2007-04-13 Thread Jacek Laskowski (JIRA) 
ArgumentException when no identification variable given in UPDATE clause


 Key: OPENJPA-216
 URL: https://issues.apache.org/jira/browse/OPENJPA-216
 Project: OpenJPA
  Issue Type: Bug
  Components: query
Affects Versions: 0.9.8
Reporter: Jacek Laskowski


According to the spec - 4.10 Bulk Update and Delete Operations page 104:

update_statement ::= update_clause [where_clause]
update_clause ::= UPDATE abstract_schema_name [[AS] identification_variable] 
SET update_item {, update_item}*
update_item ::= [identification_variable.]{state_field | 
single_valued_association_field} = new_value

The identification_variable is optional, but it doesn't seem to be true for 
OpenJPA 0.9.8-SNAPSHOT rev 528437.

$ svn up
Updated to revision 528437.

$ mvn -Dtest=false clean install
...
[INFO] 
[INFO] 
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 2 minutes 12 seconds
[INFO] Finished at: Fri Apr 13 13:00:04 CEST 2007
[INFO] Final Memory: 35M/254M
[INFO] 

$ mvn -Dtest=OpenJPATest clean test
...
0  derbyPU  INFO   [main] openjpa.Runtime - Starting OpenJPA 
0.9.8-incubating-SNAPSHOT
...
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] There are test failures.
[INFO] 
[INFO] For more information, run Maven with the -e switch
[INFO] 
[INFO] Total time: 33 seconds
[INFO] Finished at: Fri Apr 13 13:02:11 CEST 2007
[INFO] Final Memory: 11M/254M
[INFO] 

$ cat target/surefire-reports/pl.jaceklaskowski.jpa.issue.OpenJPATest.txt
---
Test set: pl.jaceklaskowski.jpa.issue.OpenJPATest
---
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.437 sec <<< 
FAILURE!
testUpdate(pl.jaceklaskowski.jpa.issue.OpenJPATest)  Time elapsed: 0.063 sec  
<<< FAILURE!
<0.9.8-incubating-SNAPSHOT nonfatal user error> 
org.apache.openjpa.persistence.ArgumentException: An error occurred while 
parsing the query filter 'UPDATE Osoba SET imie = 'JACEK'
WHERE imie = 'Jacek''. Error message: <0.9.8-incubating-SNAPSHOT nonfatal user 
error> org.apache.openjpa.kernel.jpql.ParseException: Encountered "=" at 
character 23, but expected:
["."].
at 
org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder$ParsedJPQL.parse(JPQLExpressionBuilder.java:1656)
at 
org.apache.openjpa.kernel.jpql.JPQLExpressionBuilder$ParsedJPQL.(JPQLExpressionBuilder.java:1636)
at org.apache.openjpa.kernel.jpql.JPQLParser.parse(JPQLParser.java:44)
at 
org.apache.openjpa.kernel.ExpressionStoreQuery.newCompilation(ExpressionStoreQuery.java:141)
at 
org.apache.openjpa.kernel.QueryImpl.newCompilation(QueryImpl.java:645)
at 
org.apache.openjpa.kernel.QueryImpl.compilationFromCache(QueryImpl.java:613)
at 
org.apache.openjpa.kernel.QueryImpl.compileForCompilation(QueryImpl.java:593)
at 
org.apache.openjpa.kernel.QueryImpl.compileForExecutor(QueryImpl.java:655)
at org.apache.openjpa.kernel.QueryImpl.getOperation(QueryImpl.java:1480)
at 
org.apache.openjpa.kernel.DelegatingQuery.getOperation(DelegatingQuery.java:120)
at 
org.apache.openjpa.persistence.QueryImpl.executeUpdate(QueryImpl.java:297)
at 
pl.jaceklaskowski.jpa.issue.OpenJPATest.testUpdate(OpenJPATest.java:23)

$ cat src/test/java/pl/jaceklaskowski/jpa/issue/OpenJPATest.java
package pl.jaceklaskowski.jpa.issue;

import javax.persistence.Query;

import org.testng.annotations.Test;

import pl.jaceklaskowski.jpa.BaseTest;

public class OpenJPATest extends BaseTest {

@Test(dependsOnMethods = { "utworzPracownikow" })
public void testUpdate() {
Query query;

em.getTransaction().begin();
try {
String identificationVariableUpdateQL = "UPDATE Osoba o SET o.imie 
= 'JACEK' WHERE o.imie = 'Jacek'";
query = em.createQuery(identificationVariableUpdateQL);
assert query.executeUpdate() == 1;

String noIdentificationVariableUpdateQL = "UPDATE Osoba SET imie = 
'JACEK' WHERE imie = 'Jacek'";
query = em.createQuery(noIdentificationVariableUpdateQL);
assert query.executeUpdate() == 1;
} finally {
e