Re: user management
Hi Torgei, Torgeir Veimo schrieb: > Even though user management will not be part of sling it would be good > to have a common implementation. So I'm wondering if anyone else is > working on something here, and / or if this would fit into a sort of > sling-commons project. I do not know of any open-source implementation under way for Sling. But I would assume, it would definitely be a good addition to Sling. > > With user management I'm thinking about; > > glue between login form page and jcr authenticatio I assume you are talking about an AuthenticationHandler ? > user node type definitions with most common properties for basic users; > uid, password, > basic group node types > basic manager for managing users and groups; add/remove/update, change > group membership. This sounds like two stories: One story is probably a LoginHandler and an AccessManager for Jackrabbit and the other story is adding "user profile" information. Before setting out to implement anything new, you might want take a look at what has been done around JCR-1171 with respect to (start to) implement what will utimately become support JSR-283 (JCR2.0) access control specificaiton. This has actually been released as part of the Jackrabbit 1.5 release. I have to admit, that I do not know much about this stuff (yet -- well, another area to catch up on ;-) ), but it might be worth looking at that. The other part of the story is the user profile information, and this is where it gets really interesting for Sling: I think this is something we can work on. And finally creating GUI to manage all these things ... I think all in all, such stuff would make for a nice extension to the basic offerings of Sling. Regards Felix
Upgrade to Jackrabbit 1.5 (was: user management)
Hi all, Now that the Jackrabbit project has released 1.5 which contains a lot of new functionality and even initial implementation of JSR-283 functionality, it would probably good to upgrade our Jackrabbit dependencies to 1.5. WDYT ? Regards Felix Felix Meschberger schrieb: > Hi Torgei, > > Torgeir Veimo schrieb: >> Even though user management will not be part of sling it would be good >> to have a common implementation. So I'm wondering if anyone else is >> working on something here, and / or if this would fit into a sort of >> sling-commons project. > > I do not know of any open-source implementation under way for Sling. But > I would assume, it would definitely be a good addition to Sling. > > >> With user management I'm thinking about; >> >> glue between login form page and jcr authenticatio > > I assume you are talking about an AuthenticationHandler ? > >> user node type definitions with most common properties for basic users; >> uid, password, >> basic group node types >> basic manager for managing users and groups; add/remove/update, change >> group membership. > > This sounds like two stories: One story is probably a LoginHandler and > an AccessManager for Jackrabbit and the other story is adding "user > profile" information. > > Before setting out to implement anything new, you might want take a look > at what has been done around JCR-1171 with respect to (start to) > implement what will utimately become support JSR-283 (JCR2.0) access > control specificaiton. This has actually been released as part of the > Jackrabbit 1.5 release. > > I have to admit, that I do not know much about this stuff (yet -- well, > another area to catch up on ;-) ), but it might be worth looking at that. > > The other part of the story is the user profile information, and this is > where it gets really interesting for Sling: I think this is something we > can work on. > > And finally creating GUI to manage all these things ... > > I think all in all, such stuff would make for a nice extension to the > basic offerings of Sling. > > Regards > Felix > > >
Re: Upgrade to Jackrabbit 1.5 (was: user management)
On Fri, Dec 12, 2008 at 10:12 AM, Felix Meschberger wrote: > Now that the Jackrabbit project has released 1.5 which contains a lot of > new functionality and even initial implementation of JSR-283 > functionality, it would probably good to upgrade our Jackrabbit > dependencies to 1.5. +1 Of course! ;-) Regards, Alex -- Alexander Klimetschek alexander.klimetsc...@day.com
Re: Upgrade to Jackrabbit 1.5 (was: user management)
On Fri, Dec 12, 2008 at 10:12 AM, Felix Meschberger wrote: > ...Now that the Jackrabbit project has released 1.5 which contains a lot of > new functionality and even initial implementation of JSR-283 > functionality, it would probably good to upgrade our Jackrabbit > dependencies to 1.5 +1 -Bertrand
Re: Upgrade to Jackrabbit 1.5 (was: user management)
Am 12.12.2008 um 10:12 schrieb Felix Meschberger: Now that the Jackrabbit project has released 1.5 which contains a lot of new functionality and even initial implementation of JSR-283 functionality, it would probably good to upgrade our Jackrabbit dependencies to 1.5. +1 alex
Re: Upgrade to Jackrabbit 1.5 (was: user management)
> > Now that the Jackrabbit project has released 1.5 which contains a lot of >> new functionality and even initial implementation of JSR-283 >> functionality, it would probably good to upgrade our Jackrabbit >> dependencies to 1.5. >> > > +1 > BR, Juanjo
[jira] Created: (SLING-768) jcrinstall: bundle not reactivated after adding and removing a newer version of the same bundle
jcrinstall: bundle not reactivated after adding and removing a newer version of the same bundle --- Key: SLING-768 URL: https://issues.apache.org/jira/browse/SLING-768 Project: Sling Issue Type: Bug Components: JCR Install Reporter: Bertrand Delacretaz Priority: Minor Scenario: 1. Install a bundle V1.0 by copying it to the repository under /libs/install 2. Copy bundle V1.1 to /libs/install -> jcrinstall uninstalls V1.0 and installs V1.1, ok 3. Remove V1.1 -> V1.0 not reactivated, even though it is still present in /libs/install Workaround: remove and re-add V1.0 to /libs/install -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-757) Cannot configure SlingAuthenticator "anonymous access" setting, need webconsole update
[ https://issues.apache.org/jira/browse/SLING-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-757: -- Summary: Cannot configure SlingAuthenticator "anonymous access" setting, need webconsole update (was: changing default access rights not possible) > Cannot configure SlingAuthenticator "anonymous access" setting, need > webconsole update > -- > > Key: SLING-757 > URL: https://issues.apache.org/jira/browse/SLING-757 > Project: Sling > Issue Type: Bug > Environment: vista >Reporter: Michael Marth > > Trying to change the default access rights is not possible in the Sling > console. > Go to > http://localhost:/system/console/configMgr/org.apache.sling.engine.impl.auth.SlingAuthenticator > Untick "auth.annonymous.name", > hit "save" > -> result: option still ticked > (btw: "auth.annonymous.name" is a bit cryptic :) ) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SLING-315) Groovy support
[ https://issues.apache.org/jira/browse/SLING-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-315. - Resolution: Fixed Now that Paul King (thanks again) has deployed a Groovy 1.6 RC 1 SNAPSHOT yesterday, which also includes required DynamicImport-Package I assume we can mark this issue resolved. I have updated the web page indicating the current download locations. If you are satisified with this outcome, please close this issue. Thanks. > Groovy support > -- > > Key: SLING-315 > URL: https://issues.apache.org/jira/browse/SLING-315 > Project: Sling > Issue Type: New Feature > Components: Scripting >Affects Versions: 3 > Environment: all >Reporter: Christian Sprecher >Assignee: Felix Meschberger >Priority: Minor > Attachments: diff.txt, groovy-engine-1.0.jar, groovy.tar.gz, pom.xml > > Original Estimate: 48h > Remaining Estimate: 48h > > Implement Groovy as an option for scripting language support. A patch with a > possible implementation will be attached -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-757) Cannot configure SlingAuthenticator "anonymous access" setting, need webconsole update
[ https://issues.apache.org/jira/browse/SLING-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655954#action_12655954 ] Bertrand Delacretaz commented on SLING-757: --- I talked to (our) Felix and he says he'll try to make a Felix webconsole release happen soon, so that we can upgrade it in Sling. For now, the workaround is to build the webconsole from the source at http://svn.apache.org/repos/asf/felix/trunk/webconsole, and install the resulting jar in Sling via http://localhost:/system/console/bundles > Cannot configure SlingAuthenticator "anonymous access" setting, need > webconsole update > -- > > Key: SLING-757 > URL: https://issues.apache.org/jira/browse/SLING-757 > Project: Sling > Issue Type: Bug > Environment: vista >Reporter: Michael Marth > > Trying to change the default access rights is not possible in the Sling > console. > Go to > http://localhost:/system/console/configMgr/org.apache.sling.engine.impl.auth.SlingAuthenticator > Untick "auth.annonymous.name", > hit "save" > -> result: option still ticked > (btw: "auth.annonymous.name" is a bit cryptic :) ) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-768) jcrinstall: bundle not reactivated after adding and removing a newer version of the same bundle
[ https://issues.apache.org/jira/browse/SLING-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655959#action_12655959 ] Felix Meschberger commented on SLING-768: - > 2. Copy bundle V1.1 to /libs/install -> jcrinstall uninstalls V1.0 and > installs V1.1, ok I assume you mean V1.0 is updated to V1.1, right ? > jcrinstall: bundle not reactivated after adding and removing a newer version > of the same bundle > --- > > Key: SLING-768 > URL: https://issues.apache.org/jira/browse/SLING-768 > Project: Sling > Issue Type: Bug > Components: JCR Install >Reporter: Bertrand Delacretaz >Priority: Minor > > Scenario: > 1. Install a bundle V1.0 by copying it to the repository under /libs/install > 2. Copy bundle V1.1 to /libs/install -> jcrinstall uninstalls V1.0 and > installs V1.1, ok > 3. Remove V1.1 -> V1.0 not reactivated, even though it is still present in > /libs/install > Workaround: remove and re-add V1.0 to /libs/install -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-769) Upgrade Jackrabbit Dependency to 1.5
Upgrade Jackrabbit Dependency to 1.5 Key: SLING-769 URL: https://issues.apache.org/jira/browse/SLING-769 Project: Sling Issue Type: Improvement Components: JCR Affects Versions: JCR Webdav 2.0.2, JCR OCM 2.0.2, JCR Jackrabbit Server 2.0.2, JCR Jackrabbit Client 2.0.2, JCR Jackrabbit API 2.0.2, JCR Classloader 2.0.2 Reporter: Felix Meschberger Assignee: Felix Meschberger The Jackrabbit project has released 1.5 of Jackrabbit. As a consequence we should also upgrade our infrastructure to Jackrabbit 1.5. As a consequence we do not need that jackrabbit.api module anymore, because Jackrabbits jackrabbit.api library has Bundle manifest headers and can now directly be used. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-315) Groovy support
[ https://issues.apache.org/jira/browse/SLING-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Sprecher closed SLING-315. > Groovy support > -- > > Key: SLING-315 > URL: https://issues.apache.org/jira/browse/SLING-315 > Project: Sling > Issue Type: New Feature > Components: Scripting >Affects Versions: 3 > Environment: all >Reporter: Christian Sprecher >Assignee: Felix Meschberger >Priority: Minor > Attachments: diff.txt, groovy-engine-1.0.jar, groovy.tar.gz, pom.xml > > Original Estimate: 48h > Remaining Estimate: 48h > > Implement Groovy as an option for scripting language support. A patch with a > possible implementation will be attached -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-315) Groovy support
[ https://issues.apache.org/jira/browse/SLING-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655994#action_12655994 ] Christian Sprecher commented on SLING-315: -- superb work, thank you all! > Groovy support > -- > > Key: SLING-315 > URL: https://issues.apache.org/jira/browse/SLING-315 > Project: Sling > Issue Type: New Feature > Components: Scripting >Affects Versions: 3 > Environment: all >Reporter: Christian Sprecher >Assignee: Felix Meschberger >Priority: Minor > Attachments: diff.txt, groovy-engine-1.0.jar, groovy.tar.gz, pom.xml > > Original Estimate: 48h > Remaining Estimate: 48h > > Implement Groovy as an option for scripting language support. A patch with a > possible implementation will be attached -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-768) jcrinstall: bundle not reactivated after adding and removing a newer version of the same bundle
[ https://issues.apache.org/jira/browse/SLING-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12655960#action_12655960 ] Bertrand Delacretaz commented on SLING-768: --- > I assume you mean V1.0 is updated to V1.1, right ? Yes, correct > jcrinstall: bundle not reactivated after adding and removing a newer version > of the same bundle > --- > > Key: SLING-768 > URL: https://issues.apache.org/jira/browse/SLING-768 > Project: Sling > Issue Type: Bug > Components: JCR Install >Reporter: Bertrand Delacretaz >Priority: Minor > > Scenario: > 1. Install a bundle V1.0 by copying it to the repository under /libs/install > 2. Copy bundle V1.1 to /libs/install -> jcrinstall uninstalls V1.0 and > installs V1.1, ok > 3. Remove V1.1 -> V1.0 not reactivated, even though it is still present in > /libs/install > Workaround: remove and re-add V1.0 to /libs/install -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-770) Integration tests fail due to change in default rendering semantics
Integration tests fail due to change in default rendering semantics --- Key: SLING-770 URL: https://issues.apache.org/jira/browse/SLING-770 Project: Sling Issue Type: Bug Components: Testing Reporter: Bertrand Delacretaz The changes of SLING-723 cause many launchpad/testing tests to fail, as they expect that a node URL without extension produces the default .txt rendering. After SLING-723, requesting /foo redirects to /foo/ instead of acting like /foo.txt as it did before. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Default GET Servlets
Hi, I just see, that I owe you an answer to this. Sorry for the delay. Bertrand Delacretaz schrieb: > Hi Felix, > > On Mon, Dec 8, 2008 at 8:25 AM, Felix Meschberger wrote: >> ...I have prepared an implementation for the StreamRendering for the >> DefaultGetServlet now, which is slightly different to the proposal:... > > +1 to the suggested changes. > >> ... Default is index.files=["index","index.html"] and index=true... > > Should there be a default extension as well, for when Sling redirect > to .../index ? Yes, if the index file has no extension ".html" is appended by Sling before including the index file. This is hardcoded. > > IIRC the current default extension in Sling is .txt, but I assume in > this case we want html as the default. Maybe html should be the > default everywhere. Agreed, this is why the automated directory listing just sends HTML. The previous "defaul" was caused by the fact, that the StreamRendererServlet handling requests without extension extended from the PlainTextRendererServlet and called its doGet method if the resource does not adapt to an InputStream. It should probably have had to extend from HtmlRendererServlet in the first place. But this is past ;-) Regards Felix
[jira] Closed: (SLING-770) Integration tests fail due to change in default rendering semantics
[ https://issues.apache.org/jira/browse/SLING-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz closed SLING-770. - Resolution: Fixed Fixed in revision 726016 - that revision is a good example of what needs to be changed if people hit similar issues in their applications. > Integration tests fail due to change in default rendering semantics > --- > > Key: SLING-770 > URL: https://issues.apache.org/jira/browse/SLING-770 > Project: Sling > Issue Type: Bug > Components: Testing >Reporter: Bertrand Delacretaz > > The changes of SLING-723 cause many launchpad/testing tests to fail, as they > expect that a node URL without extension produces the default .txt rendering. > After SLING-723, requesting /foo redirects to /foo/ instead of acting like > /foo.txt as it did before. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (SLING-771) Upgrade to latest Felix framework release
Upgrade to latest Felix framework release - Key: SLING-771 URL: https://issues.apache.org/jira/browse/SLING-771 Project: Sling Issue Type: Improvement Components: Launchpad Launcher Affects Versions: Launchpad Base 2.0.2 Reporter: Carsten Ziegeler Fix For: Launchpad Base 2.0.4 As discussed in the mailing list updating to the latest Felix framework should bring some improvements. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
RE: Data Validation
Bertrand, I wouldn't mind taking a crack at something but I'm not sure I'd know where to start. I only just started looking at sling. I wonder if you might have some suggestions. Here are some problems I have: If we went with a request filter the filtered posts, the filter would have to be able to resolve a validation resource. It could then validate the request. If the validation failed, the filter would have to know how to re-render the "edit" resource. Would the idea be to have the posting form contain some @suffix type fields that the filter could use to resolve the validation resource and the "edit" resource? -Original Message- From: bdelacre...@gmail.com [mailto:bdelacre...@gmail.com] On Behalf Of Bertrand Delacretaz Sent: Thursday, December 11, 2008 7:59 AM To: sling-dev@incubator.apache.org Subject: Re: Data Validation Hi Darrell, On Tue, Dec 9, 2008 at 6:22 PM, Darrell Pittman wrote: > ...I see what I have to do, thanks. Is there any plan to > incorporate some kind of validation functionality in the future?... I don't think we have a concrete plan to do that, but a validation framework would IMHO be a nice thing to have in Sling. A request filter that validates request parameters, combined with a utility that makes it easy for scripts to use request parameters values and validation errors to fill form fields instead of using the current node's values, is probably all that's needed. I would make the filter generic and use OSGi services and/or server-side scripts to define specific validations. As usual, contributions are welcome - I don't think any of the current committers is working on that at the moment, but if you want to propose a solution we can certainly help with design and review. -Bertrand
[jira] Closed: (SLING-771) Upgrade to latest Felix framework release
[ https://issues.apache.org/jira/browse/SLING-771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-771. -- Resolution: Duplicate This is a duplicate of SLING-712 > Upgrade to latest Felix framework release > - > > Key: SLING-771 > URL: https://issues.apache.org/jira/browse/SLING-771 > Project: Sling > Issue Type: Improvement > Components: Launchpad Launcher >Affects Versions: Launchpad Base 2.0.2 >Reporter: Carsten Ziegeler > Fix For: Launchpad Base 2.0.4 > > > As discussed in the mailing list updating to the latest Felix framework > should bring some improvements. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Data Validation
Darrell Pittman wrote: > Bertrand, > > I wouldn't mind taking a crack at something but I'm not sure I'd know > where to start. I only just started looking at sling. I wonder if you > might have some suggestions. Here are some problems I have: > > If we went with a request filter the filtered posts, the filter would > have to be able to resolve a validation resource. It could then > validate the request. If the validation failed, the filter would have > to know how to re-render the "edit" resource. Would the idea be to have > the posting form contain some @suffix type fields that the filter could > use to resolve the validation resource and the "edit" resource? > One possibility is to use a validation servlet instead of filter. You register the servlet for POST with a specific selector and then post your form to your resource with something like ".form.html", e.g. you post to "/mycontent/cars/ferrari.form.html". The servlet validates the form values and if the values are invalid just forwards to re-render the form by using method get (/mycontent/cars/ferrari.html"). If everything is valid the servlet just forwards to the sling post servlet. For registering your servlet, it should set the property "sling.servlet.selectors" to "form" and the property "sling.servlet.methods" to POST, so all POST requests having the selector "form" in the url are handled by this servlet. HTH Carsten -- Carsten Ziegeler cziege...@apache.org
Metatype information not showing up in webconsole
I noticed this several months back, that metatype information was not being rendered in the webconsole for some configuration options. Originally, it would happen after installing updated bundles (after a fresh checkout & build from trunk). Michael Marth alluded to this in SLING-757: > btw: "auth.annonymous.name" is a bit cryptic However, the metatype strings are showing up for some configs (notably the Sling POST Servlet). I can't see any difference between the bundle JARs - both contain metatype.xml and metatype.properties, and they look correct to me. Any idea why this is happening?
Re: Metatype information not showing up in webconsole
It looks like bundles with version 2.0.2.incubator all have their metatype strings appearing correctly, and any that are version 2.0.3.incubator-SNAPSHOT don't. This is after doing an update, clean, install cycle against trunk. If I subsequently update a 2.0.2 bundle to a 2.0.3snapshot via webconsole, it's configuration metatype strings stop working too (tried this with Sling POST servlet bundle). Rory Douglas wrote: I noticed this several months back, that metatype information was not being rendered in the webconsole for some configuration options. Originally, it would happen after installing updated bundles (after a fresh checkout & build from trunk). Michael Marth alluded to this in SLING-757: > btw: "auth.annonymous.name" is a bit cryptic However, the metatype strings are showing up for some configs (notably the Sling POST Servlet). I can't see any difference between the bundle JARs - both contain metatype.xml and metatype.properties, and they look correct to me. Any idea why this is happening?
Path component disappears
I have a node at path /sample/content/test, with a child node /entries. "entries" has a sling:resourceType="test/EntryList", but there is no script registered for that resourceType. If I browse to http://localhost:/sample/content/test/entries (i.e no selectors or extension), I get redirected to http://localhost:/sample/test/entries/ I realize some work has gone on recently with directory listing and resource resolution, but is this supposed to happen? The ResourceResolver mapping property is set to /content/- (a default value), which I had interpreted to mean URLs prefixed with /content, not all URLs containing /content. The checkbox next to "resource.resolver.new.name" is checked, but like the problem with the SlingAuthenticator allow-anonymous-access config, I'm unable to uncheck it.
Re: Path component disappears
Hi Rory, On Fri, Dec 12, 2008 at 10:07 PM, Rory Douglas wrote: > ...If I browse to http://localhost:/sample/content/test/entries (i.e > no selectors or extension), I get redirected to > http://localhost:/sample/test/entries/... Yes, this recently changed (see SLING-770 for example) - you need to add an extension to see the "entries" node URL, .txt, .json, .xml ... > ...The checkbox next to "resource.resolver.new.name" > is checked, but like the problem with the SlingAuthenticator > allow-anonymous-access config, I'm unable to uncheck it... The workaround is to install a more recent snapshot of the webconsole, see links to that in SLING-757 -Bertrand
Re: Reference Properties
Hi Darrell, On Wed, Dec 3, 2008 at 7:24 PM, Darrell Pittman wrote: >... Is there a way to post an html form in sling and have it automatically > create a REFERENCE property or do I have to handle to post in code and > create the REFERENCE property manually The SlingPostServlet doesn't support reference properties currently, the SlingPropertyValueHandler [1] is where that would happen, with a new type hint and using the value of the request parameter as the path of the referenced node, I assume. -Bertrand [1] https://svn.eu.apache.org/repos/asf/incubator/sling/trunk/servlets/post/src/main/java/org/apache/sling/servlets/post/impl/helper/SlingPropertyValueHandler.java
Re: Path component disappears
I understand the part about requiring an extension to see the node contents, and how sling is appending a / to the URL to allow the directory listing feature to work if enabled, but should it be swallowing the "/content/" element in the path when it does so? It seems arbitrary: /sample/content/test/entries --> /sample/test/entries/ Bertrand Delacretaz wrote: Hi Rory, On Fri, Dec 12, 2008 at 10:07 PM, Rory Douglas wrote: ...If I browse to http://localhost:/sample/content/test/entries (i.e no selectors or extension), I get redirected to http://localhost:/sample/test/entries/... Yes, this recently changed (see SLING-770 for example) - you need to add an extension to see the "entries" node URL, .txt, .json, .xml ... ...The checkbox next to "resource.resolver.new.name" is checked, but like the problem with the SlingAuthenticator allow-anonymous-access config, I'm unable to uncheck it... The workaround is to install a more recent snapshot of the webconsole, see links to that in SLING-757 -Bertrand -- Rory Douglas | Senior Principal Consultant Fax: +1-201-604-6428 | Mobile: +1-917-498-5344 Oracle North America Consulting ORACLE United States | | San Diego, CA "Please consider your environmental responsibility before printing this e-mail"
