David Duhme ist außer Haus. -Virus checked-

2007-01-17 Thread David Duhme
Ich werde ab  17.01.2007 nicht im Büro sein. Ich kehre zurück am  18.01.2007.

Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



David Duhme ist außer Haus. -Virus checked-

2007-01-01 Thread David Duhme
Ich werde ab  01.01.2007 nicht im Büro sein. Ich kehre zurück am  05.01.2007.

Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



David Duhme ist außer Haus. -Virus checked-

2006-09-04 Thread David Duhme
Ich werde ab  04.09.2006 nicht im Büro sein. Ich kehre zurück am  22.09.2006.

Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



David Duhme ist außer Haus. -Virus checked-

2006-07-31 Thread David Duhme
Ich werde ab  31.07.2006 nicht im Büro sein. Ich kehre zurück am  07.08.2006.

Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



David Duhme ist außer Haus. -Virus checked-

2005-12-19 Thread David Duhme
Ich werde ab  19.12.2005 nicht im Büro sein. Ich kehre zurück am  06.01.2006.

Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Portal 2.1.8 authentication behind a proxy not working -Virus checked-

2005-12-14 Thread David Duhme

Hello,

the authentication process of the new
portal engine 2.1.8 is not working when I'm behind a proxy server. Without
the proxy there's no problem.

I already removed all sample coplets
from the portal but that didn't solve it.

Does somebody know which components
in the authentication process (I think it's the new Cowarp mechanism)
needs external access and why?

Thanks,

David Duhme.


[Solved] Getting started with LDAPEntryManager -Virus checked-

2005-10-13 Thread David Duhme

I think I found the problem why the
LDAPEntryManager wasn't initialized correctly.

I changed the role attribute in cocoon.xconf
from

"org.apache.cocoon.component.EntryManager"

to

"org.apache.cocoon.components.naming.EntryManager"

and the error message when requesting
the FlowScript disappeared.

Perhaps somebody should adjust this
in the API ...

Regards,

David Duhme

Wilhelm Karmann GmbH
- Kommunikationsprozesse -
Karmannstrasse 1
49084 Osnabrueck
Telefon: +49 541 581 7280
Telefax: 
E-Mail: mailto:[EMAIL PROTECTED]
http://www.karmann.com

Getting started with LDAPEntryManager -Virus checked-

2005-10-12 Thread David Duhme

Hi,

again my topic is getting ldap updates
and adds working...

I tried loading the LDAPEntryManager
from Jeremy Quinn in my FlowScript.

I configured the LDAPEntryManager as
described in the API, in cocoon.xconf


                
  
                
  
                
  
                
  
  

Then I do

var em
= cocoon.getComponent(org.apache.cocoon.components.naming.LDAPEntryManager.ROLE);

in the FlowScript.

But all I get is an error message

org.apache.avalon.framework.service.ServiceException:
Unable to lookup component: org.apache.cocoon.components.naming.EntryManager
(Key='ComponentManagerWrapper')

I get no error with

var em
= new Packages.org.apache.cocoon.components.naming.LDAPEntryManager;

I'm not really sure what's the difference
is but I think the component isn't configured correctly if
I just call the constructor.

Please correct me if I'm wrong with
that.

So all I need to know is how to load
the component LDAPEntryManager from FlowScript.
Maybe it's just a stupid beginner issue...
I don't know.



Regards,

David Duhme

Wilhelm Karmann GmbH
- Kommunikationsprozesse -
Karmannstrasse 1
49084 Osnabrueck
Telefon: +49 541 581 7280
Telefax: 
E-Mail: mailto:[EMAIL PROTECTED]
http://www.karmann.com

Re: LDAP operations in cocoon -Virus checked-

2005-10-10 Thread David Duhme

First of all, thanks for your reply.

I think I'll try to build something
with the novell ldap client library...

But I thought the existing LDAPEntryManager
was an approach to
implement LDAP adds and updates from
FlowScript and I could
avoid writing my own component which
is always a bit time consuming ;-)

So still... if someone has already experiences
using LDAP directories,
help would be fine.


Regards,

David Duhme

Wilhelm Karmann GmbH
- Kommunikationsprozesse -
Karmannstrasse 1
49084 Osnabrueck
Telefon: +49 541 581 7280
Telefax: 
E-Mail: mailto:[EMAIL PROTECTED]
http://www.karmann.com





Christoph Hermann <[EMAIL PROTECTED]>

10.10.2005 19:36



Bitte antworten an
users@cocoon.apache.org





An
users@cocoon.apache.org


Kopie



Thema
Re: LDAP operations in cocoon
-Virus checked-








Am Montag, 10. Oktober 2005 17:33 schrieb David Duhme:

Hello,

> I successfully implemented LDAP authentication for the portal which
in
> fact is just a read operation.

fine.

> But now I need my webapp to read entries from a LDAP directory (Lotus
> Domino in my case)
> and make some attributes editable with CForms.

I really don't know how to make this (updates) work with the LDAP Transformer.

> I'm not sure wether to use the LDAP Transformer or the LDAPEntryManager.
> LDAPEntryManager seams more suiteable to me because it's accessable
> from FlowScript.
>
> Please could somebody give me a hint on how to get started with the
> LDAPEntryManager.
> Or am I better off with the LDAP Transformer??

A Quote from IRC (FreeNode #cocoon:Okt 03 17:55:39):
   just write a component that updates an LDAP directory
and call it 
from flowscript, action or XSP
   if you want a decent LDAP client library, use the
Novell one
   LDAPModification mod[] = new LDAPModification[1];
   LDAPAttribute userPassword = new LDAPAttribute("userPassword",

user.getPassword());
           mod[0] = new LDAPModification(LDAPModification.REPLACE,

userPassword);
   LDAPConnection lc =  /* Open a connection somehow
*/
   LDAPConnection lc = new LDAPConnection();

HTH
Christoph

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



LDAP operations in cocoon -Virus checked-

2005-10-10 Thread David Duhme

Hi everybody,

I'm a bit confused about the featured
LDAP operations in cocoon.

I successfully implemented LDAP authentication
for the portal which in fact is
just a read operation. 

But now I need my webapp to read entries
from a LDAP directory (Lotus Domino in my case)
and make some attributes editable with
CForms.

I'm not sure wether to use the LDAP
Transformer or the LDAPEntryManager.
LDAPEntryManager seams more suiteable
to me because it's accessable
from FlowScript.

Please could somebody give me a hint
on how to get started with the LDAPEntryManager.
Or am I better off with the LDAP Transformer??

Thanks a lot...

Regards,

David Duhme

Wilhelm Karmann GmbH
- Kommunikationsprozesse -
Karmannstrasse 1
49084 Osnabrueck
Telefon: +49 541 581 7280
Telefax: 
E-Mail: mailto:[EMAIL PROTECTED]
http://www.karmann.com

Re: [Portal] coplet transformer links

2005-02-01 Thread David Duhme

Hi, 

> 
> >>Are you using CachingURICoplet or URICoplet ?
> >>    
> >>
> >
> >I'm using the CachingURICoplet
> >
> >David.
> >
> >
> >
> >  
> >
> Hi David,
> 
> Just a hint: i keep cl:links for URI coplets, 
> with cachingURI coplets i
> usually use cl:links and bookmarks to transfer 
> some data to another
> coplet or pass something about its layout. If 
> the targeted pipeline is
> still the same- say 
> temporaryAttributes/application-uri is the same-, i
> think it is much easier to use a usual 
> hred"uri?req-param1&req-param2">Next,
the
> portal-eventlink-transformer coming wth 
> CachingURI will  let your coplet
> pipeline know about the new req-params by events
> way . Then you can
> style it too.
> I guess the cachingURI coplets have been 
> designed to do this. You
> develop your app and then put it in the portal as it is.
> 
> If you still want the cl:link, no idea, but just
> try replace $copletid
> by its actual value and add the 
> temporaryAttributes/application-uri value.
> 
> Hope it helps,
> Phil
> 
> 

Thanks Phil.

I think I will try it again with request parameters
because it didn't
work with , wether with the cachingURI
coplet nor with the URI coplet. With
the URIcoplet the pipeline is called again when I
hit a link but the parameter
doesn't change and the old one from copletinstancedata/portal.xml
is used.

But I need to execute a diiferent query in my generator,
so somehow I have
to pass the changed parameters to the generator. Maybe
me pipeline is still
wrong and I'm fetching the old parameters all the
time.

        
           
    
           
            
           
            
           
            
           
            
           
            
           
    
           
    
           
            
           
            
           
      
           
    
        


Here again the part of my stylesheet:

        
           
    
           
             path="attributes/query"

           
               value="'&RestrictToCategory=[username]&Count=10&Expand=1'"
/>
           
    
           
            
           
    
        

Perhaps you could tell me the difference between 'temporaryAttributes'
and 'attributes'
and what's the difference in definig attributes in
'copletdata/portal.xml' or
'copletinstancedata/portal.xml'.

Regards,

David.

        


Re: [Portal] menus and i18n

2005-02-01 Thread David Duhme

Hi, 

> 
> I don't know what you mean by "more 
> dynamic contents", 
> 

ok sorry, I admit that it's not clear what
that  means.

I was talking about content coming from a
database (relational or in my case lotus notes database).

I'm working on a solution to translate view headers
that are defined on the notes side. I think I need
a stylesheet that adds the necessary i18n tags to
the xml data stream.

Regards,

David.

Re: [Portal] coplet transformer links

2005-01-28 Thread David Duhme
> Are you using CachingURICoplet or URICoplet ?

I'm using the CachingURICoplet

David.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [Portal] menus and i18n

2005-01-28 Thread David Duhme
Hi Philippe,

I also have the requirement for my portal prototype
to do i18n. 

> 3- do an i18n transformation on the main portal 
> pipeline after the 
> portal-page.xsl XSL transformation
> (I'm worried it would slow down performance to 
> parse all portal pages again)

Thats what I've implemented at the moment and I didn't recognize
any big problems concerning the performance.

What seams to be a bit more difficult is the translation
of the more dynamic contents of the portal. So if anyone has
a good concept for portal internationalization, I would be
interested in that.

Regards,

David.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[Portal] coplet transformer links

2005-01-28 Thread David Duhme
Hello,

I'm trying to build links in a coplets which reload the content of a 
coplet
depending an different coplet attributes. My first approach is the 
following:


  
  
next Page
  


This renders without errors and the coplet is displayed correctly and the 
links
are reccognized. But the URL seams wrong to me:

...portal?cocoon-portal-action=1

Isn't there an event parameter missing?

If I click the link the portal page is reloaded but nothing happens. Not 
even
the coplet pipeline is called again.

Anyone got an idea what goes wrong?

Thanks,

David.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [Portal] change content of a CachingURICoplet

2005-01-27 Thread David Duhme

Hi Jean-Christophe,

first of all thanks for your reply.

I think I haven't yet understood completly how to
deal
with coplet parameters. So with your hints I will
try
some new approaches.

But I got another question. In which context do I
use
elements with the syntax

        
                  
 
                  
 
                  
    Page 2
                  
 
        

?

I'm generating links in an xslt stylesheet which is
handled by the
XSLT Transformer. Do I have to include a specific
namespace to use
these tags?

Regards,

David Duhme.

[Portal] change content of a CachingURICoplet

2005-01-27 Thread David Duhme
Hello Cocooners,

after several months of practicing cocoon it still takes me hours
and days to get some tricky things working. Hope I'm not the
only one making this experience ;)

Let me explain what I'm trying to do and perhaps someone can help
me with that.

I've written a custom generator which makes a Lotus Domino connection
and fetches xml out of a domino database. This generator is part of
a pipeline which serves the content for a CachingURICoplet in the cocoon
portal. The generator works similar to the Portal ProxyTransformer, that
means it is making a http-connection to the domino server and using the
domino specific url syntax.

 
http://server/datbase/view?ReadViewEntries&RestrictToCategory=category&Count=10 

(returns xml stream)

The initial parameters are passed to the generator through the coplet-data
like this


TITLE
CachingURICoplet

buffer
http://www.w3.org/2001/XMLSchema-instance";>  
   true



handleParameters
http://www.w3.org/2001/XMLSchema-instance";>  
   true



uri
http://www.w3.org/2001/XMLSchema-instance";>
 cocoon:/coplets/domino/view?server=[server]
&database=[database]
&designelement=View
&designelementname=[viewname]
&RestrictToCategory=[username]
&Count=10




For the coplet content the following pipeline is triggered:









Now my problem:
The domino server delivers only ten entries of the view because I told it 
so ('Count=10').
If there are more than ten entries in the view I need to generate links in 
the coplet which
reload the content of the coplet with different URL parameters. This means 
the pipeline
has to be executed again and the portal page has to be updated. So what 
I'm trying
to implement is some kind of google-like paging mechanism which stays in 
the context of
a portal coplet.

I know that I have to generate portal-events and specify the copletId and 
portalName
to do that, but I'm not sure which events I have to call and how to 
achieve that.

Another possibility is that I'm completly wrong and I could use the 
ApplicationCoplet
to realize this. But the ProxyTransformer seams to expect html or xhtml to 
work correctly
and the LinkTransformer needs the content of a ProxyTransfomer Instance to 
translate links.

So if there's any experienced cocoon portal user out there who can help me 
transforming
domino urls into portal-events, I would really appreciate it.

Thanks in advance,

David Duhme.
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [Poll] Portal deployment / Cocoon portal usage

2005-01-27 Thread David Duhme
> 
> 1. Are you currently using the Cocoon Portal Framework? 
> 

A) Yes we are using it. 

> 
> The following questions only if you are using 
> the Cocoon Portal framework 
> 
> 3. Why did you choose the Cocoon portal framework?
> 

B) A strategic decision was made to use Open Source 
C) Becaus of the features of the framework 

> 
> 4. What do you think is currently missing from 
> the Portal framework?
> 
A) Tools (which?) or tool support
-> Lotus Domino Support

D) Better Documentation 

> 
> 5. How do you get support for the framework 
> 
A) Through the mailing lists 
B) Reading the documentation and other publications 
D) We get external help 




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: run problem in cocoon 2.2

2004-10-06 Thread David Duhme
Return Receipt


Your document:
Re: run problem in cocoon 2.2


was received by:
David Duhme/auszubildende/karmann/de


at:
10/06/2004 11:30:13




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



js in cocoon

2004-10-06 Thread David Duhme
Return Receipt


Your document:
js in cocoon


was received by:
David Duhme/auszubildende/karmann/de


at:
10/06/2004 10:47:31




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: SSO between Cocoon and Lotus Domino

2004-10-06 Thread David Duhme

> What did you all set up on your
Lotus Notes-server to achieve the "http:?ReadViewEntries"
principle?

In general the domino server must have
the HTTP task running and the user who´s trying to access the database
via a web browser
has to have an internet password specified
in the person document.

For more information there´s a quite
good documentation of the Notes URL syntax in the Notes Designer help.

> For your problem: have you tried
building a simple cocoon action that sets the request/session information
that is needed to access the server?

Thanks for the hint, I was wondering
if Ihad to do something like that to authenticate the current user to the
domino server.
I´m reading the doucmentation about
the authentication framework at the moment. But because I´m fairly new
to cocoon
I hope that someone could help me out
with some code snippets or something.

What I have to do is pass a special
cookie called "LtpaToken" along with the request to the server.
Can I achieve that
with actions? What about FlowScript
in this context?

Cheers, David.

Sitemap

2004-10-05 Thread David Duhme
Return Receipt


Your document:
Sitemap


was received by:
David Duhme/auszubildende/karmann/de


at:
10/06/2004 08:52:23




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



SSO between Cocoon and Lotus Domino

2004-10-04 Thread David Duhme

Hi there,

does anybody know how to achieve SSO
between Cocoon and Lotus Domino?
I desperately need a solution for that
problem because this is a central point in
my project with Cocoon.

I´m using cocoon version 2.1.5 running
on a tomcat 5.0.28 server. What I´m
trying to do is create a pipeline which
reads an XML data stream out of
a domino database (domino version 6.5.2)
and transforms it into HTML.

Here´s my first effort:

...

        
         
      
         
      
         
      
        
        ...

...

Before calling the pipeline I authenticated
the user at the domnio server so that 
I have a LtpaToken cookie in my browser.
But when the pipeline executes I get
the following server error:

org.xml.sax.SAXParseException: White spaces
are required between publicId and systemId

I read about a bug in the xalan processor
which should produce the same error but applying the patch
didn´t solve the problem. What lead me to
the point that this could be an access rights issue is the fact
that when I allow access rights to 'anonymous'
on the domino databse the pipeline executes without errors.

So I have to tell the domino server somehow
that there´s an existing session but I don´t know how to do
it through a pipeline.

Thanks a lot for your help.

David.

Here´s the complete stacktrace:

Original Exception: org.xml.sax.SAXParseException:
White spaces are required between publicId and systemId.
                
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)
                
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
                
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
                
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
                
at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
                
at org.apache.xerces.impl.XMLScanner.scanExternalID(Unknown Source)
                
at org.apache.xerces.impl.XMLDocumentScannerImpl.scanDoctypeDecl(Unknown
Source)
                
at org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(Unknown
Source)
                
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
                
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
                
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
                
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
                
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
                
at org.apache.excalibur.xml.impl.JaxpParser.parse(JaxpParser.java:296)
                
at org.apache.excalibur.xml.impl.JaxpParser.parse(JaxpParser.java:315)
                
at org.apache.cocoon.components.source.SourceUtil.parse(SourceUtil.java:252)
                
at org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:116)
                
at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.processXMLPipeline(AbstractProcessingPipeline.java:545)
                
at org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.processXMLPipeline(AbstractCachingProcessingPipeline.java:173)
                
at org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:490)
                
at org.apache.cocoon.components.treeprocessor.sitemap.SerializeNode.invoke(SerializeNode.java:120)
                
at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:49)
                
at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:130)
                
at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:72)
                
at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:126)
                
at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:72)
                
at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:101)
                
at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:336)
                
at org.apache.cocoon.components.treeprocessor.TreeProcessor.process(TreeProcessor.java:277)
                
at org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:103)
                
at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:49)
                
at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:130)
                
at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.inv