headers
Borut Bolčina | 1 Oct 2006 10:00
Picon
Gravatar

Re: Success stories

Hello,

Serbia is up und running. Maybe instead of
"There are plans to switch to Cayenne similar sites for Slovenia, Serbia and
Macedonia."
there should be
"There are plans to add blog search Cayenne enabled services for Slovenia
and Macedonia also."

-Borut

2006/9/30, Andrus Adamchik <andrus <at> objectstyle.org>:
>
> Just got around to posting Borut's and Ari's success stories. They
> should be on the website within ~20 minutes. Here is a link to the
> news item:
>
> http://cwiki.apache.org/confluence/display/CAY/2006/09/30/
>
> Andrus
>
Permalink | Reply | 1 comment |
headers
Juergen Saar | 1 Oct 2006 12:43

Re: Error: same entity-name in 2 DataMaps

You are right ... 2 DataMaps ... had a hard week ...

2006/9/30, Andrus Adamchik <andrus <at> objectstyle.org>:
>
>
> On Sep 30, 2006, at 8:03 AM, Juergen Saar wrote:
>
> > the Entities live in different DataDomains ... but the relation in the
> > second DataDomain uses the entity-definition from the first DataDomain
>
> 2 DataDomains or 2 DataMap? Relationships between entities in
> different domains are not possible by design.
>
> Andrus
>
>
Permalink | Reply | 0 comments |
headers
Andrus Adamchik | 1 Oct 2006 18:15
Favicon

Re: Success stories

Thanks for correction - I will make this change.

Andrus

On Oct 1, 2006, at 4:00 AM, Borut Bolčina wrote:

> Hello,
>
> Serbia is up und running. Maybe instead of
> "There are plans to switch to Cayenne similar sites for Slovenia,  
> Serbia and
> Macedonia."
> there should be
> "There are plans to add blog search Cayenne enabled services for  
> Slovenia
> and Macedonia also."
>
> -Borut
>
>
> 2006/9/30, Andrus Adamchik <andrus <at> objectstyle.org>:
>>
>> Just got around to posting Borut's and Ari's success stories. They
>> should be on the website within ~20 minutes. Here is a link to the
>> news item:
>>
>> http://cwiki.apache.org/confluence/display/CAY/2006/09/30/
>>
>> Andrus
>>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Borut Bolčina | 1 Oct 2006 23:57
Picon
Gravatar

Re: Cayenne web site design

Ari, I will be attending a conference tomorrow and the day after, so I won't
be able to participate in the process of reshaping the Cayenne site.

Let us focus on the content first. I will try to create a content tree map
for the site, which will suggest the navigation items.

I like clean HTML, after all this will help building a template if we choose
to do it via Confluence export feature.

-Borut

2006/9/30, Aristedes Maniatis <ari <at> ish.com.au>:
>
> We have tried to incorporate all the issues people have had with the
> initial design into this updated design:
>
> http://www.brucemartin.net/cayenne/
>
> It achieves a few things:
>
> * reduce the size of the left menu to not make it overwhelming
> * increase the size of the left menu to give more choices (especially
> as we add version 3.1, 4,0, etc)
> * continue to have a site which degrades gracefully for old browsers,
> lynx, etc. and also for accessibility
> * conform to w3c standards
> * make the introductory text snappier and more appealing
> * give the news more prominence
> * give the wordy Apache disclaimer less prominence (but still there)
> * continue to have absolutely simple and clear html suitable for any
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kevin Menard | 2 Oct 2006 02:43

Re: Cayenne web site design

Hi Ari,

Apologies for not replying earlier.  All in all, this is a much improved 
version.  I'm glad to see the varied feedback incorporated.  As usual 
though, I have some things to note:

o "How Can I Help" should have a question mark to be consistent with 
"Why Cayenne?"

o We should probably have the 1.1 documentation on the site.  This could 
be marked as a legacy release.  1.2 is still fairly young, however, so 
we should make it easy for those still using 1.1 to get appropriate support.

o In thinking about it more, it may make more sense to invert the 
version order for the documentation.  Right now, the development version 
is the first accessible one, although we should be promoting the stable 
release for general use.

o "Getting started" is the only label that doesn't use capitalization 
across all words.

o I'm thinking it may be worthwhile to have a whole section dedicated to 
support.  This would have links to FAQs, commercial support, mailing 
lists, and what not.

o "Contributors" seems like an informative topic and may be better 
placed under "About" rather than "Collaboration."

o I still have mixed feelings on the main content.  It's definitely 
improved, but for logical flow, it would seem to me that the modeler
(Continue reading)

Permalink | Reply | 10 comments |
headers
Andrus Adamchik | 2 Oct 2006 03:48
Favicon

Re: Cayenne web site design


On Oct 1, 2006, at 8:43 PM, Kevin Menard wrote:

>
> o We should probably have the 1.1 documentation on the site.  This  
> could be marked as a legacy release.  1.2 is still fairly young,  
> however, so we should make it easy for those still using 1.1 to get  
> appropriate support.

My idea of how this should be organized is to show at most 2-3  
releases that we think of as "current" to avoid the clutter. And then  
add "Other..." menu item in the bottom of documentation section that  
points to the docs collections for the old releases. "1.1" should  
probably go in the "Other" category.

> o In thinking about it more, it may make more sense to invert the  
> version order for the documentation.  Right now, the development  
> version is the first accessible one, although we should be  
> promoting the stable release for general use.

Current ordering was actually my idea :-) The point was mainly to  
show things in chronological order, newest first... Maybe we can  
break dev release out of it, and strip the "stable" label (it should  
be implied), but keep the rest in order:

* Version 2.0
* Version 1.2
* Development Release (Version 3.0)

Once 3.0 goes Beta, the menu will look like this, to encourage users
(Continue reading)

Permalink | Reply | 1 comment |
headers
Aristedes Maniatis | 2 Oct 2006 04:14
Picon
Favicon
Gravatar

Re: Cayenne web site design


On 02/10/2006, at 10:43 AM, Kevin Menard wrote:

> Hi Ari,
>
> Apologies for not replying earlier.  All in all, this is a much  
> improved version.  I'm glad to see the varied feedback  
> incorporated.  As usual though, I have some things to note:

Of course, feedback is very helpful.

>
> o "How Can I Help" should have a question mark to be consistent  
> with "Why Cayenne?"

Fixed.

>
> o We should probably have the 1.1 documentation on the site.  This  
> could be marked as a legacy release.  1.2 is still fairly young,  
> however, so we should make it easy for those still using 1.1 to get  
> appropriate support.

Hands up anyone using 1.1... thought so... :-)

If people want 1.1, it is trivial to add one more line.

> o In thinking about it more, it may make more sense to invert the  
> version order for the documentation.  Right now, the development  
> version is the first accessible one, although we should be
(Continue reading)

Permalink | Reply | 7 comments |
headers
Tobias SCHOESSLER | 2 Oct 2006 10:34

Re: Problems with MySql id type with AUTO_INCREMENT

Sorry,the problem with the sequoia jdbc driver returning Integer Type for
the PK as described below is solved. It was not an issue of cayenne at all.
There were some problem with the update of the schema. sequoia worked with
the old INT UNSIGNED schema tested earlier.

So MySQL 5, Sequoia, db side AUTO_INCREMENT PK using BIGINT and
java.lang.Long mapping seem to work too.

                                                                           
             Tobias.Schoessler                                             
              <at> unvienna.org                                                 
                                                                        To 
             Friday, 29                cayenne-user <at> incubator.apache.org,  
             September 2006            cayenne-user <at> incubator.apache.org   
             20:39                                                      cc 

                                                                   Subject 
             Please respond to         Re: Problems with MySql id type     
             cayenne-user <at> incu         with AUTO_INCREMENT                 
             bator.apache.org                                              

ah ok, thanks for clarifying this.

was this MySQL no Locking PkGenerator ever  implemented?

*

Hmm, I got so far with the AUTO_INCREMENT set up, I don't want to drop it
so quickly.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tore Halset | 2 Oct 2006 12:19
Picon
Picon
Favicon

[OT] sync large db over slow network

Hello.

We have a large database for a cayenne server application. The  
database engine is currently MS SQL Server, but we will perhaps  
switch over to PostgreSQL at some point in time.

For disaster recovery we want to have a mirrored system somewhere  
else in the world. It is ok if the mirrored system are updated every  
15. minute or so. The data volume are too large to be able to do a  
full dump/restore of the database that often. The content of the  
database do not change that much every 15. minute.

I have looked at sequoia. It injects at the jdbc-level and issue all  
delete/update/insert-statements in the backup database as well as the  
main database. I am afraid that the extra level om complexity will  
degrade the main service. Anyone here have experience with sequoia  
over network links that may be down from time to time..? I wanted to  
have one controller on each site, but have read on the mail list that  
controllers should have a reliable network between them.

I could do some things myself at the jdbc-level to send over changes  
to the database. Small tables could be mirrored completely and have  
some smart logic for larger tables. Perhaps use dataport and/or ROP.

Any ideas?

Regards,
  - Tore.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Kevin Menard | 2 Oct 2006 14:55

Re: Cayenne web site design

Andrus Adamchik wrote:
>
> My idea of how this should be organized is to show at most 2-3 
> releases that we think of as "current" to avoid the clutter. And then 
> add "Other..." menu item in the bottom of documentation section that 
> points to the docs collections for the old releases. "1.1" should 
> probably go in the "Other" category.

Fair enough, but 1.2 and 2.0 are essentially the same release.  I 
actually think having them both marked as stable is going to create a 
bit of a confusing situation as is.  If we're going to go this way, then 
I'd mark 2.0 as "current" and 1.2 as "legacy" (and avoid the whole 
stability issue).  3.0 would obviously be "development."

>> o In thinking about it more, it may make more sense to invert the 
>> version order for the documentation.  Right now, the development 
>> version is the first accessible one, although we should be promoting 
>> the stable release for general use.
>
> Current ordering was actually my idea :-) The point was mainly to show 
> things in chronological order, newest first... Maybe we can break dev 
> release out of it, and strip the "stable" label (it should be 
> implied), but keep the rest in order:
>
> * Version 2.0
> * Version 1.2
> * Development Release (Version 3.0)
>

+1
(Continue reading)

Permalink | Reply | 0 comments |

Gmane