You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Andrew Lindesay <ap...@lindesay.co.nz> on 2010/05/11 23:10:07 UTC
Documentation
Hello;
If I want to make modifications to pages in the documentation;
http://cayenne.apache.org/doc30/...
Is there a means of getting authentication information for that system so I can make those changes or should I give those additions and amendments to somebody to load in?
cheers.
___
Andrew Lindesay
www.silvereye.co.nz
Re: Documentation
Posted by Andrew Lindesay <ap...@lindesay.co.nz>.
Hi Andrus;
Thanks for that -- I was able to load that material in. I just added it to the "CAYDOC" so thanks for that warning.
cheers.
> I got your CLA (and forwarded that to the ASF secretary). I also added your Confluence id "apl" t...
___
Andrew Lindesay
www.silvereye.co.nz
Re: Documentation
Posted by Andrus Adamchik <an...@objectstyle.org>.
Hi Andrew,
I got your CLA (and forwarded that to the ASF secretary). I also added
your Confluence id "apl" to the editors group. Let me know if you
still don't have access.
Also note that if you update CAYDOC30 space, you will also need to
update the corresponding pages in CAYDOC space if appropriate, so that
we don't lose the docs going forward. Think of CAYDOC as the wiki
"trunk" and CAYDOC30 as "STABLE-3.0" branch.
Thanks,
Andrus
On May 13, 2010, at 11:04 AM, Andrus Adamchik wrote:
> BTW, Andrew , we have a solution for docs contributions. In fact you
> don't have to be a committer to write the docs. However since
> produced docs are distributed with Cayenne, you will need to submit
> to the ASF a signed contributor license agreement (http://apache.org/licenses/
> ), and then we can give you write access to Confluence.
>
> If you could print, sign, scan and email to me the CLA form from the
> link above, I'll set you up.
>
> Thanks,
> Andrus
>
>
> On May 13, 2010, at 10:55 AM, Andrew Lindesay wrote:
>
>> Hello;
>>
>> = = = = = = = = = = =
>>
>> It would be useful to have a mention and link from;
>>
>> .../doc30/caching-and-fresh-data.html
>>
>> to here;
>>
>> .../doc30/configuring-caching-behavior.html
>>
>> = = = = = = = = = = =
>>
>> On the page;
>>
>> .../doc30/configuring-caching-behavior.html
>>
>> I am not sure what mark-up system it uses so I have left this in
>> LaTeX for now; Ari - hope you can transcribe this OK. This appears
>> to work fine, but feel free to edit it if I have made any mistakes;
>>
>> \subsection{Configuration of JMS Change Notification in a Jetty 7
>> Deployment with ActiveMQ}
>>
>> It is assumed that the Jetty deployment has been configured to
>> "look in" {\tt lib/ext}. Also assumed is that the Jetty deployment
>> is configured to support JNDI. Both of these configurations can be
>> achieved by editing the following line in the {\tt start.ini} to
>> look something like this;
>>
>> \framebox{OPTIONS=Server,jmx,resources,websocket,ext,plus}
>>
>> In this example, the messaging middleware server \href{http://activemq.apache.org
>> }{ActiveMQ} is employed. The use of ActiveMQ assumes that the
>> necessary client ActiveMQ driver jar files from the ActiveMQ
>> distribution have been installed into the {\tt lib/ext} directory
>> in the Jetty deployment.
>>
>> In this example, the ficticious Cayenne ``Data Domain Name'' is
>> called ``foo''. In the Cayenne modeller, the ``Remote Change
>> Notifications'' is checked and the ``Connection Factory Name'' is
>> set to;
>>
>> \framebox{jms/footopicconnectionfactory}
>>
>> The following would appear in the {\tt jetty.xml} file;
>>
>> \vspace{.2in}
>> \hrule
>> \begin{verbatim}<New class="org.eclipse.jetty.plus.jndi.Resource">
>> <Arg></Arg>
>> <Arg>jms/footopicconnectionfactory</Arg>
>> <Arg>
>> <New class="org.apache.activemq.ActiveMQConnectionFactory">
>> <Arg>tcp://msg01.foo.co.nz:61616</Arg>
>> </New>
>> </Arg>
>> </New>
>>
>> <New class="org.eclipse.jetty.plus.jndi.Resource">
>> <Arg>org_apache_cayenne_access_DataRowStore_foo</Arg>
>> <Arg>
>> <New class="org.apache.activemq.command.ActiveMQTopic">
>> <Arg>foochangenotificationtopic</Arg>
>> </New>
>> </Arg>
>> </New>
>>
>> \end{verbatim}
>> \hrule
>>
>> That following would appear in the servlet's {\tt web.xml} file;
>>
>> {\small
>> \vspace{.2in}
>> \hrule
>> \begin{verbatim}
>> <resource-ref>
>> <res-ref-name>jms/footopicconnectionfactory</res-ref-name>
>> <res-type>javax.jms.TopicConnectionFactory</res-type>
>> <res-auth>Container</res-auth>
>> </resource-ref>
>>
>> <resource-env-ref>
>> <resource-env-ref-name>org_apache_cayenne_access_DataRowStore_foo</
>> resource-env-ref-name>
>> <resource-env-ref-type>javax.jms.Topic</resource-env-ref-type>
>> </resource-env-ref>
>>
>> \end{verbatim}
>> \hrule
>> }
>>
>> This configuration should enable change notification to function.
>>
>> = = = = = = = = = = =
>>
>> cheers.
>>
>> ___
>> Andrew Lindesay
>> www.silvereye.co.nz
>>
>
>
Re: Documentation
Posted by Andrus Adamchik <an...@objectstyle.org>.
BTW, Andrew , we have a solution for docs contributions. In fact you
don't have to be a committer to write the docs. However since produced
docs are distributed with Cayenne, you will need to submit to the ASF
a signed contributor license agreement (http://apache.org/licenses/),
and then we can give you write access to Confluence.
If you could print, sign, scan and email to me the CLA form from the
link above, I'll set you up.
Thanks,
Andrus
On May 13, 2010, at 10:55 AM, Andrew Lindesay wrote:
> Hello;
>
> = = = = = = = = = = =
>
> It would be useful to have a mention and link from;
>
> .../doc30/caching-and-fresh-data.html
>
> to here;
>
> .../doc30/configuring-caching-behavior.html
>
> = = = = = = = = = = =
>
> On the page;
>
> .../doc30/configuring-caching-behavior.html
>
> I am not sure what mark-up system it uses so I have left this in
> LaTeX for now; Ari - hope you can transcribe this OK. This appears
> to work fine, but feel free to edit it if I have made any mistakes;
>
> \subsection{Configuration of JMS Change Notification in a Jetty 7
> Deployment with ActiveMQ}
>
> It is assumed that the Jetty deployment has been configured to "look
> in" {\tt lib/ext}. Also assumed is that the Jetty deployment is
> configured to support JNDI. Both of these configurations can be
> achieved by editing the following line in the {\tt start.ini} to
> look something like this;
>
> \framebox{OPTIONS=Server,jmx,resources,websocket,ext,plus}
>
> In this example, the messaging middleware server \href{http://activemq.apache.org
> }{ActiveMQ} is employed. The use of ActiveMQ assumes that the
> necessary client ActiveMQ driver jar files from the ActiveMQ
> distribution have been installed into the {\tt lib/ext} directory in
> the Jetty deployment.
>
> In this example, the ficticious Cayenne ``Data Domain Name'' is
> called ``foo''. In the Cayenne modeller, the ``Remote Change
> Notifications'' is checked and the ``Connection Factory Name'' is
> set to;
>
> \framebox{jms/footopicconnectionfactory}
>
> The following would appear in the {\tt jetty.xml} file;
>
> \vspace{.2in}
> \hrule
> \begin{verbatim}<New class="org.eclipse.jetty.plus.jndi.Resource">
> <Arg></Arg>
> <Arg>jms/footopicconnectionfactory</Arg>
> <Arg>
> <New class="org.apache.activemq.ActiveMQConnectionFactory">
> <Arg>tcp://msg01.foo.co.nz:61616</Arg>
> </New>
> </Arg>
> </New>
>
> <New class="org.eclipse.jetty.plus.jndi.Resource">
> <Arg>org_apache_cayenne_access_DataRowStore_foo</Arg>
> <Arg>
> <New class="org.apache.activemq.command.ActiveMQTopic">
> <Arg>foochangenotificationtopic</Arg>
> </New>
> </Arg>
> </New>
>
> \end{verbatim}
> \hrule
>
> That following would appear in the servlet's {\tt web.xml} file;
>
> {\small
> \vspace{.2in}
> \hrule
> \begin{verbatim}
> <resource-ref>
> <res-ref-name>jms/footopicconnectionfactory</res-ref-name>
> <res-type>javax.jms.TopicConnectionFactory</res-type>
> <res-auth>Container</res-auth>
> </resource-ref>
>
> <resource-env-ref>
> <resource-env-ref-name>org_apache_cayenne_access_DataRowStore_foo</
> resource-env-ref-name>
> <resource-env-ref-type>javax.jms.Topic</resource-env-ref-type>
> </resource-env-ref>
>
> \end{verbatim}
> \hrule
> }
>
> This configuration should enable change notification to function.
>
> = = = = = = = = = = =
>
> cheers.
>
> ___
> Andrew Lindesay
> www.silvereye.co.nz
>
Re: Documentation
Posted by Andrew Lindesay <ap...@lindesay.co.nz>.
Hello;
= = = = = = = = = = =
It would be useful to have a mention and link from;
.../doc30/caching-and-fresh-data.html
to here;
.../doc30/configuring-caching-behavior.html
= = = = = = = = = = =
On the page;
.../doc30/configuring-caching-behavior.html
I am not sure what mark-up system it uses so I have left this in LaTeX for now; Ari - hope you can transcribe this OK. This appears to work fine, but feel free to edit it if I have made any mistakes;
\subsection{Configuration of JMS Change Notification in a Jetty 7 Deployment with ActiveMQ}
It is assumed that the Jetty deployment has been configured to "look in" {\tt lib/ext}. Also assumed is that the Jetty deployment is configured to support JNDI. Both of these configurations can be achieved by editing the following line in the {\tt start.ini} to look something like this;
\framebox{OPTIONS=Server,jmx,resources,websocket,ext,plus}
In this example, the messaging middleware server \href{http://activemq.apache.org}{ActiveMQ} is employed. The use of ActiveMQ assumes that the necessary client ActiveMQ driver jar files from the ActiveMQ distribution have been installed into the {\tt lib/ext} directory in the Jetty deployment.
In this example, the ficticious Cayenne ``Data Domain Name'' is called ``foo''. In the Cayenne modeller, the ``Remote Change Notifications'' is checked and the ``Connection Factory Name'' is set to;
\framebox{jms/footopicconnectionfactory}
The following would appear in the {\tt jetty.xml} file;
\vspace{.2in}
\hrule
\begin{verbatim}<New class="org.eclipse.jetty.plus.jndi.Resource">
<Arg></Arg>
<Arg>jms/footopicconnectionfactory</Arg>
<Arg>
<New class="org.apache.activemq.ActiveMQConnectionFactory">
<Arg>tcp://msg01.foo.co.nz:61616</Arg>
</New>
</Arg>
</New>
<New class="org.eclipse.jetty.plus.jndi.Resource">
<Arg>org_apache_cayenne_access_DataRowStore_foo</Arg>
<Arg>
<New class="org.apache.activemq.command.ActiveMQTopic">
<Arg>foochangenotificationtopic</Arg>
</New>
</Arg>
</New>
\end{verbatim}
\hrule
That following would appear in the servlet's {\tt web.xml} file;
{\small
\vspace{.2in}
\hrule
\begin{verbatim}
<resource-ref>
<res-ref-name>jms/footopicconnectionfactory</res-ref-name>
<res-type>javax.jms.TopicConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
<resource-env-ref>
<resource-env-ref-name>org_apache_cayenne_access_DataRowStore_foo</resource-env-ref-name>
<resource-env-ref-type>javax.jms.Topic</resource-env-ref-type>
</resource-env-ref>
\end{verbatim}
\hrule
}
This configuration should enable change notification to function.
= = = = = = = = = = =
cheers.
___
Andrew Lindesay
www.silvereye.co.nz
Re: Documentation
Posted by Aristedes Maniatis <ar...@maniatis.org>.
Yes I agree. Someone could be made a committer on the basis of their documentation contributions. But we've never given anyone access to the documentation without also making them a committer to svn. At least not yet.
Ari
On 12/05/10 9:40 AM, Mike Kienenberger wrote:
> Just to be clear, we don't "change the rules." We add individuals who
> have a track record of positive community-reviewed changes as
> committers. That's as true for documentation as it is for code.
>
>
> On Tue, May 11, 2010 at 7:29 PM, Aristedes Maniatis<ar...@maniatis.org> wrote:
>> On 12/05/10 7:10 AM, Andrew Lindesay wrote:
>>>
>>> If I want to make modifications to pages in the documentation;
>>>
>>> http://cayenne.apache.org/doc30/...
>>>
>>> Is there a means of getting authentication information for that system so
>>> I can make those changes or should I give those additions and amendments to
>>> somebody to load in?
>>
>> Because the documentation forms part of the 'product' that is Cayenne, the
>> current situation is that only committers have the rights to change the
>> documentation space. The wiki space is however more open.
>>
>> The PMC has the discretion to set and change these rules and we want to make
>> it easy for people to help improve the documentation. Why don't you start
>> for now by sending through those additions to this list and if you are going
>> to have ongoing contributions it would be in everyone's interest to make
>> that as easy as possible for you.
>>
>> Regards
>>
>> Ari
>>
>>
>>
>> --
>> -------------------------->
>> Aristedes Maniatis
>> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>>
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Re: Documentation
Posted by Mike Kienenberger <mk...@gmail.com>.
Just to be clear, we don't "change the rules." We add individuals who
have a track record of positive community-reviewed changes as
committers. That's as true for documentation as it is for code.
On Tue, May 11, 2010 at 7:29 PM, Aristedes Maniatis <ar...@maniatis.org> wrote:
> On 12/05/10 7:10 AM, Andrew Lindesay wrote:
>>
>> If I want to make modifications to pages in the documentation;
>>
>> http://cayenne.apache.org/doc30/...
>>
>> Is there a means of getting authentication information for that system so
>> I can make those changes or should I give those additions and amendments to
>> somebody to load in?
>
> Because the documentation forms part of the 'product' that is Cayenne, the
> current situation is that only committers have the rights to change the
> documentation space. The wiki space is however more open.
>
> The PMC has the discretion to set and change these rules and we want to make
> it easy for people to help improve the documentation. Why don't you start
> for now by sending through those additions to this list and if you are going
> to have ongoing contributions it would be in everyone's interest to make
> that as easy as possible for you.
>
> Regards
>
> Ari
>
>
>
> --
> -------------------------->
> Aristedes Maniatis
> GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
>
Re: Documentation
Posted by Andrew Lindesay <ap...@lindesay.co.nz>.
Hello Ari;
Thanks –– for now, I'll send that to you/list to put in.
cheers.
> Why don't you start for now by sending through those additions to this list and...
___
Andrew Lindesay
www.silvereye.co.nz
Re: Documentation
Posted by Aristedes Maniatis <ar...@maniatis.org>.
On 12/05/10 7:10 AM, Andrew Lindesay wrote:
> If I want to make modifications to pages in the documentation;
>
> http://cayenne.apache.org/doc30/...
>
> Is there a means of getting authentication information for that system so I can make those changes or should I give those additions and amendments to somebody to load in?
Because the documentation forms part of the 'product' that is Cayenne, the current situation is that only committers have the rights to change the documentation space. The wiki space is however more open.
The PMC has the discretion to set and change these rules and we want to make it easy for people to help improve the documentation. Why don't you start for now by sending through those additions to this list and if you are going to have ongoing contributions it would be in everyone's interest to make that as easy as possible for you.
Regards
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A