A bit disappointing that Eclipse can't match on a simple filename pattern. We stopped using cayenne.xml in 3.1 as it wasn't flexible enough - it didn't allow multiple projects to exist under the same base url. So yeah for now it seems like we can't create an automated file association.
However... nothing prevents us from changing the naming convention again. After all 3.1 is not final yet (not even Beta). We might as well adopt another "double extension": Main project file: xyz.cayenne.xml DataMap file: xyz.map.xml This will ensure both types of files follow a similar convention, and make them Eclipse-friendly. Andrus On Jun 26, 2011, at 11:14 AM, Eshan Sudharaka wrote: > Sorry. I have made a mistake about naming conversion. But still there can be > various names for Main project file which starts from cayenne. So it is > hard to figure out which files should be open with Cayenne modeler. > According to > this<http://help.eclipse.org/indigo/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fextension-points%2Forg_eclipse_ui_editors.html>we > can filter files from extension attribute and file name attribute. So > I > it seems difficult to set cayenne modeler as the default editor for cayenne > main project xml file. ( eg : If we have a file name cayenne.xml we can > configure that name in eclipse plugin so that when double click on that file > it opens with the external editor instead open with eclipse xml editor. > Also we can load icon for that xml file as well ) . > > Once we have not such a specific name we have to open it by File > Open With > and select our editor. > > > On Sun, Jun 26, 2011 at 12:47 PM, Andrus Adamchik > <[email protected]>wrote: > >> Not sure I am answering the question being asked, but in 3.1, the file >> naming convention is the following: >> >> Main project file: cayenne-*.xml >> DataMap file: *.map.xml >> >> Which is pretty deterministic, even if a bit unusual. >> >> Andrus >> >> >> On Jun 26, 2011, at 9:05 AM, Eshan Sudharaka wrote: >>> Hi Ksenia , >>> As you mentioned I went through the code where i deletes >> cyenne.xml in UpgradeHandler_V6 class. And then in a case of we are having >> xyzDomainMap.xml (with out cayenne.xml) we can not open i with my external >> editor (cayenne modeler) by default. Because we can filter files according >> to extension or from a specific name. (can not go for pattern matching and >> filer xyzDomainMap.xml using the keyword DomainMap). So we have to open >> the DomainMap xml file by Open With > Cayenne Modeler Plugin (when we >> double click on DomainMap file is opens with default xml editor ) . I am >> still figuring out a way of solving this. >>> >>> I have attached a patch by adding java class generation support >> for my plugin in jira issue page. >> https://issues.apache.org/jira/browse/CAY-1554 >>> >>> -- >>> ~Thanks & Regards~ >>> >>> P.A.Eshan Sudharaka >>> Dept of Computer Science and Engineering >>> University of Moratuwa >>> Sri Lanka >>> http://esudharaka.blogspot.com/ >>> >>> <plugin-gsoc.patch> >> >> > > > -- > *~Thanks & Regards~* > *** > * > P.A.Eshan Sudharaka > Dept of Computer Science and Engineering > University of Moratuwa > Sri Lanka > http://esudharaka.blogspot.com/
