___
From: Javier Puerto [jpue...@gmail.com<mailto:jpue...@gmail.com>]
Sent: Monday, August 26, 2013 12:04 PM
To: users@cocoon.apache.org<mailto:users@cocoon.apache.org>
Subject: Re: [C3] Calling another from REST resource
2013/8/26 Andre Juffer mailto:andre.juf...@oulu.fi>>
I a
On 08/26/2013 12:05 PM, Javier Puerto wrote:
2013/8/26 Andre Juffer mailto:andre.juf...@oulu.fi>>
I am working on using the Java pipe. So far so so good. I have two issues:
1. I intend to use a TextSerializer in the final step as I need just a single
String returned from the other block, but
vier Puerto [jpue...@gmail.com<mailto:jpue...@gmail.com>]
Sent: Monday, August 26, 2013 12:04 PM
To: users@cocoon.apache.org<mailto:users@cocoon.apache.org>
Subject: Re: [C3] Calling another from REST resource
2013/8/26 Andre Juffer mailto:andre.juf...@oulu.fi>>
I am working on using
> --
> *From:* Javier Puerto [jpue...@gmail.com]
> *Sent:* Monday, August 26, 2013 12:04 PM
>
> *To:* users@cocoon.apache.org
> *Subject:* Re: [C3] Calling another from REST resource
>
>
>
>
> 2013/8/26 Andre Juffer
>
>> I a
To: users@cocoon.apache.org
Subject: Re: [C3] Calling another from REST resource
2013/8/26 Andre Juffer mailto:andre.juf...@oulu.fi>>
I am working on using the Java pipe. So far so so good. I have two issues:
1. I intend to use a TextSerializer in the final step as I need just a single
enter/biocomputing-and-bioinformatics
> www.oulu.fi/biocenter/groups/juffer
>
> StrucBioCat, www.strucbiocat.oulu.fi
> Triacle Biocomputing, www.triacle-bc.com
>
> --
> *From:* Thorsten Scherler [scher...@gmail.com]
> *Sent:* Monday, August 19,
le Biocomputing, www.triacle-bc.com<http://www.triacle-bc.com>
From: Thorsten Scherler [scher...@gmail.com<mailto:scher...@gmail.com>]
Sent: Monday, August 19, 2013 10:12 AM
To: users@cocoon.apache.org<mailto:users@cocoon.apache.org>
Subject: Re: [C3] Calling
PM
To: users@cocoon.apache.org
Subject: Re: [C3] Calling another from REST resource
On 08/19/2013 10:58 AM, Andre Juffer wrote:
Hi Thorsten,
I already thought that it would down to what you suggested. Seems to me that
calling a pipeline in the way you suggested is the most logical way, as the
cBioCat, www.strucbiocat.oulu.fi
> Triacle Biocomputing, www.triacle-bc.com
>
>
> *From:* Thorsten Scherler [scher...@gmail.com]
> *Sent:* Monday, August 19, 2013 10:12 AM
> *To:* users@cocoon.apache.org
> *Subject:* Re: [C3] Calling another from REST resource
>
: users@cocoon.apache.org
Subject: Re: [C3] Calling another from REST resource
On 08/15/2013 04:34 PM, Andre Juffer wrote:
To clarify my question:
I need to identify persons when they access a resource. On the client side, a
temporal hash is stored. On the server side, I use that hash to connect
On 08/15/2013 04:34 PM, Andre Juffer wrote:
> To clarify my question:
>
> I need to identify persons when they access a resource. On the client
> side, a temporal hash is stored. On the server side, I use that hash
> to connect with an account associated with a person. The hash is not
> unique, it
To clarify my question:
I need to identify persons when they access a resource. On the client side, a
temporal hash is stored. On the server side, I use that hash to connect with an
account associated with a person. The hash is not unique, it is assigned upon
signing in, and lost after signing
12 matches
Mail list logo