From: Dmitriy S. <sha...@gm...> - 2010-08-22 17:50:36
Attachments:
smime.p7s
|
Hi All, I did made second stage commits: - new account 'SYSTEM' - id = 0, all documents & collections under /db/system (& system itself) owned by this account & DBA group - split User to Account & Subject, only one account instance per account. Subject have reference to it & also will response for authentication - finish security storage changes (one question left: delete principal procedure. I don't want to delete information, all metadata must be checked for references firstly) - hot configuration engine The API was changed: - add getRealmId methods to Principal - for Account manipulation to have 'Account' (change getUser to getAccount) - for Group manipulation to have 'Group' (change group manipulation methods to have 'group' in name instead of 'role') - 'add', 'update', 'delete' principal manipulations methods to have 'add', 'update', 'delete' TODO: 1. fix backup restore, automatic /db/system/users.xml migration question 2. principal delete procedure 3. make sure that old clients will work with new API, as example oXygen with old libs 4. stabilization This week I plan to finish refactoring & next LDAP & AD realms (hope, till September) On Wed, 2010-08-11 at 23:05 +0500, Dmitriy Shabanov wrote: > Hello, > > I did made first commit > ttp://exist.svn.sourceforge.net/exist/?rev=12393&view=rev > > WARNING: this commit disable SecurityManager reloading > on /db/system/users.xml document changes (switching to new mechanism) > -- Cheers, Dmitriy Shabanov |
From: Pierrick B. <pie...@fr...> - 2010-08-22 17:59:20
|
Hi, Le 22/08/2010 19:51, Dmitriy Shabanov a écrit : > I did made second stage commits: When can we expect a working test suite ? Cheers, p.b. |
From: Dmitriy S. <sha...@gm...> - 2010-08-22 18:18:27
Attachments:
smime.p7s
|
On Sun, 2010-08-22 at 19:59 +0200, Pierrick Brihaye wrote: > Hi, > > Le 22/08/2010 19:51, Dmitriy Shabanov a écrit : > > > I did made second stage commits: > > When can we expect a working test suite ? In two or (max)three days, the trunk is stable, only two things make troubles: restore from backup require migration & less critical principal removal procedure (test suite failing because of it) (I plan to do it tomorrow) -- Cheers, Dmitriy Shabanov |
From: Andrzej J. T. <an...@ch...> - 2010-08-22 18:44:53
|
Dmitriy: > I did made second stage commits: Excellent...glad to see you are making progress! > TODO: > 1. fix backup restore, automatic /db/system/users.xml migration question > 2. principal delete procedure > 3. make sure that old clients will work with new API, as example oXygen > with old libs > 4. stabilization I'm really keen on 1 & 4. Any ETA on when you think that might be ready for testing with existing databases? Thanks! -- Andrzej Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com |
From: Dmitriy S. <sha...@gm...> - 2010-08-23 08:20:17
Attachments:
smime.p7s
|
On Sun, 2010-08-22 at 14:16 -0400, Andrzej Jan Taramina wrote: > Dmitriy: > > > I did made second stage commits: > > Excellent...glad to see you are making progress! > > > TODO: > > 1. fix backup restore, automatic /db/system/users.xml migration question > > 2. principal delete procedure > > 3. make sure that old clients will work with new API, as example oXygen > > with old libs > > 4. stabilization > > I'm really keen on 1 & 4. Any ETA on when you think that might be ready for testing with existing databases? I really want to finish in 2-3 days, let's be optimistic from 3 to 6 days. #1 should be done today. -- Cheers, Dmitriy Shabanov |
From: Andrzej J. T. <an...@ch...> - 2010-08-24 07:25:38
|
On 08/23/2010 04:20 AM, Dmitriy Shabanov wrote: > I really want to finish in 2-3 days, let's be optimistic from 3 to 6 > days. #1 should be done today. Sounds great, Dmitriy! I'll look forward to testing it in about a week or less. -- Andrzej Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com |
From: Andrzej J. T. <an...@ch...> - 2010-08-25 21:05:54
|
On 08/22/2010 01:51 PM, Dmitriy Shabanov wrote: > TODO: > 1. fix backup restore, automatic /db/system/users.xml migration question > 2. principal delete procedure > 3. make sure that old clients will work with new API, as example oXygen > with old libs > 4. stabilization > > This week I plan to finish refactoring & next LDAP & AD realms (hope, > till September) Does the refactoring include items 1, 4 and maybe 3 on your Todo list? I'm really anxious for 1 and 4 to be completed, before you tackle other realms like LDAP and AD.... -- Andrzej Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com |
From: Dmitriy S. <sha...@gm...> - 2010-08-26 04:30:32
Attachments:
smime.p7s
|
On Wed, 2010-08-25 at 17:05 -0400, Andrzej Jan Taramina wrote: > On 08/22/2010 01:51 PM, Dmitriy Shabanov wrote: > > > TODO: > > 1. fix backup restore, automatic /db/system/users.xml migration question > > 2. principal delete procedure > > 3. make sure that old clients will work with new API, as example oXygen > > with old libs > > 4. stabilization > > > > This week I plan to finish refactoring & next LDAP & AD realms (hope, > > till September) > > Does the refactoring include items 1, 4 and maybe 3 on your Todo list? > > I'm really anxious for 1 and 4 to be completed, before you tackle other realms like LDAP and AD.... I did finish coding #1, only the problem is collection's configuration get method, it have restriction on '/db/system'. Analyzing how to change it. #4 is the question of more tests. -- Cheers, Dmitriy Shabanov |
From: Dmitriy S. <sha...@gm...> - 2010-08-29 18:43:31
Attachments:
smime.p7s
|
On Mon, 2010-08-23 at 13:21 +0500, Dmitriy Shabanov wrote: > On Sun, 2010-08-22 at 14:16 -0400, Andrzej Jan Taramina wrote: > > Dmitriy: > > > > > I did made second stage commits: > > > > Excellent...glad to see you are making progress! > > > > > TODO: > > > 1. fix backup restore, automatic /db/system/users.xml migration question > > > 2. principal delete procedure > > > 3. make sure that old clients will work with new API, as example oXygen > > > with old libs > > > 4. stabilization > > > > I'm really keen on 1 & 4. Any ETA on when you think that might be ready for testing with existing databases? > > I really want to finish in 2-3 days, let's be optimistic from 3 to 6 > days. #1 should be done today. > The items 1 & 2 should be done. Let me know if any problem. -- Cheers, Dmitriy Shabanov |
From: Andrzej J. T. <an...@ch...> - 2010-09-01 19:06:10
|
Dmitriy: >>>> TODO: >>>> 1. fix backup restore, automatic /db/system/users.xml migration question >>>> 2. principal delete procedure >>>> 3. make sure that old clients will work with new API, as example oXygen >>>> with old libs >>>> 4. stabilization >>> >>> I'm really keen on 1 & 4. Any ETA on when you think that might be ready for testing with existing databases? > The items 1 & 2 should be done. Let me know if any problem. Automatic /db/system/users.xml migration does not work. I tried our app with an existing database on the latest SVN build, and it doesn't pick up some of the users we already have defined in the /db/system/users.xml file. Is this not working yet? Thanks! -- Andrzej Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com |
From: Dmitriy S. <sha...@gm...> - 2010-09-02 06:20:09
Attachments:
smime.p7s
|
On Wed, 2010-09-01 at 15:05 -0400, Andrzej Jan Taramina wrote: > > Automatic /db/system/users.xml migration does not work. I tried our > app with an existing database on the latest SVN > build, and it doesn't pick up some of the users we already have > defined in the /db/system/users.xml file. How do you do db migration? restore from backup? or just run on existing data? > Is this not working yet? What rev do you use? -- Cheers, Dmitriy Shabanov |
From: Evgeny G. <gaz...@gm...> - 2010-09-02 12:27:51
|
During restoring data from users.xml diggest password is not coping into account. Where just stored the link between account and groups? -- Evgeny |
From: Andrzej J. T. <an...@ch...> - 2010-09-03 01:03:32
|
> How do you do db migration? restore from backup? or just run on existing > data? I just fire up using an existing database...I was under the impression the migration would be automatic. Having to restore from a backup is not realistic for remote production sites! > What rev do you use? I used the latest SVN Trunk a day ago. -- Andrzej Taramina Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com |
From: Dmitriy S. <sha...@gm...> - 2010-09-03 05:42:43
Attachments:
smime.p7s
|
On Thu, 2010-09-02 at 21:03 -0400, Andrzej Jan Taramina wrote: > > > How do you do db migration? restore from backup? or just run on > existing > > data? > > I just fire up using an existing database...I was under the impression > the migration would be automatic. > > Having to restore from a backup is not realistic for remote production > sites! You can open&save users.xml, that will trigger the convertor. Same time, I don't think that trunk ready for production site, some more tests require first. -- Cheers, Dmitriy Shabanov |
From: Joe W. <jo...@gm...> - 2010-09-08 13:09:34
|
Hi all, My experience with trunk recently is that oXygen's Database Explorer can browse the database, but generates an error whenever I try to open a document: [ Resource Opener ] - java.lang.NoSuchMethodError: org.exist.xmldb.UserManagementService.getUser(Ljava/lang/String;)Lorg/exist/security/User; java.lang.NoSuchMethodError: org.exist.xmldb.UserManagementService.getUser(Ljava/lang/String;)Lorg/exist/security/User; at ro.sync.db.nxd.exist.A.B(Unknown Source) at ro.sync.exml.editor.T.V$25.A(Unknown Source) at ro.sync.db.nxd.B.A(Unknown Source) at ro.sync.db.nxd.B$_E$1.Ե(Unknown Source) at ro.sync.ui.application.P.run(Unknown Source) I do not get this error when opening documents via File > Open URL. I recall Dmitriy saying: > TODO: ... > 3. make sure that old clients will work with new API, as example oXygen with old libs Is anyone else seeing this error? If so, I guess the workaround for now is to avoid using trunk libraries for oXygen Data Source definitions. Joe |
From: Adam R. <ad...@ex...> - 2010-09-08 13:44:26
|
Hey Joe, How recent is your trunk experience? It seems to work okay here for me... On 8 September 2010 14:09, Joe Wicentowski <jo...@gm...> wrote: > Hi all, > > My experience with trunk recently is that oXygen's Database Explorer > can browse the database, but generates an error whenever I try to open > a document: > > [ Resource Opener ] - java.lang.NoSuchMethodError: > org.exist.xmldb.UserManagementService.getUser(Ljava/lang/String;)Lorg/exist/security/User; > java.lang.NoSuchMethodError: > org.exist.xmldb.UserManagementService.getUser(Ljava/lang/String;)Lorg/exist/security/User; > at ro.sync.db.nxd.exist.A.B(Unknown Source) > at ro.sync.exml.editor.T.V$25.A(Unknown Source) > at ro.sync.db.nxd.B.A(Unknown Source) > at ro.sync.db.nxd.B$_E$1.Ե(Unknown Source) > at ro.sync.ui.application.P.run(Unknown Source) > > I do not get this error when opening documents via File > Open URL. > > I recall Dmitriy saying: > >> TODO: > ... >> 3. make sure that old clients will work with new API, as example oXygen with old libs > > Is anyone else seeing this error? If so, I guess the workaround for > now is to avoid using trunk libraries for oXygen Data Source > definitions. > > Joe > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |
From: Dmitriy S. <sha...@gm...> - 2010-09-08 14:43:01
Attachments:
smime.p7s
|
Hi Joe, What revision do you use? I did try beta oXygen 12.0 & make it work with trunk rev 12624 ( http://exist.svn.sourceforge.net/exist/?rev=12624&view=rev ) -- Cheers, Dmitriy Shabanov On Wed, 2010-09-08 at 09:09 -0400, Joe Wicentowski wrote: > Hi all, > > My experience with trunk recently is that oXygen's Database Explorer > can browse the database, but generates an error whenever I try to open > a document: > > [ Resource Opener ] - java.lang.NoSuchMethodError: > org.exist.xmldb.UserManagementService.getUser(Ljava/lang/String;)Lorg/exist/security/User; > java.lang.NoSuchMethodError: > org.exist.xmldb.UserManagementService.getUser(Ljava/lang/String;)Lorg/exist/security/User; > at ro.sync.db.nxd.exist.A.B(Unknown Source) > at ro.sync.exml.editor.T.V$25.A(Unknown Source) > at ro.sync.db.nxd.B.A(Unknown Source) > at ro.sync.db.nxd.B$_E$1.Ե(Unknown Source) > at ro.sync.ui.application.P.run(Unknown Source) > > I do not get this error when opening documents via File > Open URL. > > I recall Dmitriy saying: > > > TODO: > ... > > 3. make sure that old clients will work with new API, as example oXygen with old libs > > Is anyone else seeing this error? If so, I guess the workaround for > now is to avoid using trunk libraries for oXygen Data Source > definitions. > > Joe |
From: Jens Ø. P. <oe...@gm...> - 2010-09-08 16:25:18
|
Hi Joe, I have been seeing this error for several weeks now (and so has my colleague). Checked out a totally fresh trunk today, and it was still the same. Are you suggesting that one should use the files from an early 1.5 (or 1.4) eXist in the Data Source definitions? Are there no problems with this? If there is a work-around, this should be posted to the open list. As Dmitriy says, there is no problems when using the oXygen 12 beta. Tested on Mac OS X only with 12654. Jens On Sep 8, 2010, at 3:09 PM, Joe Wicentowski wrote: > Hi all, > > My experience with trunk recently is that oXygen's Database Explorer > can browse the database, but generates an error whenever I try to open > a document: > > [ Resource Opener ] - java.lang.NoSuchMethodError: > org.exist.xmldb.UserManagementService.getUser(Ljava/lang/String;)Lorg/exist/security/User; > java.lang.NoSuchMethodError: > org.exist.xmldb.UserManagementService.getUser(Ljava/lang/String;)Lorg/exist/security/User; > at ro.sync.db.nxd.exist.A.B(Unknown Source) > at ro.sync.exml.editor.T.V$25.A(Unknown Source) > at ro.sync.db.nxd.B.A(Unknown Source) > at ro.sync.db.nxd.B$_E$1.Ե(Unknown Source) > at ro.sync.ui.application.P.run(Unknown Source) > > I do not get this error when opening documents via File > Open URL. > > I recall Dmitriy saying: > >> TODO: > ... >> 3. make sure that old clients will work with new API, as example oXygen with old libs > > Is anyone else seeing this error? If so, I guess the workaround for > now is to avoid using trunk libraries for oXygen Data Source > definitions. > > Joe > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development |
From: Dmitriy S. <sha...@gm...> - 2010-09-08 16:42:59
Attachments:
smime.p7s
|
On Wed, 2010-09-08 at 18:24 +0200, Jens Østergaard Petersen wrote: > Hi Joe, > > I have been seeing this error for several weeks now (and so has my > colleague). Checked out a totally fresh trunk today, and it was still > the same. Did you replace libs with new one at oXygen side? -- Cheers, Dmitriy Shabanov |
From: Chris T. <chr...@gm...> - 2010-09-08 16:47:19
|
I see the same error: > [ Resource Opener ] - java.lang.NoSuchMethodError: org.exist.xmldb.UserManagementService.lockResource(Lorg/xmldb/api/base/Resource;Lorg/exist/security/User;)V > java.lang.NoSuchMethodError: org.exist.xmldb.UserManagementService.lockResource(Lorg/xmldb/api/base/Resource;Lorg/exist/security/User;)V > at ro.sync.db.nxd.exist.b.gd(Unknown Source) > at ro.sync.exml.editor.u.w$25.c(Unknown Source) > at ro.sync.db.nxd.c.be(Unknown Source) > at ro.sync.db.nxd.c$_f$1.rhg(Unknown Source) > at ro.sync.ui.application.r.run(Unknown Source) with: <oXygen/> XML Editor 11.2, build 2010080212 and the correct set of libs in oXygen from a build of trunk rev 12655. Regards, Chris On Sep 8, 2010, at 10:28 PM, Dmitriy Shabanov wrote: > On Wed, 2010-09-08 at 18:24 +0200, Jens Østergaard Petersen wrote: >> Hi Joe, >> >> I have been seeing this error for several weeks now (and so has my >> colleague). Checked out a totally fresh trunk today, and it was still >> the same. > > Did you replace libs with new one at oXygen side? > > -- > Cheers, > > Dmitriy Shabanov > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd_______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development |
From: Adam R. <ad...@ex...> - 2010-09-08 17:12:04
|
2010/9/8 Jens Østergaard Petersen <oe...@gm...>: > Hi Joe, > > I have been seeing this error for several weeks now (and so has my colleague). Checked out a totally fresh trunk today, and it was still the same. > > Are you suggesting that one should use the files from an early 1.5 (or 1.4) eXist in the Data Source definitions? Are there no problems with this? If there is a work-around, this should be posted to the open list. > > As Dmitriy says, there is no problems when using the oXygen 12 beta. I dont see the issue with current trunk on Mac OSX with oXygen 11.2 beta. > > Tested on Mac OS X only with 12654. > > Jens > > > On Sep 8, 2010, at 3:09 PM, Joe Wicentowski wrote: > >> Hi all, >> >> My experience with trunk recently is that oXygen's Database Explorer >> can browse the database, but generates an error whenever I try to open >> a document: >> >> [ Resource Opener ] - java.lang.NoSuchMethodError: >> org.exist.xmldb.UserManagementService.getUser(Ljava/lang/String;)Lorg/exist/security/User; >> java.lang.NoSuchMethodError: >> org.exist.xmldb.UserManagementService.getUser(Ljava/lang/String;)Lorg/exist/security/User; >> at ro.sync.db.nxd.exist.A.B(Unknown Source) >> at ro.sync.exml.editor.T.V$25.A(Unknown Source) >> at ro.sync.db.nxd.B.A(Unknown Source) >> at ro.sync.db.nxd.B$_E$1.Ե(Unknown Source) >> at ro.sync.ui.application.P.run(Unknown Source) >> >> I do not get this error when opening documents via File > Open URL. >> >> I recall Dmitriy saying: >> >>> TODO: >> ... >>> 3. make sure that old clients will work with new API, as example oXygen with old libs >> >> Is anyone else seeing this error? If so, I guess the workaround for >> now is to avoid using trunk libraries for oXygen Data Source >> definitions. >> >> Joe >> >> ------------------------------------------------------------------------------ >> This SF.net Dev2Dev email is sponsored by: >> >> Show off your parallel programming skills. >> Enter the Intel(R) Threading Challenge 2010. >> http://p.sf.net/sfu/intel-thread-sfd >> _______________________________________________ >> Exist-development mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-development > > > ------------------------------------------------------------------------------ > This SF.net Dev2Dev email is sponsored by: > > Show off your parallel programming skills. > Enter the Intel(R) Threading Challenge 2010. > http://p.sf.net/sfu/intel-thread-sfd > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |
From: George C. B. <ge...@ox...> - 2010-09-09 07:03:08
|
This issue was handled on our side in the oXygen 12 beta, using Java reflection to test if the getUser method is available or not. Version 11.2 of course tries to use the getUser method and will not work with the new code. However, it would have been better is the UserManagementService.getUser was deprecated instead of being removed. Best Regards, George -- George Cristian Bina <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger http://www.oxygenxml.com On 9/8/10 8:11 PM, Adam Retter wrote: > 2010/9/8 Jens Østergaard Petersen<oe...@gm...>: >> Hi Joe, >> >> I have been seeing this error for several weeks now (and so has my colleague). Checked out a totally fresh trunk today, and it was still the same. >> >> Are you suggesting that one should use the files from an early 1.5 (or 1.4) eXist in the Data Source definitions? Are there no problems with this? If there is a work-around, this should be posted to the open list. >> >> As Dmitriy says, there is no problems when using the oXygen 12 beta. > > I dont see the issue with current trunk on Mac OSX with oXygen 11.2 beta. > >> >> Tested on Mac OS X only with 12654. >> >> Jens >> >> >> On Sep 8, 2010, at 3:09 PM, Joe Wicentowski wrote: >> >>> Hi all, >>> >>> My experience with trunk recently is that oXygen's Database Explorer >>> can browse the database, but generates an error whenever I try to open >>> a document: >>> >>> [ Resource Opener ] - java.lang.NoSuchMethodError: >>> org.exist.xmldb.UserManagementService.getUser(Ljava/lang/String;)Lorg/exist/security/User; >>> java.lang.NoSuchMethodError: >>> org.exist.xmldb.UserManagementService.getUser(Ljava/lang/String;)Lorg/exist/security/User; >>> at ro.sync.db.nxd.exist.A.B(Unknown Source) >>> at ro.sync.exml.editor.T.V$25.A(Unknown Source) >>> at ro.sync.db.nxd.B.A(Unknown Source) >>> at ro.sync.db.nxd.B$_E$1.Ե(Unknown Source) >>> at ro.sync.ui.application.P.run(Unknown Source) >>> >>> I do not get this error when opening documents via File> Open URL. >>> >>> I recall Dmitriy saying: >>> >>>> TODO: >>> ... >>>> 3. make sure that old clients will work with new API, as example oXygen with old libs >>> >>> Is anyone else seeing this error? If so, I guess the workaround for >>> now is to avoid using trunk libraries for oXygen Data Source >>> definitions. >>> >>> Joe >>> >>> ------------------------------------------------------------------------------ >>> This SF.net Dev2Dev email is sponsored by: >>> >>> Show off your parallel programming skills. >>> Enter the Intel(R) Threading Challenge 2010. >>> http://p.sf.net/sfu/intel-thread-sfd >>> _______________________________________________ >>> Exist-development mailing list >>> Exi...@li... >>> https://lists.sourceforge.net/lists/listinfo/exist-development >> >> >> ------------------------------------------------------------------------------ >> This SF.net Dev2Dev email is sponsored by: >> >> Show off your parallel programming skills. >> Enter the Intel(R) Threading Challenge 2010. >> http://p.sf.net/sfu/intel-thread-sfd >> _______________________________________________ >> Exist-development mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-development >> > > > |
From: Dmitriy S. <sha...@gm...> - 2010-09-09 07:41:01
Attachments:
smime.p7s
|
On Thu, 2010-09-09 at 10:03 +0300, George Cristian Bina wrote: > This issue was handled on our side in the oXygen 12 beta, using Java > reflection to test if the getUser method is available or not. Version > 11.2 of course tries to use the getUser method and will not work with > the new code. > > However, it would have been better is the > UserManagementService.getUser > was deprecated instead of being removed. I did put them as deprecated: http://exist.svn.sourceforge.net/exist/?rev=12624&view=rev Also, fix lockResource(Resource, User) issue by http://exist.svn.sourceforge.net/exist/?rev=12665&view=rev -- Cheers, Dmitriy Shabanov |
From: Wolfgang M. <wol...@ex...> - 2010-09-09 07:09:36
|
> However, it would have been better is the UserManagementService.getUser > was deprecated instead of being removed. I agree. Not all users can easily update Oxygen to the newest version. Some of my users just get a pre-installed Oxygen. Dmitryi, would it be possible to keep the old method and map it to the new one transparently? Wolfgang |
From: Dmitriy S. <sha...@gm...> - 2010-09-09 07:44:06
Attachments:
smime.p7s
|
On Thu, 2010-09-09 at 09:09 +0200, Wolfgang Meier wrote: > I agree. Not all users can easily update Oxygen to the newest version. > Some of my users just get a pre-installed Oxygen. > > Dmitryi, would it be possible to keep the old method and map it to the > new one transparently? It was done few weeks ago. -- Cheers, Dmitriy Shabanov |