CKFinder 2.x/Developers Guide/Java/Integration - Revision history

Wiktor: /* File Upload Filter (Removed in CKFinder 2.6) */

2015-12-05T18:20:16Z

‎File Upload Filter (Removed in CKFinder 2.6)

Wiktor: /* File Upload Filter */

2015-12-05T18:20:02Z

‎File Upload Filter

Anna: /* Installing CKFinder as a JSP Page Tag */

2014-02-20T11:56:50Z

‎Installing CKFinder as a JSP Page Tag

Wiktor at 12:38, 21 December 2012

2012-12-21T12:38:49Z

Anna: /* File Upload Filter */ Article section proof-read and corrected

2012-02-10T09:19:38Z

‎File Upload Filter: Article section proof-read and corrected

J.swiderski at 16:22, 9 September 2011

2011-09-09T16:22:01Z

J.swiderski at 15:54, 9 September 2011

2011-09-09T15:54:58Z

Anna: Integration methods section added

2011-05-25T14:39:14Z

Integration methods section added

Wiktor: Removed -2.0

2011-05-02T19:35:31Z

Removed -2.0

Wiktor: /* Installing CKFinder as a JSP Page Tag */ updated basePath

2011-05-01T20:14:43Z

‎Installing CKFinder as a JSP Page Tag: updated basePath

@@ Line 35: / Line 35: @@
 ==File Upload Filter (Removed in CKFinder 2.6)==
-Note: the flash upload component has been completely removed in CKFinder 2.6. As a result, the FileUploadFilter is no longer included in CKFinder.
+'''Note: the flash upload component has been completely removed in CKFinder 2.6. As a result, the FileUploadFilter is no longer included in CKFinder.'''
 As described in the [[CKFinder_2.x/Developers_Guide/Java/Troubleshooting#Flash_Upload_Problem|Flash Upload Problem]] section of the Troubleshooting article, if you are using the Flash multiple file upload component together with session-based authentication, you might get some "missing cookies" problems when trying to upload files. To work around this Flash bug you have to take care of posting cookies yourself. On server side this is done by setting a <code>FileUploadFilter</code>:

@@ Line 33: / Line 33: @@
 * Similarily, some further adjustments of the <code>config.xml</code> file might be needed, like <code>baseUrl</code> and <code>baseDir</code> paths, for example.
-==File Upload Filter==
+==File Upload Filter (Removed in CKFinder 2.6)==
 As described in the [[CKFinder_2.x/Developers_Guide/Java/Troubleshooting#Flash_Upload_Problem|Flash Upload Problem]] section of the Troubleshooting article, if you are using the Flash multiple file upload component together with session-based authentication, you might get some "missing cookies" problems when trying to upload files. To work around this Flash bug you have to take care of posting cookies yourself. On server side this is done by setting a <code>FileUploadFilter</code>:

@@ Line 64: / Line 64: @@
 * In order to use the tag on the JSP page you should import the tag library by using the following directive:
 <source lang="java">
-<%@ taglib uri="http://ckfinder.com" prefix="ckfinder" %>
+<%@ taglib uri="http://cksource.com/ckfinder" prefix="ckfinder" %>
 </source>

@@ Line 81: / Line 81: @@
 == Extending Configuration ==
-The <code>MyConfiguration</code> class lets you change the base CKFinder configuration, or, in other words, change the settings from the XML file at the Java class level. To read more about extending your CKFinder configuration, refer to the [[CKFinder_2.x/Developers_Guide/Java/Configuration/Extending|Extending CKFinder Configuration]] article.
+To read more about extending your CKFinder configuration, refer to the [[CKFinder_2.x/Developers_Guide/Java/Configuration/Extending|Extending CKFinder Configuration]] article.
 == Integration methods ==
 * [[/JavaScript|JavaScript integration]] &ndash; the preferred integration method, simple yet powerful.

@@ Line 35: / Line 35: @@
 ==File Upload Filter==
-As described in Troubleshooting, [[http://docs.cksource.com/CKFinder_2.x/Developers_Guide/Java/Troubleshooting#Flash_Upload_Problem Flash Upload Problem]] section, if you are using Flash multi file upload component together with session based authentication you might get some "missing cookies" problems when trying to upload files. To workaround this Flash bug you have to take care of posting cookies your self. On server side this is done by <code>FileUploadFilter</code>:
+As described in the [[CKFinder_2.x/Developers_Guide/Java/Troubleshooting#Flash_Upload_Problem|Flash Upload Problem]] section of the Troubleshooting article, if you are using the Flash multiple file upload component together with session-based authentication, you might get some "missing cookies" problems when trying to upload files. To work around this Flash bug you have to take care of posting cookies yourself. On server side this is done by setting a <code>FileUploadFilter</code>:
 <source lang="xml">
 <filter>
@@ Line 55: / Line 55: @@
 </source>
-As you can see, besides basic elements like name, full class declaration (<code><filter-class></code>) and mapping applying filter to specific URL (has to be the same mapping as for <code>ConnectorServlet</code>), there are also two optional configuration parameters which help to identify "authentication cookies" that need to be rewritten.
+Besides basic elements like name, full class declaration (<code><filter-class></code>), and a mapping applying the filter to a specific URL (it has to be the same mapping as for <code>ConnectorServlet</code>), there are also two optional configuration parameters which help to identify "authentication cookies" that need to be rewritten.
-Those parameters are name for the session cookie (<code>sessionCookieName</code>) which in Java defaults to "JSESSIONID" value and name for the session path parameter (<code>sessionParameterName</code>) which in Java defaults to "jsessionid". As said before those parameters are optional and can be omitted. However if you are using custom configuration and you have changed names for those session identifiers on your server you should also specify them in <code>FileUploadFilter</code> init parameters so that CKFinder could know what to rewrite.
+Those parameters are the name of the session cookie (<code>sessionCookieName</code>), which in Java defaults to the <code>JSESSIONID</code> value, and the name of the session path parameter (<code>sessionParameterName</code>), which in Java defaults to <code>jsessionid</code>. These parameters are optional and can be omitted. However, if you are using custom configuration and you have changed names for these session identifiers on your server, you should also specify them in the <code>FileUploadFilter</code> init parameters so that CKFinder would know what to rewrite.
 == Installing CKFinder as a JSP Page Tag ==

← Older revision		Revision as of 14:39, 25 May 2011
Line 56:		Line 56:
	== Extending Configuration ==		== Extending Configuration ==
	The <code>MyConfiguration</code> class lets you change the base CKFinder configuration, or, in other words, change the settings from the XML file at the Java class level. To read more about extending your CKFinder configuration, refer to the [[CKFinder_2.x/Developers_Guide/Java/Configuration/Extending\|Extending CKFinder Configuration]] article.		The <code>MyConfiguration</code> class lets you change the base CKFinder configuration, or, in other words, change the settings from the XML file at the Java class level. To read more about extending your CKFinder configuration, refer to the [[CKFinder_2.x/Developers_Guide/Java/Configuration/Extending\|Extending CKFinder Configuration]] article.
		+
		+	== Integration methods ==
		+	* [[/JavaScript\|JavaScript integration]] – the preferred integration method, simple yet powerful.

@@ Line 43: / Line 43: @@
 You can now use the CKFinder tag on your JSP page in the following way:
 <source lang="java">
-<ckfinder:ckfinder basePath="/CKFinderJava-2.0/ckfinder/" />
+<ckfinder:ckfinder basePath="/CKFinderJava/ckfinder/" />
 </source>
@@ Line 49: / Line 49: @@
 <source lang="java">
-<ckfinder:ckfinder basePath="/CKFinderJava-2.0/ckfinder/" width="700" height="500" />
+<ckfinder:ckfinder basePath="/CKFinderJava/ckfinder/" width="700" height="500" />
 </source>