richfaces-svn-commits
November 2011
richfaces-svn-commits@lists.jboss.org
- 1 participants
- 160 discussions
JBoss Rich Faces SVN: r22934 - in modules/docs/trunk/Component_Reference/src/main/docbook/en-US: extras and 1 other directory.
by richfaces-svn-commits＠lists.jboss.org
Author: lfryc(a)redhat.com
Date: 2011-11-14 17:23:00 -0500 (Mon, 14 Nov 2011)
New Revision: 22934
Modified:
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Rich_inputs.xml
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richautocomplete-Customizing_the_filter.xml_sample
Log:
RFPL-1727: renamed attribute clientFilter to clientFilterFunction
Modified: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Rich_inputs.xml
===================================================================
--- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Rich_inputs.xml 2011-11-14 20:33:24 UTC (rev 22933)
+++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Rich_inputs.xml 2011-11-14 22:23:00 UTC (rev 22934)
@@ -153,12 +153,12 @@
<section id="sect-Component_Reference-richautocomplete-Customizing_the_filter_in_client_and_lazyClient_modes">
<title>Customizing the filter in <literal>client</literal> and <literal>lazyClient</literal> modes</title>
<para>
- The <sgmltag><rich:autocomplete></sgmltag> component uses the JavaScript <function>startsWith()</function> method to create the list of suggestions. The filtering is performed on the client side. Alternatively, use the <varname>clientFilter</varname> attribute to specify a custom filtering function. The custom function must accept two parameters: the <varname>subString</varname> parameter is the filtering value as typed into the text box by the user, and the <varname>value</varname> parameter is an item in the list of suggestions against which the <varname>subString</varname> must be checked. Each item is iterated through and passed to the function as the <varname>value</varname> parameter. The custom function must return a boolean value indicating whether the passed item meets the conditions of the filter, and the suggestion list is constructed from successful items.
+ The <sgmltag><rich:autocomplete></sgmltag> component uses the JavaScript <function>startsWith()</function> method to create the list of suggestions. The filtering is performed on the client side. Alternatively, use the <varname>clientFilterFunction</varname> attribute to specify a custom filtering function. The custom function must accept two parameters: the <varname>subString</varname> parameter is the filtering value as typed into the text box by the user, and the <varname>value</varname> parameter is an item in the list of suggestions against which the <varname>subString</varname> must be checked. Each item is iterated through and passed to the function as the <varname>value</varname> parameter. The custom function must return a boolean value indicating whether the passed item meets the conditions of the filter, and the suggestion list is constructed from successful items.
</para>
<example id="exam-Component_Reference-richautocomplete-Customizing_the_filter">
<title>Customizing the filter</title>
<para>
- This example demonstrates how to use a custom filter with the <varname>clientFilter</varname> attribute. The custom filter determines if the sub-string is contained anywhere in the suggestion item, instead of just at the start.
+ This example demonstrates how to use a custom filter with the <varname>clientFilterFunction</varname> attribute. The custom filter determines if the sub-string is contained anywhere in the suggestion item, instead of just at the start.
</para>
<programlisting language="XML" role="XML"><xi:include parse="text" href="extras/exam-Component_Reference-richautocomplete-Customizing_the_filter.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
</example>
Modified: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richautocomplete-Customizing_the_filter.xml_sample
===================================================================
--- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richautocomplete-Customizing_the_filter.xml_sample 2011-11-14 20:33:24 UTC (rev 22933)
+++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richautocomplete-Customizing_the_filter.xml_sample 2011-11-14 22:23:00 UTC (rev 22934)
@@ -8,6 +8,6 @@
</script>
<h:form>
<rich:autocomplete mode="client" minChars="0" autofill="false"
- clientFilter="customFilter"
+ clientFilterFunction="customFilter"
autocompleteMethod="#{autocompleteBean.autocomplete}" />
-</h:form>
+</h:form>
\ No newline at end of file
12 years, 5 months
- 1
- 0
JBoss Rich Faces SVN: r22933 - modules/docs/trunk/Component_Reference/src/main/docbook/en-US.
by richfaces-svn-commits＠lists.jboss.org
Author: lfryc(a)redhat.com
Date: 2011-11-14 15:33:24 -0500 (Mon, 14 Nov 2011)
New Revision: 22933
Modified:
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Actions.xml
Log:
RFPL-1610: small improvements of a4j:push documentation
Modified: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Actions.xml
===================================================================
--- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Actions.xml 2011-11-14 20:24:01 UTC (rev 22932)
+++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Actions.xml 2011-11-14 20:33:24 UTC (rev 22933)
@@ -731,8 +731,14 @@
<para>
Sending message using <code>TopicsContext</code> involves creating <code>TopicKey</code> instance (denominator of given message topic) and looking up for <code>TopicsContext</code> used for topic registration and message publishing.
</para>
- <important>
- For using <code>TopicsContext</code> is it necessary having <code>FacesContext</code> instance available in current thread.
+ <important id="important-Component_Reference-a4jpush-Limitations_for_using_TopicsContext_interface">
+ <title>Limitations for using <code>TopicsContext</code> interface</title>
+ <para>
+ For using <code>TopicsContext</code> is it necessary having <code>FacesContext</code> instance available in current thread.
+ </para>
+ <para>
+ The method <code>TopicsContext.lookup()</code> can be called only in context of web application class loader (<code>ServiceTracker</code> needs to be accessible for given application).
+ </para>
</important>
</section>
@@ -749,10 +755,10 @@
</para>
<programlisting language="Java" role="JAVA"><xi:include parse="text" href="extras/exam-Component_Reference-a4jpush-Integrating_Push_with_CDI_events.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<important>
- For using CDI events for producing push notifications, is it necessary having <code>FacesContext</code> instance available in current thread.
+ For using CDI events for producing push notifications, same <link linkend="important-Component_Reference-a4jpush-Limitations_for_using_TopicsContext_interface">limitations</link> applies as for using <code>TopicsContext</code> interface.
</important>
<note>
- Associations for CDI events and their handlers are constructed in application deployment. Therefore topics can't be dynamically associated using <code>Event.select(Annotation...)</code> @Push CDI qualifier.
+ Associations for CDI events and their handlers are constructed in application deployment. Therefore topics can't be dynamically associated using <code>Event.select(Annotation...)</code> and <code>@Push</code> CDI qualifier.
</note>
</section>
12 years, 5 months
- 1
- 0
JBoss Rich Faces SVN: r22932 - in modules/docs/trunk/Component_Reference/src/main/docbook/en-US: extras and 1 other directory.
by richfaces-svn-commits＠lists.jboss.org
Author: lfryc(a)redhat.com
Date: 2011-11-14 15:24:01 -0500 (Mon, 14 Nov 2011)
New Revision: 22932
Modified:
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Actions.xml
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-a4jpush-Basic_usage.java
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-a4jpush-Basic_usage.xml_sample
Log:
RFPL-1685, RFPL-1610: finishing a4j:push documentation changes for 4.1
Modified: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Actions.xml
===================================================================
--- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Actions.xml 2011-11-14 19:46:43 UTC (rev 22931)
+++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Actions.xml 2011-11-14 20:24:01 UTC (rev 22932)
@@ -533,7 +533,7 @@
<section id="sect-Component_Reference-Actions-a4jpush">
<title><sgmltag><a4j:push></sgmltag></title>
<para>
- The <sgmltag><a4j:push></sgmltag> component performs real-time updates on the client side from events raised at the server side. The events are pushed out to the client through the RichFaces messaging queue (which is bound to Java Messaging Service - <acronym>JMS</acronym>). When the <sgmltag><a4j:push></sgmltag> component is triggered by a server event, it can in turn cause Ajax updates and changes.
+ The <sgmltag><a4j:push></sgmltag> component performs real-time updates on the client side from events triggered at the server side. The events are pushed out to the client through the RichFaces messaging queue (which is bound to Java Messaging Service - <acronym>JMS</acronym>). When the <sgmltag><a4j:push></sgmltag> component is triggered by a server event, it can in turn cause Ajax updates and changes.
</para>
<para>
The <sgmltag><a4j:push></sgmltag> component uses the Comet model for pushing data to the client.
@@ -545,7 +545,7 @@
The <sgmltag><a4j:push></sgmltag> uses Atmosphere framework on both client-side and server-side. In order to use Atmosphere on server-side, it is necessary to add Atmosphere libraries into project.
</para>
<para>
- It is possible to trigger push events on server-side in several ways, which will be described later:
+ It is possible to trigger push events on server-side in several ways:
</para>
<itemizedlist>
<listitem>
@@ -587,11 +587,11 @@
No matter which type way of producing messages is chosen, message is delivered to the client based on the topic name (with optional subtopic).
</para>
<para>
- Examples of topic names might be <code>someTopic</code> or topic including subtopic <code>subtopic@anotherTopic</code>.
+ Examples of topic names might be <code>someTopic</code> or <code>subtopic@anotherTopic</code>.
</para>
- <para>
+ <note>
Push topic name format is very close to JMS topic names and thus enables seamless transport of JMS messages to RichFaces message queue.
- </para>
+ </note>
</section>
<section id="sect-Component_Reference-a4jpush-Handling_a_push_notification">
@@ -619,7 +619,7 @@
<title>Updating DOM for each push notification</title>
<programlisting language="XML" role="XML"><xi:include parse="text" href="extras/exam-Component_Reference-a4jpush-Updating_DOM_for_each_push_notification.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
- The example uses the <varname>dataavailable</varname> event handler to trigger ajax update of the part of the page.
+ The example uses the <varname>dataavailable</varname> event handler to trigger AJAX request and partial page update.
</para>
</example>
</section>
@@ -706,18 +706,15 @@
<programlisting language="XML" role="XML"><xi:include parse="text" href="extras/exam-Component_Reference-a4jpush-Basic_usage.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<programlisting language="Java" role="JAVA"><xi:include parse="text" href="extras/exam-Component_Reference-a4jpush-Basic_usage.java" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
- The example demonstrates a simple use of the <sgmltag><a4j:push></sgmltag> component to manage a list of users in a chat room. The <sgmltag><a4j:push></sgmltag> component refers to the <code>#{chatBean.listSubtopic}@chat</code> address, which has been created on the JMS server. It then uses the sub-topics to separate messages across different topics.
+ The example demonstrates a simple use of the <sgmltag><a4j:push></sgmltag> causing immediate update of page content.
</para>
- <para>
- When a new message arrives, the <sgmltag><a4j:ajax></sgmltag> behavior causes the user list to update. If an error occurs, the user is alerted.
- </para>
</example>
</section>
<section id="sect-Component_Reference-a4jpush-Using_Push_without_JMS">
<title>Using Push without JMS</title>
<para>
- Since JMS coupling may be unwated in certain cases, RichFaces provides switch which turns off JMS integration:
+ Since JMS coupling may be unwanted in certain cases, RichFaces provides switch which turns off JMS integration:
</para>
<programlisting language="XML" role="XML"><xi:include parse="text" href="extras/exam-Component_Reference-a4jpush-Using_Push_without_JMS.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
@@ -728,15 +725,15 @@
<section id="sect-Component_Reference-a4jpush-Using_TopicsContext_to_publish_message">
<title>Using TopicsContext to publish message</title>
<para>
- Alternative way of producing messages is using RichFaces' <code>TopicsContext</code> interface directly as in following sample:
+ Alternative way of producing messages is using <code>TopicsContext</code> interface directly as in following sample:
</para>
<programlisting language="Java" role="JAVA"><xi:include parse="text" href="extras/exam-Component_Reference-a4jpush-Using_TopicsContext_to_publish_message.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
Sending message using <code>TopicsContext</code> involves creating <code>TopicKey</code> instance (denominator of given message topic) and looking up for <code>TopicsContext</code> used for topic registration and message publishing.
</para>
- <para>
- Note that for using <code>TopicsContext</code> is it necessary having <code>FacesContext</code> instance available in current thread.
- </para>
+ <important>
+ For using <code>TopicsContext</code> is it necessary having <code>FacesContext</code> instance available in current thread.
+ </important>
</section>
<section id="sect-Component_Reference-a4jpush-Push_CDI_Integration">
@@ -748,15 +745,15 @@
Push notifications can be produced by annotating CDI event with <code>@Push</code> annotation, which specifies end-point (topic name).
</para>
<para>
- Payload of the message is the serialized object sent with CDI event using <code>Event.fire(T object)</code>.
+ Payload of the message is the serialized object sent using CDI event interface (<code>Event.fire(T object)</code>).
</para>
<programlisting language="Java" role="JAVA"><xi:include parse="text" href="extras/exam-Component_Reference-a4jpush-Integrating_Push_with_CDI_events.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <para>
- Note that for using CDI events for producing push notifications, is it necessary having <code>FacesContext</code> instance available in current thread.
- </para>
- <para>
- Note that associations for CDI events and their handlers are constructed in application deployment. Therefore topics can't be dynamically associated using <code>Event.select(Annotation...)</code> @Push CDI qualifier.
- </para>
+ <important>
+ For using CDI events for producing push notifications, is it necessary having <code>FacesContext</code> instance available in current thread.
+ </important>
+ <note>
+ Associations for CDI events and their handlers are constructed in application deployment. Therefore topics can't be dynamically associated using <code>Event.select(Annotation...)</code> @Push CDI qualifier.
+ </note>
</section>
<section id="sect-Component_Reference-a4jpush-Reference_data">
Modified: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-a4jpush-Basic_usage.java
===================================================================
--- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-a4jpush-Basic_usage.java 2011-11-14 19:46:43 UTC (rev 22931)
+++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-a4jpush-Basic_usage.java 2011-11-14 20:24:01 UTC (rev 22932)
@@ -1,24 +1,8 @@
-public String getListSubtopic() {
- return this.getUserName() + SUBTOPIC_SEPARATOR + channelName + "List";
-}
+TopicSession session;
+TopicPublisher publisher;
-@Override
-protected void onUserList(String channel, User[] users) {
- try {
- getTopicsContext().publish(new TopicKey("chat", getListSubtopic()), null);
- } catch (MessageException e) {
- LOGGER.error(e.getMessage(), e);
- }
-}
-
-@Override
-protected void onJoin(String channel, String sender, String login, String hostname) {
- try {
- getTopicsContext().publish(new TopicKey("chat", getListSubtopic()), null);
- Message messageObject = new Message("joined channel", sender,
- DateFormat.getInstance().format(new Date()));
- getTopicsContext().publish(new TopicKey("chat", getMessagesSubtopic()), messageObject);
- } catch (MessageException e) {
- LOGGER.error(e.getMessage(), e);
- }
-}
+public void sendCurrentDate() throws JMSException {
+ String currentDate = new Date().toString();
+ ObjectMessage message = session.createObjectMessage(message);
+ publisher.publish(message);
+}
\ No newline at end of file
Modified: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-a4jpush-Basic_usage.xml_sample
===================================================================
--- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-a4jpush-Basic_usage.xml_sample 2011-11-14 19:46:43 UTC (rev 22931)
+++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-a4jpush-Basic_usage.xml_sample 2011-11-14 20:24:01 UTC (rev 22932)
@@ -1,8 +1,6 @@
-<rich:list value="#{chatBean.users}" var="user" id="users" type="unordered">
- #{user.nick}
-</rich:list>
-...
-<a4j:push address="#{chatBean.listSubtopic}@chat"
- onerror="alert(event.rf.data)">
- <a4j:ajax event="dataavailable" render="users" execute="@none" />
-</a4j:push>
+<a4j:push id="pushJms" address="pushJms"
+ ondataavailable="jQuery(#{rich:element('serverDate')}).text(event.rf.data)" />
+
+<a4j:outputPanel id="serverDate" layout="block">
+ <i>waiting for event...</i>
+</a4j:outputPanel>
\ No newline at end of file
12 years, 5 months
- 1
- 0
JBoss Rich Faces SVN: r22931 - in modules/docs/trunk/Component_Reference/src/main/docbook/en-US: extras and 1 other directory.
by richfaces-svn-commits＠lists.jboss.org
Author: lfryc(a)redhat.com
Date: 2011-11-14 14:46:43 -0500 (Mon, 14 Nov 2011)
New Revision: 22931
Added:
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richnotifyStack-Basic_usage.xml_sample
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richnotifyStack-Binding_by_stack_id.xml_sample
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richnotifyStack-Stacking_method_first.xml_sample
Modified:
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Output_and_messages.xml
Log:
RFPL-1580: finished rich:notify documentation
Modified: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Output_and_messages.xml
===================================================================
--- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Output_and_messages.xml 2011-11-14 18:45:44 UTC (rev 22930)
+++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Output_and_messages.xml 2011-11-14 19:46:43 UTC (rev 22931)
@@ -251,24 +251,30 @@
<section id="sect-Component_Reference-richnotify-Basic_usage">
<title>Basic usage</title>
<para>
- The <sgmltag><rich:notify></sgmltag> has two message customization attributes: <parameter>summary</parameter> is short text summarizing the message communicated with user, while <parameter>detail</parameter> configures detailed body of the message.
+ The <sgmltag><rich:notify></sgmltag> has two message customization attributes: <parameter>summary</parameter> is short text summarizing the message, while <parameter>detail</parameter> configures detailed body of the message.
</para>
<para>
- Both attributes have their counterparts in form of facets with same names as respective attributes.
+ Both attributes have their counterparts in form of facets with same names as attributes.
</para>
</section>
<section id="sect-Component_Reference-richnotify-Customizing_notifications">
<title>Customizing notifications</title>
<para>
- By default, notifications appears immediately after request which renders them in case of AJAX requests or once page is completely loaded in full-page request.
+ Notification appears on the page each them they are rendered, on full-page or ajax requests.
</para>
<para>
- They are waiting for 8 seconds and then they disappear. User can close notification with close button in the top-right corner of each notification.
+ Notifications are waiting on the screen for 8 seconds and then they disappear.
</para>
<para>
- But there are several attributes that can change default behavior:
+ Notification stacks and creates sequences. For customizition of stacking see <sgmltag><rich:notifyStack></sgmltag> component.
</para>
+ <para>
+ User can close notification with close button in the top-right corner of each notification.
+ </para>
+ <para>
+ There are several attributes that can change default behavior:
+ </para>
<itemizedlist>
<listitem>
<para>
@@ -287,12 +293,12 @@
</listitem>
<listitem>
<para>
- <parameter>nonblocking</parameter>: defines notifications which can't be closed manually, user needs to wait before they disappear, but once notification is hovered with mouse, it becomes partially transparent and user can click through
+ <parameter>nonblocking</parameter>: defines notifications which becomes partially transparent and user can click through. Non-blocking notifications don't have close button.
</para>
</listitem>
<listitem>
<para>
- <parameter>nonblockingOpacity</parameter>: defines opacity of nonblocking notifications when mouse hovers over notification
+ <parameter>nonblockingOpacity</parameter>: defines opacity of nonblocking notifications when mouse hovers over notification (decimal number between 0 and 1)
</para>
</listitem>
<listitem>
@@ -301,9 +307,9 @@
</para>
</listitem>
</itemizedlist>
- <para>
- Note that nonblocking notifications can be clicked through, but because they are using jQuery mechanism to bypass events, only jQuery event handlers are triggered. It specifically means that standard links won't be triggered.
- </para>
+ <note>
+ Nonblocking notifications can be clicked through, but because they are using jQuery mechanism to bypass events, only jQuery event handlers are triggered. It specifically means that standard links won't be triggered.
+ </note>
</section>
<section id="sect-Component_Reference-richnotify-Reference_data">
@@ -347,16 +353,16 @@
<section id="sect-Component_Reference-richnotifyMessage-Basic_usage">
<title>Basic usage</title>
<para>
- The <sgmltag><rich:notifyMessage></sgmltag> component is built on top of <sgmltag><rich:notify></sgmltag>, the difference is in usage of Faces messages system to define notifications.
+ The <sgmltag><rich:notifyMessage></sgmltag> component is built on top of <sgmltag><rich:notify></sgmltag>, the difference is in usage.
</para>
<para>
- Behavior does not differ from <sgmltag><rich:message></sgmltag>: one notification is displayed for first <code>FacesMessage</code> in stack, raisen either programatically or during component conversion/validation.
+ Component displays <code>FacesMessage</code>s associated with given component, similarry to <sgmltag><rich:message></sgmltag>: one notification is displayed for first <code>FacesMessage</code> in stack, raisen either programatically or during component conversion or validation.
</para>
<para>
- Notification icon and text color is determined by severity of message for which has been notification raised.
+ Severify of message which triggers notification determines color and icon of notification.
</para>
<para>
- For customization of notifications behavior refer to Customizing notifications.
+ For customization of notifications behavior refer to <link linkend="sect-Component_Reference-richnotify-Customizing_notifications">Customizing notifications</link> of <sgmltag><rich:notify></sgmltag>.
</para>
</section>
@@ -401,7 +407,7 @@
<section id="sect-Component_Reference-Output_and_messages-richnotifyMessages">
<title><sgmltag><rich:notifyMessages></sgmltag></title>
<para>
- The <sgmltag><rich:notifyMessages></sgmltag> component is same as <sgmltag><rich:notifyMessage></sgmltag>, but all available messages are displayed instead of the first one only.
+ The <sgmltag><rich:notifyMessages></sgmltag> component is same as <sgmltag><rich:notifyMessage></sgmltag>, but each of available messages generates one notification.
</para>
<para>
<sgmltag><rich:notifyMessages></sgmltag> shares the same set of attributes with <sgmltag><rich:notifyMessage></sgmltag>
@@ -409,7 +415,7 @@
<figure id="figu-Component_Reference-richnotifyMessages-richnotifyMessages">
<mediaobject>
<imageobject>
- <imagedata fileref="images/figu-Component_Reference-richnotifyMessages-richnotifyMessages.png" width="300" height="222" format="PNG" />
+ <imagedata fileref="images/figu-Component_Reference-richnotifyMessages-richnotifyMessages.png" width="200" format="PNG" />
</imageobject>
<textobject>
<para>
@@ -462,7 +468,7 @@
It is <sgmltag><rich:notifyStack></sgmltag> which defines where messages will appear and handles their stacking.
</para>
<para>
- Stack does also provide way how to remove messages from screen - when stack is re-rendered, current notifications are destroyed, freeing place for new notifications.
+ Stack also provides way how to remove messages from screen - when stack is re-rendered, current notifications are destroyed, freeing place for new notifications.
</para>
<section id="sect-Component_Reference-richnotifyStack-Basic_usage">
@@ -473,12 +479,12 @@
<itemizedlist>
<listitem>
<para>
- <emphasis>wrapping</emphasis>: nesting component bounds notifications with stack which is wrapping them
+ <emphasis>wrapping</emphasis>: nesting <sgmltag><rich:notify></sgmltag>, <sgmltag><rich:notifyMessage></sgmltag> or <sgmltag><rich:notifyMessages></sgmltag> bounds notifications with stack which is wrapping them
</para>
</listitem>
<listitem>
<para>
- <emphasis>binding by id</emphasis>: notification can be bound directly to stack using it's <code>componentId</code> and attribute <parameter>stack</parameter> attribute of notification
+ <emphasis>binding by id</emphasis>: notification can be bound directly to stack using it's <code>componentId</code> in attribute <parameter>stack</parameter>
</para>
</listitem>
<listitem>
@@ -487,26 +493,14 @@
</para>
</listitem>
</itemizedlist>
- <programlisting language="XML" role="XML">
- <![CDATA[
-<rich:notifyStack position="bottomRight">
- <rich:notifyMessages />
-</rich:notifyStack>
- ]]>
- </programlisting>
+ <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/exam-Component_Reference-richnotifyStack-Basic_usage.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
- Sample above defines stack explicitly, where notifications uses wrapping stack.
+ The sample above defines stack explicitly, where notifications uses stack in that they are wrapped.
</para>
<para>
- Following sample uses notification, which is rendered into top-left screen corner. Notification is bound to stack using <code>componentId</code>.
+ The sample bellow uses notification, which is rendered into top-left screen corner. Notification is bound to stack using its id.
</para>
- <programlisting language="XML" role="XML">
- <![CDATA[
-<rich:notifyStack id="leftStack" position="topLeft" />
-
-<rich:notify stack="leftStack" />
- ]]>
- </programlisting>
+ <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/exam-Component_Reference-richnotifyStack-Binding_by_stack_id.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
</section>
<section id="sect-Component_Reference-richnotifyStack-Positioning_notifications">
@@ -524,9 +518,6 @@
<para>
There are two attributes which influences how notifications are placed into stack:
</para>
- <para>
- <sgmltag><rich:notifyStack></sgmltag> uses <parameter>position</parameter> attribute which places stack and its notifications into one of four corners: <code>topRight</code> (default), <code>bottomRight</code>, <code>bottomLeft</code>, <code>topLeft</code>.
- </para>
<itemizedlist>
<listitem>
<para>
@@ -540,11 +531,7 @@
<para>
Following sample shows stack which will place new notification as first - incoming message will appear first, causing all notifications currently in stack to shift. Adequately, messages on the end of stack will be then removed from stack as first.
</para>
- <programlisting language="XML" role="XML">
- <![CDATA[
-<rich:notifyStack method="first" />
- ]]>
- </programlisting>
+ <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/exam-Component_Reference-richnotifyStack-Stacking_method_first.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
On the other hand, stacking method <code>last</code> does provide method to place messages on the end of stack, and when removing notification, it is removed from start, causing all other notifications to shift.
</para>
Added: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richnotifyStack-Basic_usage.xml_sample
===================================================================
--- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richnotifyStack-Basic_usage.xml_sample (rev 0)
+++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richnotifyStack-Basic_usage.xml_sample 2011-11-14 19:46:43 UTC (rev 22931)
@@ -0,0 +1,3 @@
+<rich:notifyStack position="bottomRight">
+ <rich:notifyMessages />
+</rich:notifyStack>
\ No newline at end of file
Added: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richnotifyStack-Binding_by_stack_id.xml_sample
===================================================================
--- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richnotifyStack-Binding_by_stack_id.xml_sample (rev 0)
+++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richnotifyStack-Binding_by_stack_id.xml_sample 2011-11-14 19:46:43 UTC (rev 22931)
@@ -0,0 +1,3 @@
+<rich:notifyStack id="leftStack" position="topLeft" />
+
+<rich:notify stack="leftStack" />
\ No newline at end of file
Added: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richnotifyStack-Stacking_method_first.xml_sample
===================================================================
--- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richnotifyStack-Stacking_method_first.xml_sample (rev 0)
+++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richnotifyStack-Stacking_method_first.xml_sample 2011-11-14 19:46:43 UTC (rev 22931)
@@ -0,0 +1 @@
+<rich:notifyStack method="first" />
\ No newline at end of file
12 years, 5 months
- 1
- 0
JBoss Rich Faces SVN: r22930 - modules/docs/trunk/Developer_Guide/src/main/docbook/en-US.
by richfaces-svn-commits＠lists.jboss.org
Author: lfryc(a)redhat.com
Date: 2011-11-14 13:45:44 -0500 (Mon, 14 Nov 2011)
New Revision: 22930
Modified:
modules/docs/trunk/Developer_Guide/src/main/docbook/en-US/chap-Developer_Guide-Advanced_features.xml
Log:
RFPL-1702: finished documentation for resource mapping and resource loading strategies
Modified: modules/docs/trunk/Developer_Guide/src/main/docbook/en-US/chap-Developer_Guide-Advanced_features.xml
===================================================================
--- modules/docs/trunk/Developer_Guide/src/main/docbook/en-US/chap-Developer_Guide-Advanced_features.xml 2011-11-14 18:45:24 UTC (rev 22929)
+++ modules/docs/trunk/Developer_Guide/src/main/docbook/en-US/chap-Developer_Guide-Advanced_features.xml 2011-11-14 18:45:44 UTC (rev 22930)
@@ -277,8 +277,8 @@
Resources which RichFaces uses in components, like style sheets, JavaScript code or images are handled by standard JSF resource handling.
</para>
<para>
- However JSF resource handling feature falls short when using static resources which refers to each other (style sheets refering to images, JavaScript refering to style sheets).
- These resources does not know about Faces servlet mapping and thus it cannot be referenced by JSF resource handling feature.
+ However JSF resource handling feature falls short when using static resources which refers to another resources (style sheets refering to images, JavaScript refering to style sheets).
+ These resources doesn't carry informations necessary to address JSF resources (servlet context path, servlet mapping, library name).
</para>
<para>
RichFaces provides <sgmltag>ResourceServlet</sgmltag> which handles framework static resources:
@@ -302,18 +302,18 @@
<sgmltag>ResourceServlet</sgmltag> is automatically registered in Servlet 3.0 and higher environments.
</para>
<para>
- In Servlet 2.5 environment, it is necessary to register <sgmltag>ResourceServlet</sgmltag> manually in <sgmltag>WEB-INF/web.xml</sgmltag> configuration file:
+ In Servlet 2.5 and lower environments, it is necessary to register <sgmltag>ResourceServlet</sgmltag> manually in <sgmltag>WEB-INF/web.xml</sgmltag> configuration file:
</para>
<programlisting language="XML" role="XML"><xi:include parse="text" href="extras/prog-Developer_Guide-Advanced_features-Configuring_ResourceServlet.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
- This servlet is strictly limited in what can be processed to the RichFaces resource libraries only.
+ This servlet is strictly limited in what it can process to the RichFaces resource libraries only.
</para>
</section>
<section id="sect-Developer_Guide-Advanced_features-Resource_mapping">
<title>Resource mapping</title>
<para>
- RichFaces resources are determined by notion of resource libraries and load by standard JSF resource handling mechanism.
+ RichFaces resources are determined by notion of resource libraries and loaded by standard JSF resource handling mechanism.
</para>
<para>
There are situations where it may be favourable to use alternative resource location:
@@ -321,66 +321,108 @@
<itemizedlist>
<listitem>
<para>
- loading modified resource (either patched version, alternative version, compressed resource)
+ loading pre-processed resources (packed or compressed resource)
</para>
</listitem>
<listitem>
<para>
- loading resource from external location (HTTP server, Content Delivery Network)
+ loading modified resource (patched or alternative resource)
</para>
</listitem>
+ <listitem>
+ <para>
+ loading resource from external location (static HTTP server, Content Delivery Network)
+ </para>
+ </listitem>
</itemizedlist>
<section id="sect-Developer_Guide-Advanced_features-Configuring_resource_mapping">
<title>Configuring resource mapping</title>
<para>
- Resource mapping feature is in default state disabled. You can enable it with contextual parameter <code>org.richfaces.resourceMapping.enabled</code>.
+ Resource mapping feature is in default state disabled. You can enable it with contextual parameter <code>org.richfaces.resourceMapping.enabled</code> with value <code>true</code>.
</para>
<para>
- Resource mapping consist of properties file with records in format:
+ Resource mapping is controlled by two configurations:
</para>
- <programlisting>resourceLibrary:resourceName=resourceLocation</programlisting>
+ <itemizedlist>
+ <listitem>
+ <para>
+ mapped resources location
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ resource mapping configuration file
+ </para>
+ </listitem>
+ </itemizedlist>
<para>
- It is possible to define custom resource mapping configuration file using contextual parameter identifying class-path location where file resides: <code>org.richfaces.resourceMapping.mappingFile</code>
+ While mapped resources location determines the base URL from which all resource locations are derived, resource mapping file contains resource-specific locations.
</para>
- <para>
- Location of resources is determined by resource location root and <code>resourceLocation</code> configured in file.
- Since <code>resourceLocation</code> can point to external locations, you can point it to completely other server, these locations are determined
- In other cases resource location root can be configured using contextual parameter <code>org.richfaces.resourceMapping.location</code> and it can contain EL expressions.
- </para>
- <para>
- By default, resource mapping file and location root are determined by current resource loading strategy.
- </para>
- <para>
- Following sample shows usage of <code>web.xml</code> and <code>META-INF/custom-mapping.properties</code> configurations:
- </para>
- <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/prog-Developer_Guide-Advanced_features-Configuring_resource_mapping_web_xml.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <para>
- First <code>context-param</code> is enabling resource mapping. Both other context-params are configuring the behavior.
- </para>
- <para>
- Second <code>context-param</code> instructs RichFaces to look for <code>META-INF/custom-mapping.properties</code> file on class-path (either in your WAR: <code>WEB-INF/classes/META-INF/custom-mapping.properties</code> or any JAR on class-path in <code>META-INF/custom-mapping.properties</code>).
- </para>
- <para>
- Last <code>context-param</code> configures the root resource location and uses expressions <code>#{facesContext.externalContext.requestContextPath}</code> to retrieve context path and <code>#{resourceLocation}</code> to retrieve location of specific resource (as provided from resource mapping configuration file).
- </para>
- <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/prog-Developer_Guide-Advanced_features-Configuring_resource_mapping_custom_mappping_properties.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <para>
- First property in the <code>META-INF/custom-mapping.properties</code> specifies resource mapping for resource with qualifier <code>javax.faces:jsf.js</code> which stands for Java Server Faces 2.0 JavaScript implementation. It instructs resource handler to look for <code>patched-jsf.js</code> source file.
- Using the resource location root, it will specifically look for <code>#{facesContext.externalContext.requestContextPath}/resources/com.acme/patched-jsf.js</code>
- </para>
- <para>
- Second property defines mapping for <code>jquery.js</code> resource. This line instructs resource handler to locate this resource on external URL, specifically from CDN.
- </para>
- <para>
- Note that several resources can point to one location, which will in turn cause browser to load only one resource which should contain all resources.
- </para>
</section>
+
+ <section>
+ <title>Mapped resources location</title>
+ <para>
+ Absolute resource location is determined from base URL, which is string that contains EL expression <code>#{resourceLocation}</code>.
+ </para>
+ <para>
+ This base URL can be configured using contextual parameter <code>org.richfaces.resourceMapping.location</code>.
+ </para>
+ <note>
+ Several resources can point to one location, which will in turn cause browser to load only one resource. That can be radical performance improvement, because client will need only one resource request per several resources. The aggregated resource needs to be properly formatted.
+ </note>
+ </section>
+
+ <section>
+ <title>Resource mapping configuration file</title>
+ <para>
+ Resource mapping configuration is properties file with records in format:
+ </para>
+ <programlisting>resourceLibrary:resourceName=resourceLocation</programlisting>
+ <para>
+ It is possible to define custom resource mapping configuration file using contextual parameter identifying class-path location where file resides: <code>org.richfaces.resourceMapping.mappingFile</code>
+ </para>
+ <para>
+ The <code>resourceLocation</code> can be absolute resource URL, allowing to relocate selected resources to another server.
+ </para>
+ </section>
+
+ <example>
+ <title>Example of resource mapping web.xml configuration</title>
+
+ <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/prog-Developer_Guide-Advanced_features-Configuring_resource_mapping_web_xml.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ <para>
+ First <code>context-param</code> is enabling resource mapping. Both other context-params are configuring the behavior.
+ </para>
+ <para>
+ Second <code>context-param</code> instructs RichFaces to look for <code>META-INF/custom-mapping.properties</code> file on class-path (either in your WAR: <code>WEB-INF/classes/META-INF/custom-mapping.properties</code> or any JAR on class-path in <code>META-INF/custom-mapping.properties</code>).
+ </para>
+ <para>
+ Last <code>context-param</code> configures the root resource location and uses expressions <code>#{facesContext.externalContext.requestContextPath}</code> to retrieve context path and <code>#{resourceLocation}</code> to retrieve location of specific resource (as provided from resource mapping configuration file).
+ </para>
+ </example>
+ <example>
+ <title>Example of resource mapping configuration file</title>
+ <para>
+ The contents of <code>META-INF/custom-mapping.properties</code> file:
+ </para>
+ <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/prog-Developer_Guide-Advanced_features-Configuring_resource_mapping_custom_mappping_properties.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ <para>
+ First property in the <code>META-INF/custom-mapping.properties</code> specifies resource mapping for resource with qualifier <code>javax.faces:jsf.js</code> which stands for Java Server Faces 2.0 JavaScript implementation. It instructs resource handler to look for <code>patched-jsf.js</code> source file (in this sample located on WAR relative location <code>resources/com.acme/patched-jsf.js</code>).
+ </para>
+ <para>
+ Using the resource location root, it will specifically look for <code>#{facesContext.externalContext.requestContextPath}/resources/com.acme/patched-jsf.js</code>
+ </para>
+ <para>
+ Second property defines mapping for <code>jquery.js</code> resource. This line instructs resource handler to locate this resource on external URL, specifically from CDN.
+ </para>
+ </example>
</section>
<section id="sect-Developer_Guide-Advanced_features-Resource_loading_strategies">
<title>Resource loading strategies</title>
<para>
- Resource loading strategies are special configuration of resource mapping suitable in lot of cases.
+ Resource loading strategies are special configuration of resource mapping.
</para>
<para>
RichFaces framework bundles static versions of all components' resources which are processed to optimize performance in certain scenarios:
@@ -405,41 +447,55 @@
<para>
Previous features aren't configured directly, it is necessary to choose project stages in which given feature will be applied.
</para>
- <para>
- It is necessary to choose stages, where compression is applied and where packed resource will be used. If both compression and packing are disable, simple static resources will be served.
- </para>
+ <note>
+ <para>
+ Resource mapping needs to be enabled for using resource loading strategies.
+ </para>
+ </note>
+
<section id="sect-Developer_Guide-Advanced_features-Configuring_resource_loading_strategies">
<title>Configuring resource loading strategies</title>
<para>
- It is possible to provide following options for project stages: <code>None, Development, UnitTest, SystemTest, Production, All</code>.
+ It is necessary to choose stages, where compression is applied and where packed resource will be used. If both compression and packing are disabled, simple static resources will be served.
</para>
<para>
- For configuration, you can use any combination of project stages (separated by commas) or keywords None (for feature turned off in all stages) or All (for feature turned off in all stages).
+ It is possible to provide following options for project stages: <code>Development, UnitTest, SystemTest, Production</code> or keywords <code>None</code> and <code>All</code>.
</para>
<para>
+ For configuration, you can use any combination of project stages (separated by commas) or keywords <code>None</code> (for feature turned off in all stages) or <code>All</code> (for feature turned off in all stages).
+ </para>
+ <para>
Compression is configured in <code>web.xml</code> using <code>context-param</code> <code>org.richfaces.resourceMapping.compressedStages</code>.
- Compression is set to <code>Production,SystemTest</code>, enabling this feature for production and system testing.
+ Compression is by default set to <code>Production,SystemTest</code>, enabling this feature for production and system testing.
</para>
<para>
Packing is configured in <code>web.xml</code> using <code>context-param</code> <code>org.richfaces.resourceMapping.packedStages</code>.
- Packing is set to <code>All</code>, enabling this feature in all stages.
+ Packing is by default set to <code>All</code>, enabling this feature in all stages.
</para>
- <para>
- It specifically means that with resource mapping enabled, packed resources are served and compression is turned off in development and unit tests and turned on in production and for system tests.
- </para>
- <para>
- Following sample turns off packing, so only compression will be applied.
- </para>
- <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/prog-Developer_Guide-Advanced_features-Configuring_resource_loading_strategies.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
- <para>
- Notice that resource mapping needs to be enabled for serving static resources
- </para>
- <para>
- For serving static resources, you will need to turn off both compression and packing.
- </para>
- <para>
- Note that resource loading strategies are just special case of resource mapping, thus once you will provide custom resource mapping configuration or location, bundled default resources won't be referenced correctly. For using compressed/packed resources you will need to copy properties from one of files located in <code>richfaces-components-ui.jar:/META-INF/richfaces/staticResourceMapping/</code>.
- </para>
+ <note>
+ <para>
+ It specifically means that with resource mapping enabled, packed resources are served and compression is turned off in development and unit tests and turned on in production and for system tests.
+ </para>
+ <para>
+ For serving static versions of regular resources, you will need to turn off both compression and packing.
+ </para>
+ </note>
+ <example>
+ <title>Resource loading strategies configuration</title>
+ <para>
+ Following sample turns off packing in all stages, so only compression will be applied.
+ </para>
+ <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/prog-Developer_Guide-Advanced_features-Configuring_resource_loading_strategies.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ </example>
+ <important>
+ <title>Custom resource mapping and Resource loading strategies</title>
+ <para>
+ Resource loading strategies are just special case of resource mapping, thus once you will provide custom resource mapping configuration or location, bundled default resources won't be referenced correctly.
+ </para>
+ <para>
+ For using compressed/packed resources you will need to copy properties from one of files located in <code>richfaces-components-ui.jar:/META-INF/richfaces/staticResourceMapping/</code>.
+ </para>
+ </important>
</section>
</section>
</section>
12 years, 5 months
- 1
- 0
JBoss Rich Faces SVN: r22929 - in modules/docs/trunk/Component_Reference/src/main/docbook/en-US: extras and 1 other directories.
by richfaces-svn-commits＠lists.jboss.org
Author: lfryc(a)redhat.com
Date: 2011-11-14 13:45:24 -0500 (Mon, 14 Nov 2011)
New Revision: 22929
Added:
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Advanced_configuration.xml_sample
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Basic_usage.xml_sample
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Client_side_event_handlers.xml_sample
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Internationalization_and_localization.xml_sample
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Toolbar_customization.xml_sample
Modified:
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Rich_inputs.xml
modules/docs/trunk/Component_Reference/src/main/docbook/en-US/skinning/tabl-richeditor.xml
Log:
RFPL-1574: finished rich:editor documentation
Modified: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Rich_inputs.xml
===================================================================
--- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Rich_inputs.xml 2011-11-14 13:56:40 UTC (rev 22928)
+++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/chap-Component_Reference-Rich_inputs.xml 2011-11-14 18:45:24 UTC (rev 22929)
@@ -804,7 +804,7 @@
<title><sgmltag><rich:editor></sgmltag></title>
<mediaobject>
<imageobject>
- <imagedata fileref="images/figu-Component_Reference-richeditor-richeditor.png" format="PNG" />
+ <imagedata fileref="images/figu-Component_Reference-richeditor-richeditor.png" width="400" format="PNG" />
</imageobject>
<textobject>
<para>
@@ -817,34 +817,36 @@
<sgmltag><rich:editor></sgmltag> component is based on CKEditor implementation.
</para>
<para>
- When rendering <sgmltag><rich:editor></sgmltag>, textarea is rendered to the page and once the page is completely loaded (ready state), textarea is enhanced by CKEditor script and replaced with full-featured WYSIWYG editor.
+ When rendering <sgmltag><rich:editor></sgmltag>, textarea is rendered to the page and once the page is completely loaded (ready state), textarea is enhanced using CKEditor script and replaced with full-featured WYSIWYG editor.
</para>
- <para>
- Note that ResourceServlet has to be registered manually in order to serve editor resources correctly (JavaScript, CSS, images). Check RichFaces Developer's Guide out for details.
- </para>
- <para>
- Note that <sgmltag><rich:editor></sgmltag> requires having <sgmltag><h:body></sgmltag> component as ancestor in the view for rendering editor's JavaScript resource dependencies correctly.
- </para>
<section id="sect-Component_Reference-richeditor-Basic_usage">
<title>Basic usage</title>
<para>
Basic usage requires the <varname>value</varname> attribute to point to the expression for the current value of the component.
</para>
- <programlisting language="XML" role="XML">
- <![CDATA[
-<rich:editor value="#{backingBean.editedValue}" />
- ]]>
- </programlisting>
+ <example>
+ <title>Basic usage of <sgmltag><rich:editor></sgmltag></title>
+ <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/exam-Component_Reference-richeditor-Basic_usage.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
+ <para>
+ Note that editor does produce HTML markup and to be able render it's output, markup needs to be output as unescaped (as with <sgmltag><h:outputText></sgmltag> component in example above).
+ </para>
+ </example>
<para>
Dimensions of editor can be managed using <parameter>width</parameter> and <parameter>height</parameter> attributes.
</para>
<para>
- Attribute <parameter>readonly</parameter> can be used to switch editor into read-only mode.
+ The <parameter>readonly</parameter> attribute can be used to switch editor into read-only mode.
</para>
<para>
- <parameter>tabindex</parameter> is used as for any other form inputs.
+ The <parameter>tabindex</parameter> attribute specifies the position of the current element in the tabbing order for the current document.
</para>
+ <note>
+ <code>ResourceServlet</code> has to be registered for <code>url-pattern</code> <code>/org.richfaces.resources/*</code> in order to serve editor resources (JavaScript, CSS, images) correctly. Check <emphasis>RichFaces Developer's Guide</emphasis> out for details.
+ </note>
+ <note>
+ The <sgmltag><rich:editor></sgmltag> requires having <sgmltag><h:body></sgmltag> component present in the view and being its ancestor for rendering resource dependencies correctly.
+ </note>
</section>
<section id="sect-Component_Reference-richeditor-Styling">
@@ -860,7 +862,7 @@
</listitem>
<listitem>
<para>
- <parameter>editorStyle, editorClass</parameter>: customizes style of the editor
+ <parameter>editorStyle, editorClass</parameter>: customizes style of the CKEditor instance
</para>
</listitem>
<listitem>
@@ -869,46 +871,55 @@
</para>
</listitem>
</itemizedlist>
- <para>
- Attributes above gives possibility to customize style of both, editor and underlying textarea.
- </para>
</section>
<section id="sect-Component_Reference-richeditor-Editor_skins">
<title>Editor skins</title>
<para>
- <sgmltag><rich:editor></sgmltag> comes with two axis of skinnability.
+ The <sgmltag><rich:editor></sgmltag> comes with skinnability using attribute <code>skin</code> and two approaches:
</para>
<para>
- At first, standard skin called <code>richfaces</code> is optimized to suit rest of the component suite look & feel and behaves regarding to which RichFaces skin is currently chosen.
+ At first, <sgmltag><rich:editor></sgmltag> has default skin called <code>richfaces</code> that is optimized to suit rest of the component suite look & feel and behaves regarding to which RichFaces skin is currently chosen (refer to <emphasis>RichFaces Developer's Guide</emphasis> for details about <emphasis>Skinning and theming</emphasis>).
</para>
- <figure id="figu-Component_Reference-richeditor-richfaces_skin">
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/figu-Component_Reference-richeditor-richfaces_skin.png" format="PNG" />
- </imageobject>
- <textobject>
- <para>
- A <sgmltag><rich:editor></sgmltag> with default <code>richfaces</code> editor skin rendered against several RichFaces Skin options.
- </para>
- </textobject>
- </mediaobject>
- </figure>
+ <example>
+ <title>The skin <code>richfaces</code> of <sgmltag><rich:editor></sgmltag></title>
+ <figure id="figu-Component_Reference-richeditor-richfaces_skin">
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/figu-Component_Reference-richeditor-richfaces_skin.png" width="400" format="PNG" />
+ </imageobject>
+ <textobject>
+ <para>
+ A <sgmltag><rich:editor></sgmltag> with default <code>richfaces</code> editor skin rendered against several RichFaces Skin options.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
+ <para>
+ A <sgmltag><rich:editor></sgmltag> with default <code>richfaces</code> editor skin rendered against several RichFaces Skin options.
+ </para>
+ </example>
<para>
Second option gives you possibility to use any other skin for CKEditor, either from standard distribution or downloaded one or custom one. In distribution, there are three skins bundled: <code>kama, v2, office2003</code>.
</para>
- <figure id="figu-Component_Reference-richeditor-distribution_skins">
- <mediaobject>
- <imageobject>
- <imagedata fileref="images/figu-Component_Reference-richeditor-distribution_skins.png" format="PNG" />
- </imageobject>
- <textobject>
- <para>
- A CKEditor distribution skins <code>kama</code>, <code>v2</code> and <code>office2003</code>.
- </para>
- </textobject>
- </mediaobject>
- </figure>
+ <example>
+ <title>Examples of <sgmltag><rich:editor></sgmltag> skins in CKEditor distribution</title>
+ <figure id="figu-Component_Reference-richeditor-distribution_skins">
+ <mediaobject>
+ <imageobject>
+ <imagedata fileref="images/figu-Component_Reference-richeditor-distribution_skins.png" width="400" format="PNG" />
+ </imageobject>
+ <textobject>
+ <para>
+ A CKEditor distribution skins <code>kama</code>, <code>v2</code> and <code>office2003</code>.
+ </para>
+ </textobject>
+ </mediaobject>
+ </figure>
+ <para>
+ A CKEditor distribution skins <code>kama</code>, <code>v2</code> and <code>office2003</code>.
+ </para>
+ </example>
</section>
<section id="sect-Component_Reference-richeditor-Advanced_configuration">
@@ -917,69 +928,38 @@
Basic set of <sgmltag><rich:editor></sgmltag> attributes allows to support common use-cases for WYSIWYG editor.
</para>
<para>
- CKEditor imlementation supports much more configuration options that the ones which are exposed to basic set of attributes.
+ However CKEditor imlementation supports much more configuration options.
</para>
<para>
Attribute <parameter>config</parameter> gives possibility to define any advanced configuration option which CKEditor supports.
</para>
<para>
- Configuration is written in JavaScript object format and its value interpolated for EL expressions (making configuration dynamic).
+ Configuration is written in JavaScript object format and its value is interpolated for EL expressions (making configuration dynamic).
</para>
<para>
- There are two options to define configuration: <parameter>config</parameter> attribute and component facet with name <parameter>config</parameter>. Facet takes precedence over attribute when both defined.
+ There are two options to define configuration: <parameter>config</parameter> attribute and facet with name <parameter>config</parameter>. Facet takes precedence over attribute when both defined.
</para>
- <programlisting language="XML" role="XML">
- <![CDATA[
-<rich:editor config="startupFocus: #{userPreferences.startupFocus}" />
-
-<rich:editor>
- <f:facet name="config">
- startupFocus: #{userPreferences.startupFocus}
- </f:facet>
-</rich:editor>
- ]]>
- </programlisting>
+ <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/exam-Component_Reference-richeditor-Advanced_configuration.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
In samples above, <sgmltag><rich:editor></sgmltag> is configured to take focus after load of the page regarding to user preferences. Definitions using either attribute or facet are adequate.
</para>
- <para>
- For further configuration options, refer to CKEditor 3 Developer Guide ( http://docs.cksource.com/CKEditor_3.x/Developers_Guide/Setting_Configurat... ) and CKEditor 3 configuration reference ( http://docs.cksource.com/ckeditor_api/symbols/CKEDITOR.config.html ).
- </para>
+ <note>
+ For further configuration options, refer to <ulink url="http://docs.cksource.com/CKEditor_3.x/Developers_Guide/Setting_Configurat...">CKEditor 3 Developer Guide</ulink> and <ulink url="http://docs.cksource.com/ckeditor_api/symbols/CKEDITOR.config.html">CKEditor 3 configuration reference</ulink>.
+ </note>
</section>
<section id="sect-Component_Reference-richeditor-Toolbar_customization">
<title>Toolbar customization</title>
<para>
- <sgmltag><rich:editor></sgmltag> supports <parameter>toolbar</parameter> attribute able to switch between toolbar configurations.
+ <sgmltag><rich:editor></sgmltag> supports <parameter>toolbar</parameter> attribute able to switch between configurations of toolbar's button set.
</para>
<para>
- There are two configurations available: <code>basic</code> (default), <code>full</code>.
+ There are two configurations available: <code>basic</code> (default), <code>full</code> (enables all of the features).
</para>
<para>
- It is possible to define custom toolbar using CKEditor toolbar definition notion:
+ It is possible to define custom toolbar using CKEditor toolbar configuration in <code>config</code> facet:
</para>
- <programlisting language="XML" role="XML">
- <![CDATA[
-<rich:editor toolbar="CustomToolbar">
- <f:facet name="config">
- toolbar_CustomToolbar:
- [
- { name: 'document', items : [ 'NewPage','Preview' ] },
- { name: 'clipboard', items : [ 'Cut','Copy','Paste','PasteText','PasteFromWord','-','Undo','Redo' ] },
- { name: 'editing', items : [ 'Find','Replace','-','SelectAll','-','Scayt' ] },
- { name: 'insert', items : [ 'Image','Flash','Table','HorizontalRule','Smiley','SpecialChar','PageBreak'
- ,'Iframe' ] },
- '/',
- { name: 'styles', items : [ 'Styles','Format' ] },
- { name: 'basicstyles', items : [ 'Bold','Italic','Strike','-','RemoveFormat' ] },
- { name: 'paragraph', items : [ 'NumberedList','BulletedList','-','Outdent','Indent','-','Blockquote' ] },
- { name: 'links', items : [ 'Link','Unlink','Anchor' ] },
- { name: 'tools', items : [ 'Maximize' ] }
- ]
- </f:facet>
-</rich:editor>
- ]]>
- </programlisting>
+ <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/exam-Component_Reference-richeditor-Toolbar_customization.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
Note that toolbar name (<code>CustomToolbar</code>) needs to match the <code>toolbar_<name></code> configuration option.
</para>
@@ -991,25 +971,25 @@
<sgmltag><rich:editor></sgmltag> comes with attribute <parameter>lang</parameter> which allows to change localization of editor.
</para>
<para>
- For language configuration options, refer to http://www.w3.org/TR/html4/struct/dirlang.html.
+ For language configuration options, refer to <ulink url="http://www.w3.org/TR/html4/struct/dirlang.html">http://www.w3.org/TR/html4/struct/dirlang.html</ulink>.
</para>
<para>
- <parameter>lang</parameter> attribute is influences following settings:
+ The <parameter>lang</parameter> attribute influences following settings:
</para>
<itemizedlist>
<listitem>
<para>
- underlying textarea - specifies the i18n settings for received and submitted content
+ <emphasis>underlying textarea</emphasis> - specifies the i18n settings for received and submitted content
</para>
</listitem>
<listitem>
<para>
- editor value - specifies the i18n settings for value edited in WYSIWYG mode
+ <emphasis>editor value</emphasis> - specifies the i18n settings for value edited in WYSIWYG mode
</para>
</listitem>
<listitem>
<para>
- default settings of localization of editor controls and interface
+ <emphasis>default settings of localization</emphasis> of editor controls and interface
</para>
</listitem>
</itemizedlist>
@@ -1017,13 +997,9 @@
However localization of interface is in first place localized using the browser configuration (usually determined by client system settings).
</para>
<para>
- To force editor to use specific localization of interface, you can use custom CKEditor configuration option <code>language</code> as in following sample:
+ To force editor to use specific localization of interface, you can use advanced CKEditor configuration option <code>language</code> as in following sample:
</para>
- <programlisting language="XML" role="XML">
- <![CDATA[
-<rich:editor lang="fr" config="language: 'fr'" />
- ]]>
- </programlisting>
+ <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/exam-Component_Reference-richeditor-Internationalization_and_localization.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
The sample above force editor to use french interface, supressing the browser preferred settings.
</para>
@@ -1032,7 +1008,7 @@
<section id="sect-Component_Reference-richeditor-Client_side_event_handlers">
<title>Client-side event handlers</title>
<para>
- <sgmltag><rich:editor></sgmltag> component produces set of events for handling component specific interaction.
+ The <sgmltag><rich:editor></sgmltag> component produces set of events for handling component specific interaction.
</para>
<itemizedlist>
<listitem>
@@ -1064,20 +1040,7 @@
<para>
Events can be handled either by registering JavaScript event handler or by attaching JSF behavior:
</para>
- <programlisting language="XML" role="XML">
- <![CDATA[
-<rich:editor value="#{backingBean.editorValue}">
- <a4j:ajax event="change" render="editorOutput" />
- <a4j:ajax event="dirty" render="editorOutput">
- <a4j:attachQueue requestDelay="1000" />
- </a4j:ajax>
-</rich:editor>
-
-<a4j:outputPanel id="editorOutput">
- <h:outputText escape="false" value="#{backingBean.editorValue}" />
-</a4j:outputPanel>
- ]]>
- </programlisting>
+ <programlisting language="XML" role="XML"><xi:include parse="text" href="extras/exam-Component_Reference-richeditor-Client_side_event_handlers.xml_sample" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting>
<para>
Example above shows editor and its output, which is updated each 1 sec after each instant change or immediately after user focus leaves editor area.
</para>
@@ -1109,7 +1072,7 @@
<term><function>getEditor()</function></term>
<listitem>
<para>
- Returns the CKEditor object associated to given instance of <sgmltag><rich:editor></sgmltag> component.
+ Returns the CKEditor object instance associated to given <sgmltag><rich:editor></sgmltag> component.
</para>
</listitem>
</varlistentry>
@@ -1117,7 +1080,7 @@
<term><function>getInput()</function></term>
<listitem>
<para>
- Returns the textarea associated textarea.
+ Returns the associated textarea.
</para>
</listitem>
</varlistentry>
@@ -1149,7 +1112,7 @@
<term><function>isDirty()</function></term>
<listitem>
<para>
- Returns <literal>true</literal> if editor is focused and it was edited from last focus event (reset by blur event and using setValue(newValue) call and when component re-rendered)
+ Returns <literal>true</literal> if editor is focused and it was edited from last focus event (reset by blur event, by using <code>setValue(newValue)</code> call and when component is re-rendered)
</para>
</listitem>
</varlistentry>
@@ -1157,7 +1120,7 @@
<term><function>isValueChanged()</function></term>
<listitem>
<para>
- Returns <literal>true</literal> if the control's value has been changed from the default (reset by setValue(newValue) call and when component re-rendered)
+ Returns <literal>true</literal> if the control's value has been changed from the default (reset by <code>setValue(newValue)</code> call and when component is re-rendered)
</para>
</listitem>
</varlistentry>
Added: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Advanced_configuration.xml_sample
===================================================================
--- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Advanced_configuration.xml_sample (rev 0)
+++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Advanced_configuration.xml_sample 2011-11-14 18:45:24 UTC (rev 22929)
@@ -0,0 +1,7 @@
+<rich:editor config="startupFocus: #{userPreferences.startupFocus}" />
+
+<rich:editor>
+ <f:facet name="config">
+ startupFocus: #{userPreferences.startupFocus}
+ </f:facet>
+</rich:editor>
\ No newline at end of file
Added: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Basic_usage.xml_sample
===================================================================
--- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Basic_usage.xml_sample (rev 0)
+++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Basic_usage.xml_sample 2011-11-14 18:45:24 UTC (rev 22929)
@@ -0,0 +1,3 @@
+<rich:editor value="#{backingBean.editedValue}" />
+
+<h:outputText escape="false" value="#{backingBean.editedValue}" />
\ No newline at end of file
Added: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Client_side_event_handlers.xml_sample
===================================================================
--- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Client_side_event_handlers.xml_sample (rev 0)
+++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Client_side_event_handlers.xml_sample 2011-11-14 18:45:24 UTC (rev 22929)
@@ -0,0 +1,10 @@
+<rich:editor value="#{backingBean.editorValue}">
+ <a4j:ajax event="change" render="editorOutput" />
+ <a4j:ajax event="dirty" render="editorOutput">
+ <a4j:attachQueue requestDelay="1000" />
+ </a4j:ajax>
+</rich:editor>
+
+<a4j:outputPanel id="editorOutput">
+ <h:outputText escape="false" value="#{backingBean.editorValue}" />
+</a4j:outputPanel>
\ No newline at end of file
Added: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Internationalization_and_localization.xml_sample
===================================================================
--- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Internationalization_and_localization.xml_sample (rev 0)
+++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Internationalization_and_localization.xml_sample 2011-11-14 18:45:24 UTC (rev 22929)
@@ -0,0 +1 @@
+<rich:editor lang="fr" config="language: 'fr'" />
\ No newline at end of file
Added: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Toolbar_customization.xml_sample
===================================================================
--- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Toolbar_customization.xml_sample (rev 0)
+++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/extras/exam-Component_Reference-richeditor-Toolbar_customization.xml_sample 2011-11-14 18:45:24 UTC (rev 22929)
@@ -0,0 +1,18 @@
+<rich:editor toolbar="CustomToolbar">
+ <f:facet name="config">
+ toolbar_CustomToolbar:
+ [
+ { name: 'document', items : [ 'NewPage','Preview' ] },
+ { name: 'clipboard', items : [ 'Cut','Copy','Paste','-','Undo','Redo' ] },
+ { name: 'editing', items : [ 'Find','Replace','-','SelectAll','-','Scayt' ] },
+ { name: 'insert', items : [ 'Image', 'Flash', 'Table', 'HorizontalRule',
+ 'Smiley', 'SpecialChar', 'PageBreak', 'Iframe' ] },
+ '/',
+ { name: 'styles', items : [ 'Styles','Format' ] },
+ { name: 'basicstyles', items : [ 'Bold','Italic','Strike','-','RemoveFormat' ] },
+ { name: 'paragraph', items : [ 'NumberedList','BulletedList','-','Outdent','Indent','-','Blockquote' ] },
+ { name: 'links', items : [ 'Link','Unlink','Anchor' ] },
+ { name: 'tools', items : [ 'Maximize' ] }
+ ]
+ </f:facet>
+</rich:editor>
\ No newline at end of file
Modified: modules/docs/trunk/Component_Reference/src/main/docbook/en-US/skinning/tabl-richeditor.xml
===================================================================
--- modules/docs/trunk/Component_Reference/src/main/docbook/en-US/skinning/tabl-richeditor.xml 2011-11-14 13:56:40 UTC (rev 22928)
+++ modules/docs/trunk/Component_Reference/src/main/docbook/en-US/skinning/tabl-richeditor.xml 2011-11-14 18:45:24 UTC (rev 22929)
@@ -22,11 +22,9 @@
<entry>
<variablelist>
<varlistentry>
- <term><classname>span.cke_skin_richfaces</classname></term>
+ <term><classname>.cke_skin_richfaces</classname></term>
<listitem>
- <para>
- ???
- </para>
+ <para></para>
</listitem>
</varlistentry>
</variablelist>
@@ -41,9 +39,7 @@
<varlistentry>
<term><classname>.cke_skin_richfaces .cke_wrapper</classname></term>
<listitem>
- <para>
- ???
- </para>
+ <para></para>
</listitem>
</varlistentry>
</variablelist>
@@ -58,9 +54,7 @@
<varlistentry>
<term><classname>.cke_skin_richfaces .cke_dialog_body</classname></term>
<listitem>
- <para>
- ???
- </para>
+ <para></para>
</listitem>
</varlistentry>
</variablelist>
@@ -79,9 +73,7 @@
<varlistentry>
<term><classname>.cke_skin_richfaces .cke_dialog_title</classname></term>
<listitem>
- <para>
- ???
- </para>
+ <para></para>
</listitem>
</varlistentry>
</variablelist>
@@ -112,9 +104,7 @@
<varlistentry>
<term><classname>.cke_skin_richfaces .cke_path a</classname>, <classname>.cke_skin_richfaces .cke_path .cke_empty</classname></term>
<listitem>
- <para>
- ???
- </para>
+ <para></para>
</listitem>
</varlistentry>
</variablelist>
@@ -129,9 +119,7 @@
<varlistentry>
<term><classname>.cke_skin_richfaces .cke_button a.cke_on</classname></term>
<listitem>
- <para>
- ???
- </para>
+ <para></para>
</listitem>
</varlistentry>
</variablelist>
@@ -150,9 +138,7 @@
<varlistentry>
<term><classname>.cke_skin_richfaces .cke_button a:hover</classname>, <classname>.cke_skin_richfaces .cke_button a:focus</classname>, <classname>.cke_skin_richfaces .cke_button a:active</classname></term>
<listitem>
- <para>
- ???
- </para>
+ <para></para>
</listitem>
</varlistentry>
</variablelist>
@@ -164,27 +150,6 @@
<entry><para><parameter>tabBackgroundColor</parameter></para></entry>
<entry><para><property>background-color</property></para></entry>
</row>
-
- <row>
- <entry morerows="1">
- <variablelist>
- <varlistentry>
- <term><classname>.rf-ii-btn-p</classname></term>
- <listitem>
- <para>
- This class defines styles for the buttons for the in-place input when they are pressed.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </entry>
- <entry><para><parameter>tabBackgroundColor</parameter></para></entry>
- <entry><para><property>background-color</property></para></entry>
- </row>
- <row>
- <entry><para><parameter>panelBorderColor</parameter></para></entry>
- <entry><para><property>border-color</property></para></entry>
- </row>
<row>
<entry morerows="4">
@@ -194,9 +159,7 @@
<term><classname>.cke_skin_richfaces .cke_rcombo a:active</classname></term>
<term><classname>.cke_skin_richfaces .cke_rcombo a:hover</classname></term>
<listitem>
- <para>
- ???
- </para>
+ <para></para>
</listitem>
</varlistentry>
</variablelist>
@@ -227,9 +190,7 @@
<varlistentry>
<term><classname>.cke_skin_richfaces .cke_rcombo .cke_openbutton</classname></term>
<listitem>
- <para>
- ???
- </para>
+ <para></para>
</listitem>
</varlistentry>
</variablelist>
12 years, 5 months
- 1
- 0
JBoss Rich Faces SVN: r22928 - modules/tests/archetypes/richfaces-simpleapp-ftest/trunk.
by richfaces-svn-commits＠lists.jboss.org
Author: ppitonak(a)redhat.com
Date: 2011-11-14 08:56:40 -0500 (Mon, 14 Nov 2011)
New Revision: 22928
Modified:
modules/tests/archetypes/richfaces-simpleapp-ftest/trunk/pom.xml
Log:
[maven-release-plugin] prepare for next development iteration
Modified: modules/tests/archetypes/richfaces-simpleapp-ftest/trunk/pom.xml
===================================================================
--- modules/tests/archetypes/richfaces-simpleapp-ftest/trunk/pom.xml 2011-11-14 13:56:37 UTC (rev 22927)
+++ modules/tests/archetypes/richfaces-simpleapp-ftest/trunk/pom.xml 2011-11-14 13:56:40 UTC (rev 22928)
@@ -30,14 +30,14 @@
<groupId>org.richfaces.tests.archetypes</groupId>
<artifactId>richfaces-simpleapp-ftest</artifactId>
- <version>4.1.0.20111111-CR1</version>
+ <version>4.1.0-SNAPSHOT</version>
<name>richfaces-simpleapp-ftest</name>
<description>Functional Test for richfaces-archetype-simpleapp</description>
<scm>
- <connection>scm:svn:http://anonsvn.jboss.org/repos/richfaces/modules/tests/archetypes...</connection>
- <developerConnection>scm:svn:https://svn.jboss.org/repos/richfaces/modules/tests/archetypes/ri...</developerConnection>
- <url>http://fisheye.jboss.org/browse/RichFaces/modules/tests/archetypes/richfa...</url>
+ <connection>scm:svn:http://anonsvn.jboss.org/repos/richfaces/modules/tests/archetypes...</connection>
+ <developerConnection>scm:svn:https://svn.jboss.org/repos/richfaces/modules/tests/archetypes/ri...</developerConnection>
+ <url>http://fisheye.jboss.org/browse/RichFaces/modules/tests/archetypes/richfa...</url>
</scm>
<licenses>
12 years, 5 months
- 1
- 0
JBoss Rich Faces SVN: r22927 - modules/tests/archetypes/richfaces-simpleapp-ftest/tags.
by richfaces-svn-commits＠lists.jboss.org
Author: ppitonak(a)redhat.com
Date: 2011-11-14 08:56:37 -0500 (Mon, 14 Nov 2011)
New Revision: 22927
Added:
modules/tests/archetypes/richfaces-simpleapp-ftest/tags/richfaces-simpleapp-ftest-4.1.0.20111111-CR1/
Log:
[maven-scm] copy for tag richfaces-simpleapp-ftest-4.1.0.20111111-CR1
12 years, 5 months
- 1
- 0
JBoss Rich Faces SVN: r22926 - modules/tests/archetypes/richfaces-simpleapp-ftest/trunk.
by richfaces-svn-commits＠lists.jboss.org
Author: ppitonak(a)redhat.com
Date: 2011-11-14 08:56:25 -0500 (Mon, 14 Nov 2011)
New Revision: 22926
Modified:
modules/tests/archetypes/richfaces-simpleapp-ftest/trunk/pom.xml
Log:
[maven-release-plugin] prepare release richfaces-simpleapp-ftest-4.1.0.20111111-CR1
Modified: modules/tests/archetypes/richfaces-simpleapp-ftest/trunk/pom.xml
===================================================================
--- modules/tests/archetypes/richfaces-simpleapp-ftest/trunk/pom.xml 2011-11-14 10:33:16 UTC (rev 22925)
+++ modules/tests/archetypes/richfaces-simpleapp-ftest/trunk/pom.xml 2011-11-14 13:56:25 UTC (rev 22926)
@@ -30,14 +30,14 @@
<groupId>org.richfaces.tests.archetypes</groupId>
<artifactId>richfaces-simpleapp-ftest</artifactId>
- <version>4.1.0-SNAPSHOT</version>
+ <version>4.1.0.20111111-CR1</version>
<name>richfaces-simpleapp-ftest</name>
<description>Functional Test for richfaces-archetype-simpleapp</description>
<scm>
- <connection>scm:svn:http://anonsvn.jboss.org/repos/richfaces/modules/tests/archetypes...</connection>
- <developerConnection>scm:svn:https://svn.jboss.org/repos/richfaces/modules/tests/archetypes/ri...</developerConnection>
- <url>http://fisheye.jboss.org/browse/RichFaces/modules/tests/archetypes/richfa...</url>
+ <connection>scm:svn:http://anonsvn.jboss.org/repos/richfaces/modules/tests/archetypes...</connection>
+ <developerConnection>scm:svn:https://svn.jboss.org/repos/richfaces/modules/tests/archetypes/ri...</developerConnection>
+ <url>http://fisheye.jboss.org/browse/RichFaces/modules/tests/archetypes/richfa...</url>
</scm>
<licenses>
12 years, 5 months
- 1
- 0
JBoss Rich Faces SVN: r22925 - in modules/tests/metamer/trunk: ftest and 1 other directory.
by richfaces-svn-commits＠lists.jboss.org
Author: ppitonak(a)redhat.com
Date: 2011-11-14 05:33:16 -0500 (Mon, 14 Nov 2011)
New Revision: 22925
Modified:
modules/tests/metamer/trunk/ftest/pom.xml
modules/tests/metamer/trunk/pom.xml
Log:
RichFaces changed back to snapshot
Modified: modules/tests/metamer/trunk/ftest/pom.xml
===================================================================
--- modules/tests/metamer/trunk/ftest/pom.xml 2011-11-14 09:25:00 UTC (rev 22924)
+++ modules/tests/metamer/trunk/ftest/pom.xml 2011-11-14 10:33:16 UTC (rev 22925)
@@ -81,8 +81,8 @@
<properties>
<context.path>/metamer/</context.path>
<deployable.classifier>mojarra</deployable.classifier>
- <deployable.version>4.1.0.20111111-CR1</deployable.version>
- <ftest.source.version>4.1.0.20111111-CR1</ftest.source.version>
+ <deployable.version>4.1.0-SNAPSHOT</deployable.version>
+ <ftest.source.version>4.1.0-SNAPSHOT</ftest.source.version>
<testng.suite.xml>src/test/resources/testng.xml</testng.suite.xml>
<container.home>target/installs/${container.dir.deflatted}/${container.dir.unflatted}</container.home>
<jsf.config>Mojarra-2.0</jsf.config>
Modified: modules/tests/metamer/trunk/pom.xml
===================================================================
--- modules/tests/metamer/trunk/pom.xml 2011-11-14 09:25:00 UTC (rev 22924)
+++ modules/tests/metamer/trunk/pom.xml 2011-11-14 10:33:16 UTC (rev 22925)
@@ -124,7 +124,7 @@
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
<richfaces.checkstyle.version>3</richfaces.checkstyle.version>
- <version.richfaces>4.1.0.20111111-CR1</version.richfaces>
+ <version.richfaces>4.1.0-SNAPSHOT</version.richfaces>
</properties>
<dependencyManagement>
12 years, 5 months
- 1
- 0