diff --git a/portal-impl/src/META-INF/javadocs.xml b/portal-impl/src/META-INF/javadocs.xml
index 0e6918219ceb37..1d9402ad202954 100644
--- a/portal-impl/src/META-INF/javadocs.xml
+++ b/portal-impl/src/META-INF/javadocs.xml
@@ -1,126438 +1,575786 @@
-Groups are also the entity to which LayoutSets are generally associated. Since LayoutSets are the parent entities of Layouts (i.e. pages), no entity can have associated pages without also having an associated Group. This relationship can be depicted as ... Layout -> LayoutSet -> Group[type] [-> Entity]. Note, the Entity part is optional. -
- -
-Group has a "type" definition that is typically identified by two fields of the entity - String className
, and int type
.
-
-The className
field helps create the group's association with other entities (e.g. Organization, User, Company, UserGroup, ... etc.). The value of className
is the full name of the entity's class and the primary key of the associated entity instance. A site has className="Group"
and has no associated entity.
-
-The type
field helps distinguish between a group used strictly for scoping and a group that also has pages (in which case the type is SITE
). For a list of types, see {@link com.liferay.portal.model.GroupConstants}.
-
-Here is a listing of how Group is related to some portal entities ... -
- -className="Group"
-LayoutPrototype
) has 1 Group which uses only 1
-of it's 2 LayoutSets to store a single page which can later be used to
-derive a single page in any Site
-LayoutSetPrototype
) has 1 Group which uses only
-1 of it's 2 LayoutSets to store many pages which can later be used to derive
-entire Sites or pulled into an existing Site
-end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>true
.
-
-
-Useful when paginating results. Returns a maximum of end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-
false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>null
object. For more information see {@link com.liferay.portal.service.persistence.GroupFinder}]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>null
object. For more information see {@link com.liferay.portal.service.persistence.GroupFinder}]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>null
object. For more information see {@link com.liferay.portal.service.persistence.GroupFinder}]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>true
.
-
-
-Useful when paginating results. Returns a maximum of end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-
classNames
value of null
includes the user's layout set group, organization groups, inherited organization groups, and site groups. classNames
value of null
includes the user's layout set group, organization groups, inherited organization groups, and site groups. false
otherwise]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>false
otherwise.]]>false
otherwise]]>selected-pages
.]]>layoutSetPrototypeLinkEnabled
to false
. However, this method can only enable the layout set prototype's link if the layout set prototype's current uuid is not null
. Setting the layoutSetPrototypeLinkEnabled
to true
when the layout set prototype's current uuid is null
will have no effect.
-]]>layoutSetPrototypeLinkEnabled
to true
and layoutSetPrototypeUuid
to null
when the layout set prototype's current uuid is null
will result in an IllegalStateException
.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>availableOrganizations
.]]>availableOrganizations
]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>- -
inheritSuborganizations=false
:
-the method checks whether the user belongs to the organization specified
-by organizationId
. The parameter
-includeSpecifiedOrganization
is ignored.
+ isRequiresSecure
method to programmatically decide when a request requires HTTPS.
+]]>+For a usage example see {@link com.liferay.portlet.shopping.util.ShoppingUtil#getBreadcrumbs( com.liferay.portlet.shopping.model.ShoppingCategory, javax.servlet.jsp.PageContext, javax.portlet.RenderRequest, javax.portlet.RenderResponse) ShoppingUtil.getBreadcrumbs} . +
]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>done
which will open the latch. All blocking loser threads can pass the latch at the same time.
+
++See LPS-3744 for a sample use case. +
]]>false
if the waiting time elapsed before the latch be opened.]]>false
if the latch is already open]]>false
otherwise]]>false
otherwise]]>PortletDataHandler
s are defined by placing a portlet-data-handler-class
element in the portlet
section of the liferay-portlet.xml file.]]>importData()
.]]>friendly-url-routes.xml
file will handle the needs of most portlets.
+]]>liferay-portlet.xml
, and write a friendly-url-routes.xml
file.
+
+
++If you do need to extend this class, use {@link com.liferay.util.bridges.alloy.AlloyFriendlyURLMapper} as a guide. The key methods to override are {@link #buildPath(LiferayPortletURL)} and {@link #populateParams(String, Map, Map)}. +
]]>p_p_id
and instanceId
for instanceable portlets.
+]]>instanceId
.]]>null
will cause a normal portlet URL to be generated.]]>/-/
in the URL.
+
+
+
+For instance, the blogs portlet mapping is "blogs". This produces friendly URLs similar to http://www.liferay.com/web/guest/blog/-/blogs/example-post
+
+Typically, friendly URLs will include the separator "/-/" before the friendly URL mapping. If this method returns false
, a single slash will be used instead.
+
+This method is called by {@link com.liferay.portal.util.PortalImpl} when a friendly URL is processed. +
+ +
+It is strongly recommended that this method always return true
.
+
false
if only a "/" should be used]]>+The value returned from this method has no effect on whether a portlet is instanceable, it is a helper method used to determine if the instance ID should be included in the URL. +
]]>false
otherwise]]>liferay-portlet.xml
.
+]]>liferay-portlet.xml
.
+]]>p_p_id
and p_p_lifecycle
.
+]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>+Note that this is not the same as making a URL {@link #setSecure(boolean) secure}. +
]]>false
any existing values will be overwritten with the new value.]]>false
any existing values will be overwritten with the new values.]]>+When a URL is generated, the opposite process occurs. The generated parameter must have its value passed in through the parameter map. This value is parsed using the pattern string, and the virtual parameters are populated and made available for use in the route pattern string. The value of the generated parameter will not be available in the route pattern; only the values of the virtual parameters may be used. +
+ ++The following is an example route definition that uses a generated parameter to remove the .jsp extension of the current page from the URL. +
+ +
+
+<route>
+ <pattern>/{jspPageName}/{id:\d+}</pattern>
+ <generated-parameter name="jspPage">{jspPageName}.jsp</generated-parameter>
+</route>
+
+
]]>+Implicit parameters are matched after all virtual parameters have been populated, and therefore should not match against the value of a generated parameter, as it will not be available. +
+ ++The most common use of implicit parameters is to specify a parameter that is included statically in the route pattern. For instance, if a custom route is specified for the JSP page "view_profile.jsp", the routes definition could look like the following: +
+ +
+
+<route>
+ <pattern>/profile/view/{id:\d+}</pattern>
+ <implicit-parameter name="jspPage">view_profile.jsp</implicit-parameter>
+</route>
+
+
+
++Since the jspPage is specified with a implicit-parameter, this route will only be used to generate URLs if the jspPage is set to "view_profile.jsp". Likewise, when a URL in this format is recognized, the jspPage will automatically be set to "view_profile.jsp". +
]]>+If a implicit parameter and an overridden parameter share the same name, the overridden parameter value will take precedence when a URL is parsed. When a URL is generated the implicit parameter value will be checked against the parameter map as usual. +
]]>parameters
for the route's generated
+parameters match their patterns
+parameters
+parameters
+parameters
if possible. If the pattern for a virtual parameter in the generated parameter does not match its pattern in the route, that generated parameter may not be build.
+
+
+
+Virtual parameters will not be present in parameters
.
+
false
otherwise]]>+When choosing the order in which to place a list of routes, the general rule is to sort the routes from least general to most general. The simplest way of determining the generality of a route is by counting the number of capturing fragments in it. +
]]>parameters
was populated; false
otherwise]]>+The entities that support these operations are: +
+ +changeType
tells if the change happened in source or target. lineNumber
holds the line number of the first modified line. This line number refers to a line in source or target, depending on the changeType
value. changedLines
is a list of strings, each string is a line that is already highlighted, indicating where the changes are.
+]]>false
and no localization exists for the requested language, an empty string will be returned.]]>false
and no localization exists for the requested language, an empty string will be returned.]]>false
and no localization exists for the requested language, an empty array will be returned.]]>
+
+Hi {name}! How are you?
+
+
+
+
+This pattern would match the string "Hi Tom! How are you?". The format of a fragment may optionally be specified by inserting a colon followed by a regular expression after the fragment name. For instance, name
could be set to match only lower case letters with the following:
+
+
+Hi {name:[a-z]+}! How are you?
+
+
+
++By default, a fragment will match anything except a forward slash or a period. +
+ ++If a string parser is set to encode fragments using a {@link StringEncoder}, an individual fragment can be specified as raw by prefixing its name with a percent sign, as shown below: +
+ +
+
+/view_page/{%path:.*}
+
+
+
++The format of the path fragment has also been specified to match anything using the pattern ".*". This pattern could be used to parse the string: +
+ +
+
+/view_page/root/home/mysite/pages/index.htm
+
+
+
+
+path
would be set to "root/home/mysite/pages/index.htm", even if {@link URLStringEncoder} had been set as the string encoder.
+
+Do not include capturing subgroups in the pattern. +
]]>+If this parser is appropriate, all the parameters used in the pattern will be removed from the parameter map. If this parser is not appropriate, the parameter map will not be modified. +
]]>false
otherwise]]>s
resulting in a comma delimited list of strings, disallowing duplicate strings in the list.
+
++The resulting string ends with a comma even if the original string does not. +
]]>null
]]>s
that represents a delimited list of strings, using a specified delimiter and disallowing duplicate words.
+
++The returned string ends with the delimiter even if the original string does not. +
]]>null
]]>s
that represents a delimited list of strings, using a specified delimiter and optionally allowing duplicate words.
+
++The returned string ends with the delimiter even if the original string does not. +
]]>null
]]>suffix - 1
, then the existing parenthetical suffix is replaced by the new one.
+
+
++Examples: +
+ +
+
+appendParentheticalSuffix("file", 0) returns "file (0)"
+appendParentheticalSuffix("file (0)", 0) returns "file (0) (0)"
+appendParentheticalSuffix("file (0)", 1) returns "file (1)"
+appendParentheticalSuffix("file (0)", 2) returns "file (0) (2)"
+
+]]>
+
+appendParentheticalSuffix("Java", "EE") returns "Java (EE)"
+
+
]]>+Example: +
+ +
+
+contains("application", "app") returns true
+
+
]]>false
otherwise]]>+Examples: +
+ +
+
+contains("three...two...one", "two", "...") returns true
+contains("three...two...one", "thr", "...") returns false
+
+
]]>false
otherwise]]>false
otherwise]]>end
.]]>end
; false
otherwise]]>chars
. The substring of characters returned maintain their original order.]]>chars
, or an empty string if the given string is null
]]>null
if the string is null
or the delimiter does not occur in the string]]>null
if the string is null
or the delimiter does not occur in the string]]>null
if the string is null
or the delimiter does not occur in the string]]>null
if the string is null
or the delimiter does not occur in the string]]>null
]]>null
]]>null
]]>null
]]>null
]]>null
]]>null
]]>null
]]>null
]]>null
]]>null
]]>null
]]>null
]]>null
]]>null
]]>null
]]>null
]]>null
]]>
+
+quote("Hello, World!") returns "'Hello, World!'"
+
+
]]>null
]]>
+
+quote("PATH", '%') returns "%PATH%"
+
+
]]>null
]]>
+
+quote("WARNING", "!!!") returns "!!!WARNING!!!"
+
+
]]>null
]]>s
that represents a list of comma delimited strings.
+
++The resulting string ends with a comma even if the original string does not. +
+ ++Examples: +
+ +
+
+remove("red,blue,green,yellow", "blue") returns "red,green,yellow,"
+remove("blue", "blue") returns ""
+remove("blue,", "blue") returns ""
+
+
]]>null
if the original string, the string to remove, or the delimiter is null
]]>s
that represents a list of delimited strings.
+
++The resulting string ends with the delimiter even if the original string does not. +
+ ++Examples: +
+ +
+
+remove("red;blue;green;yellow", "blue") returns "red,green,yellow;"
+remove("blue", "blue") returns ""
+remove("blue;", "blue") returns ""
+
+
]]>null
if the original string, the string to remove, or the delimiter is null
]]>newSub
character, or null
if the original string is null
]]>newSub
, or null
if the original string is null
]]>newSub
, or null
if the original string is null
]]>newSub
, or null
if the original string is null
]]>newSubs
strings, or null
if the original string, the oldSubs
array, or the newSubs
is null
]]>
+
+replace("redorangeyellow", {"red", "orange", "yellow"}, {"RED","ORANGE", "YELLOW"}, false) returns "REDORANGEYELLOW"
+replace("redorangeyellow", {"red", "orange", "yellow"}, {"RED","ORANGE", "YELLOW"}, true) returns "redorangeyellow"
+replace("redorange yellow", {"red", "orange", "yellow"}, {"RED","ORANGE", "YELLOW"}, false) returns "REDORANGE YELLOW"
+replace("redorange yellow", {"red", "orange", "yellow"}, {"RED","ORANGE", "YELLOW"}, true) returns "redorange YELLOW"
+replace("red orange yellow", {"red", "orange", "yellow"}, {"RED","ORANGE", "YELLOW"}, false) returns "RED ORANGE YELLOW"
+replace("redorange.yellow", {"red", "orange", "yellow"}, {"RED","ORANGE", * "YELLOW"}, true) returns "redorange.YELLOW"
+
+
]]>true
, a string representing the original string with all occurrences of the oldSubs
strings that are surrounded by word boundaries replaced with the corresponding newSubs
strings, or else a string representing the original string with all occurrences of the oldSubs
strings replaced with the corresponding newSubs
strings, or null
if the original string, the oldSubs
array, or the newSubs
null]]>newSub
]]>newSub
]]>newSub
]]>newSubs
strings, or null
if the original string, the oldSubs
array, or the newSubs
null]]>newSub
]]>newSub
]]>s
with the string newSub
.]]>newSub
]]>newSubs
strings, or null
if the original string, the oldSubs
array, or the newSubs
null]]>
+
+safePath("http://www.liferay.com") returns "http:/www.liferay.com"
+
+
]]>+Examples: +
+ +
+
+shorten("12345678901234567890xyz") returns "12345678901234567890..."
+shorten("1 345678901234567890xyz") returns "1..."
+shorten(" 2345678901234567890xyz") returns "..."
+shorten("12345678901234567890") returns "12345678901234567890"
+shorten(" 2345678901234567890") returns " 2345678901234567890"
+
+
]]>+Examples: +
+ +
+
+shorten("123456", 5) returns "12345..."
+shorten("1 3456", 5) returns "1..."
+shorten(" 23456", 5) returns "..."
+shorten("12345", 5) returns "12345"
+shorten(" 1234", 5) returns " 1234"
+
+
]]>+Examples: +
+ +
+
+shorten("123456", 5, "... etc.") returns "12345... etc."
+shorten("1 3456", 5, "... etc.") returns "1... etc."
+shorten(" 23456", 5, "... etc.") returns "... etc."
+shorten("12345", 5, "... etc.") returns "12345"
+shorten(" 1234", 5, "... etc.") returns " 1234"
+
+
]]>+Examples: +
+ +
+
+shorten("12345678901234567890xyz", "... etc.") returns "12345678901234567890... etc."
+shorten("1 345678901234567890xyz", "... etc.") returns "1... etc."
+shorten(" 2345678901234567890xyz", "... etc.") returns "... etc."
+shorten("12345678901234567890", "... etc.") returns "12345678901234567890"
+shorten(" 2345678901234567890", "... etc.") returns " 2345678901234567890"
+
+
]]>+Example: +
+ +
+
+split("Alice,Bob,Charlie") returns {"Alice", "Bob", "Charlie"}
+split("Alice, Bob, Charlie") returns {"Alice", " Bob", " Charlie"}
+
+
]]>s
is null
or s
is empty]]>s
is null
]]>+Example: +
+ +
+
+splitLines("First;Second;Third", ';') returns {"First","Second","Third"}
+
+
]]>s
is null
or if s
is empty]]>s
is null
]]>s
is null
]]>s
is null
]]>s
is null
]]>s
is null
]]>+Example: +
+ +
+
+splitLines("oneandtwoandthreeandfour", "and") returns {"one","two","three","four"}
+
+
]]>s
is null
or equals the delimiter]]>s
is null
]]>s
is null
]]>s
is null
]]>s
is null
]]>s
is null
]]>s
is null
]]>+Example: +
+ +
+
+splitLines("Red\rBlue\nGreen") returns {"Red","Blue","Green"}
+
+
]]>s
is null
]]>false
otherwise]]>false
otherwise]]>s2
have in common before their characters deviate.]]>s2
have in common before their characters deviate]]>+Example: +
+ +
+
+strip("Mississipi", 'i') returns "Mssssp"
+
+
]]>null
if s
is null
]]>begin
concatenated with the substring of s
after but not including the string end
.
+
++Example: +
+ +
+
+stripBetween("One small step for man, one giant leap for mankind", "step", "giant ") returns "One small leap for mankind"
+
+
]]>begin
concatenated with the substring of s
after but not including the string end
, or the original string if the value of s
, begin
, or end
are null
]]>+Example: +
+ +
+
+toCharCode("a") returns "97"
+toCharCode("b") returns "98"
+toCharCode("c") returns "99"
+toCharCode("What's for lunch?") returns "87104971163911532102111114321081171109910463"
+
+]]>
+Examples: +
+ +
+
+trim(" \tHey\t ", '\t') returns "\tHey\t"
+trim(" \t Hey \t ", '\t') returns "\t Hey \t"
+
+
]]>null
]]>true
otherwise]]>+In its current form, this is not intended to replace java.util.Properties for reading properties flat files. This class is not thread-safe. +
]]>java.util.List
. Query operations will "read through" to the specified list. Attempts to modify the list directly or via its iterator will result in a java.lang.UnsupportedOperationException
.
+]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>null
.]]>null
; false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>null
; it does not actually check the format of the string.]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>null
, meaning it is neither a null
reference or zero.]]>null
; false
otherwise]]>null
, using the rules from {@link #isNotNull(Long)} or {@link #isNotNull(String)} if the object is one of these types.]]>null
; false
otherwise]]>null
, meaning it is neither a null
reference or empty.]]>null
; false
otherwise]]>null
, meaning it is not a null
reference, nothing but spaces, or the string "null
".]]>null
; false
otherwise]]>null
, meaning it is either a null
reference or zero.]]>null
; false
otherwise]]>null
, using the rules from {@link #isNull(Long)} or {@link #isNull(String)} if the object is one of these types.]]>null
; false
otherwise]]>null
, meaning it is either a null
reference or empty.]]>null
; false
otherwise]]>null
, meaning it is a null
reference, nothing but spaces, or the string "null
".]]>null
; false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>null
character '0' or whitespace according to {@link java.lang.Character#isWhitespace(char)}.]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>+Groups also have a second, partially conflicting purpose in Liferay. For legacy reasons, groups are also the model used to represent sites (known as communities before Liferay v6.1). Confusion may arise from the fact that a site group is both the resource container and the site itself, whereas a layout or organization would have both a primary model and an associated group. +
]]>false
if preferences are owned by the user at all times.]]>false
if preferences are owned by the user at all times.]]>false
if preferences are owned by the user at all times.]]>false
if preferences are owned by the user at all times.]]>false
if preferences are owned by the user at all times.]]>False
if preferences are owned by the user at all times.]]>+The second constraint is required because users can have different roles in different groups. If resources from different groups were contained in the same resource block, it would be impossible to check permissions properly when loading resources from multiple groups simultaneously. A user could have access to a certain resource block in one group, but not in another. +
+ +
+The type of resource a resource block contains is specified by the name
attribute, which must be the fully qualified class name of a model (such as a blog entry).
+
+The permissionsHash
attribute holds a hashed representation of the permissions shared by all the resources contained in the block. When the permissions on an individual resource are changed, a new permissions hash is calculated for it, and the database is checked to determine if a resource block already exists with that hash. If one exists, the resource is moved into that block; otherwise a new block is created.
+
+The referenceCount
attribute stores the number of resources in the resource block, meaning those resources whose resourceBlockId
is set to the primary key of this resource block. If referenceCount
reaches zero, the resource block is no longer needed and may be safely deleted. To ensure that this reference count remains accurate, resources must always call {@link com.liferay.portal.service.impl.ResourceLocalServiceImpl#deleteResource} when a resource is deleted.
+
actionIds
attribute stores the bitwise IDs of all the actions allowed by this permission.
+]]>name
attribute. It will either be the numeric ID of a portlet, or the fully qualified class name of a model (such as a layout or document library folder).
+
+
++These permissions can apply in one of four scopes: company, group, group-template, or individual. The scope of a permission determines how broadly it applies to resources in the portal. Company scope is the broadest, and grants a user with the role permissions for every resource of the type within the company. Likewise, group scope gives users with the role permissions for every resource within the specified group, and individual scope only applies to a single resource of the type. Group-template scope is similar to group scope, except that it does not automatically apply to a specific group. A user must be a member of a group (generally either a site or an organization), and they must have been given the role within that group before they are granted its permissions. +
+ ++Note: Lacking permission to perform an action on a resource at one scope does not necessarily mean that a role does not have permission to perform that action. For instance, a message boards moderator role will not have individual scope permissions to edit every post, but it will have edit permissions at the group or company level, which is sufficient. Every scope must be checked. +
+ +
+The scope of the resource permission also determines the meaning of the primKey
attribute. Its different uses are listed below:
+
primKey
is the primary key of the company
+primKey
is the primary key of the group the
+permission applies within
+primKey
is always 0
+primkey
will be the primary key of the instance. If the
+permission is for a portlet, primKey
will contain the primary
+key of the layout containing the portlet, followed by "_LAYOUT_"
+and the portlet ID. The instance ID will also be present for instanceable
+portlets, preceded by "_INSTANCE_".
+
+The actionIds
attribute stores the bitwise IDs of all the actions allowed by this permission.
+
+Do not confuse resource type permissions with resource block permissions; they serve very different purposes. Resource block permissions store the permissions on a single resource block, and are simply a representation of who can do what to the resources within the block. Resource type permissions grant permissions to perform actions on all resources of a type within a group or company. Any permissions granted to a role with a resource type permission are automatically added to all the resource blocks for that resource type within the group/company. +
+ ++For example, if a company scope resource type permission is granted to a role to edit blog entries, all the resource blocks within the company for blog entries are modified to grant the role permission to edit the blog entries they contain. Thus, granting and revoking resource type permissions will also cause those same permissions to be granted/revoked at the resource block permission level. +
+ ++Copying permissions from the company and group scope to the resource block scope eliminates the need to check multiple scopes when determining if a role has permission to perform an action on a resource. All the necessary information is cached at the most granular level. +
+ +
+Rather than using a separate "scope" attribute as {@linkplain ResourcePermissionImpl resource permissions} do, company scope resource type permissions simply have a groupId
of 0
+
+The type of resource the permission grants access to is specified by the name
attribute, which must be the fully qualified class name of a model (such as a blog entry).
+
+The actionIds
attribute stores the bitwise IDs of all the actions allowed by this permission.
+
+2. Install the Modify Headers 0.5.4 Add-on. Tools > Add Ons. Click the get extensions link at the bottom of the window. Type in "Modify Headers" in the Search box. Find Modify Headers in the results page and click on it. Then click the install now link. +
+ ++3. Configure Modify Headers to add a basic authentication header. Tools > Modify Headers. In the Modify Headers window select the Add drop down. Type in "Authorization" in the next box. Type in "Basic bGlmZXJheS5jb20uMTp0ZXN0" in the next box. Click the Add button. +
+ ++4. Make sure your header modification is enabled and point your browser to the Liferay portal. +
+ ++5. You should now be authenticated as Joe Bloggs. +
]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>ServiceContext
object simplifies method signatures and provides a way to consolidate many different methods with different sets of optional parameters into a single, easier to use method. It also aggregates information necessary for transversal features such as permissioning, tagging, categorization, etc.
+]]>false
otherwise]]>+Example: +
+ ++Person1 and person2 start editing the same version of a Web Content article. Person1 publishes changes to the article first. When person2 attempts to publish changes to that article, the service implementation finds that a modification to that article has already been published some time after person2 started editing the article. Since the the article modification date was found to be later than the form date for person2, person2 could be alerted to the modification and make a backup copy of his edits before synchronizing with the published changes by person1. +
]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>+Example: +
+ ++Person1 and person2 start editing the same version of a Web Content article. Person1 publishes changes to the article first. When person2 attempts to publish changes to that article, the service implementation finds that a modification to that article has already been published some time after person2 started editing the article. Since the the article modification date was found to be later than the form date for person2, person2 could be alerted to the modification and make a backup copy of his edits before synchronizing with the published changes by person1. +
]]>null
)]]>+Groups are also the entity to which LayoutSets are generally associated. Since LayoutSets are the parent entities of Layouts (i.e. pages), no entity can have associated pages without also having an associated Group. This relationship can be depicted as ... Layout -> LayoutSet -> Group[type] [-> Entity]. Note, the Entity part is optional. +
+ +
+Group has a "type" definition that is typically identified by two fields of the entity - String className
, and int type
.
+
+The className
field helps create the group's association with other entities (e.g. Organization, User, Company, UserGroup, ... etc.). The value of className
is the full name of the entity's class and the primary key of the associated entity instance. A site has className="Group"
and has no associated entity.
+
+The type
field helps distinguish between a group used strictly for scoping and a group that also has pages (in which case the type is SITE
). For a list of types, see {@link com.liferay.portal.model.GroupConstants}.
+
+Here is a listing of how Group is related to some portal entities ... +
+ +className="Group"
+LayoutPrototype
) has 1 Group which uses only 1
+of it's 2 LayoutSets to store a single page which can later be used to
+derive a single page in any Site
+LayoutSetPrototype
) has 1 Group which uses only
+1 of it's 2 LayoutSets to store many pages which can later be used to derive
+entire Sites or pulled into an existing Site
+end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>true
.
+
+
+Useful when paginating results. Returns a maximum of end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+
false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>null
object. For more information see {@link com.liferay.portal.service.persistence.GroupFinder}]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>null
object. For more information see {@link com.liferay.portal.service.persistence.GroupFinder}]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>null
object. For more information see {@link com.liferay.portal.service.persistence.GroupFinder}]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>true
.
+
+
+Useful when paginating results. Returns a maximum of end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+
classNames
value of null
includes the user's layout set group, organization groups, inherited organization groups, and site groups. classNames
value of null
includes the user's layout set group, organization groups, inherited organization groups, and site groups. false
otherwise]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>false
otherwise.]]>false
otherwise]]>selected-pages
.]]>layoutSetPrototypeLinkEnabled
to false
. However, this method can only enable the layout set prototype's link if the layout set prototype's current uuid is not null
. Setting the layoutSetPrototypeLinkEnabled
to true
when the layout set prototype's current uuid is null
will have no effect.
+]]>layoutSetPrototypeLinkEnabled
to true
and layoutSetPrototypeUuid
to null
when the layout set prototype's current uuid is null
will result in an IllegalStateException
.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>availableOrganizations
.]]>availableOrganizations
]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>+ +
inheritSuborganizations=false
:
+the method checks whether the user belongs to the organization specified
+by organizationId
. The parameter
+includeSpecifiedOrganization
is ignored.
+includeSpecifiedOrganization
is
+ignored unless inheritSuborganizations
is also
+true
.
+inheritSuborganizations=true
and
+includeSpecifiedOrganization=false
: the method
+checks
+whether the user belongs to one of the child organizations of the one
+specified by organizationId
.
+inheritSuborganizations=true
and
+includeSpecifiedOrganization=true
: the method
+checks whether
+the user belongs to the organization specified by
+organizationId
or any of
+its child organizations.
+]]>
organizationId
is considered in the determination]]>false
otherwise]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>+If a company scope permission is granted to resources that the role already had group scope permissions to, the group scope permissions are deleted. Likewise, if a group scope permission is granted to resources that the role already had company scope permissions to, the company scope permissions are deleted. Be aware that this latter behavior can result in an overall reduction in permissions for the role. +
+ +
+Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
+
+Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
+
+Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
+
end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>
+Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
+
false
otherwise]]>
+Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
+
false
otherwise]]>
+Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
+
false
otherwise]]>
+Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
+
false
otherwise]]>primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
+]]>
+Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
+
+Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
+
+Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
+
primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
+]]>primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
+]]>+If a company scope permission is granted to resources that the role already had group scope permissions to, the group scope permissions are deleted. Likewise, if a group scope permission is granted to resources that the role already had company scope permissions to, the company scope permissions are deleted. Be aware that this latter behavior can result in an overall reduction in permissions for the role. +
+ +
+Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
+
primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
+]]>
+Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
+
+Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
+
false
otherwise]]>false
otherwise]]>false
otherwise]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>admin.default.group.names
.]]>admin.default.role.names
.]]>admin.default.user.group.names
.]]>uuid
attribute), asset category IDs, asset tag names, and expando bridge attributes for the user.]]>uuid
attribute), asset category IDs, asset tag names, and expando bridge attributes for the user.]]>password
was null
]]>password
was null
]]>password
was null
]]>
+Authentication type specifies what login
contains.The valid values are:
+
CompanyConstants.AUTH_TYPE_EA
- login
is the
+user's email address
+CompanyConstants.AUTH_TYPE_SN
- login
is the
+user's screen name
+CompanyConstants.AUTH_TYPE_ID
- login
is the
+user's primary key
+false
otherwise]]>sendEmail
attribute) for the user.]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>admin.email.password
keys.]]>portal.properties
will be used.]]>portal.properties
will be used.]]>uuid
attribute), asset category IDs, asset tag names, and expando bridge attributes for the user.]]>login
contains.The valid values are:
+
+
+CompanyConstants.AUTH_TYPE_EA
- login
is the
+user's email address
+CompanyConstants.AUTH_TYPE_SN
- login
is the
+user's screen name
+CompanyConstants.AUTH_TYPE_ID
- login
is the
+user's primary key
+password
was null
]]>uuid
attribute), asset category IDs, asset tag names, and expando bridge attributes for the user.]]>uuid
attribute), asset category IDs, asset tag names, and expando bridge attributes for the user.]]>uuid
attribute), asset category IDs, asset tag names, and expando bridge attributes for the user.]]>uuid
attribute), asset category IDs, asset tag names, and expando bridge attributes for the user.]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>uuid
attribute), asset category IDs, asset tag names, and expando bridge attributes for the user.]]>uuid
attribute), asset category IDs, asset tag names, and expando bridge attributes for the user.]]>portal.properties
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>true
:
+
+
+includeSpecifiedOrganization
is
-ignored unless inheritSuborganizations
is also
-true
.
+The batch size is set to zero
inheritSuborganizations=true
and
-includeSpecifiedOrganization=false
: the method
-checks
-whether the user belongs to one of the child organizations of the one
-specified by organizationId
.
+Enough updates and/or deletions have been queued to fill another batch
+
+The batch size may be set in portal.properties with the key hibernate.jdbc.batch_size
.
+
false
otherwise]]>true
:
+
+
+inheritSuborganizations=true
and
-includeSpecifiedOrganization=true
: the method
-checks whether
-the user belongs to the organization specified by
-organizationId
or any of
-its child organizations.
+The batch size is set to zero
+The batch size may be set in portal.properties with the key hibernate.jdbc.batch_size
.
+
+The merge
parameter controls a special case of persistence. If the session that a model instance was originally loaded from is closed, that instance becomes "detached", and changes to it will not be persisted automatically. To persist its changes, the detached instance must be merged with the current session. This will load a new copy of the model instance from the database, copy the changes to it, and persist it.
+
+This process is most commonly necessary if a model instance is modified in the controller or view, as the database session is closed when control leaves the model layer. However, local service update model methods use merging by default, so in most cases this nuance is handled automatically. See {@link com.liferay.portal.service.UserLocalService#updateUser( com.liferay.portal.model.User)} for an example. +
]]>portal.properties
+]]>null
]]>null
]]>null
]]>null
]]>renderRequest.getAttribute(PortletRequest.USER_INFO)
is called. It is safe to cache attributes in this instance because you can assume that all calls to this instance belong to the same user.
+]]>portal.properties
under the key omniadmin.users. If this property is left blank, administrators of the default company will automatically be universal administrators.
+]]>
end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>
+The repositoryId
parameter used by most of the methods is the primary key of the specific repository. If the repository is a default Liferay repository, the repositoryId
is the groupId
or scopeGroupId
. Otherwise, the repositoryId
will correspond to values obtained from {@link RepositoryLocalServiceUtil}.
+
sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal. If it is null
, the sourceFileName
will be used.
+]]>sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal. If it is null
, the sourceFileName
will be used.
+]]>sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal. If it is null
, the sourceFileName
will be used.
+]]>title
, description
, and parameters in the serviceContext
) will be updated.
+
+
+This method takes two file names, the sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal.
+
null
)]]>title
, description
, and parameters in the serviceContext
) will be updated.
+
+
+This method takes two file names, the sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal.
+
null
)]]>title
, description
, and parameters in the serviceContext
) will be updated.
+
+
+This method takes two file names, the sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal.
+
null
)]]>workflowDefinition
appended by the fileEntryTypeId
(optionally 0
).
+The repositoryId
parameter used by most of the methods is the primary key of the specific repository. If the repository is a default Liferay repository, the repositoryId
is the groupId
or scopeGroupId
. Otherwise, the repositoryId
will correspond to values obtained from {@link RepositoryServiceUtil}.
+
sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal. If it is null
, the sourceFileName
will be used.
+]]>sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal. If it is null
, the sourceFileName
will be used.
+]]>sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal. If it is null
, the sourceFileName
will be used.
+]]>portal.properties>.]]>
end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>portal.properties>.]]>
portal.properties>.]]>
portal.properties>.]]>
title
, description
, and parameters in the serviceContext
) will be updated.
+
+
+This method takes two file names, the sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal.
+
null
)]]>title
, description
, and parameters in the serviceContext
) will be updated.
+
+
+This method takes two file names, the sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal.
+
null
)]]>title
, description
, and parameters in the serviceContext
) will be updated.
+
+
+This method takes two file names, the sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal.
+
null
)]]>workflowDefinition
appended by the fileEntryTypeId
(optionally 0
). false
otherwise]]>false
otherwise]]>name
is a unique identifier for a given file and is generally numeric, whereas the title
is the actual name specified by the user (such as "Budget.xls").
+]]>+This method should be overrided if a more optimized approach can be used (e.g., {@link FileSystemStore#getFile(long, long, String, String)}). +
]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>dl.store.impl
. Virus checking can also be enabled under the property dl.store.antivirus.impl
.
+
+
+The main client for this class is the Document Library portlet. It is also used by other portlets like Wiki and Message Boards to store file attachments. For the Document Library portlet, the repositoryId
can be obtained by calling {@link com.liferay.portlet.documentlibrary.model.DLFolderConstants#getDataRepositoryId( long,long)}. For all other portlets, the repositoryId
should be set to {@link CompanyConstants#SYSTEM}. These methods can be used in plugins and other portlets, as shown below.
+
+
+long repositoryId = CompanyConstants.SYSTEM;
+String dirName = "portlet_name/1234";
+
+try {
+DLStoreUtil.addDirectory(companyId, repositoryId, dirName);
+}
+catch (DuplicateDirectoryException dde) {
+}
+
+DLStoreUtil.addFile(
+companyId, repositoryId, dirName + "/" + fileName, file);
+
+
]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>]]>
+This PortletDataHandler
differs from from JournalPortletDataHandlerImpl
in that it only exports articles referenced in Journal Content portlets. Articles not displayed in Journal Content portlets will not be exported unless JournalPortletDataHandlerImpl
is activated.
+
+This PortletDataHandler
differs from JournalContentPortletDataHandlerImpl
in that it exports all articles owned by the group whether or not they are actually displayed in a portlet in the layout set.
+
organizationId
is considered in the determination]]>false
otherwise]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>-If a company scope permission is granted to resources that the role already had group scope permissions to, the group scope permissions are deleted. Likewise, if a group scope permission is granted to resources that the role already had company scope permissions to, the company scope permissions are deleted. Be aware that this latter behavior can result in an overall reduction in permissions for the role. -
- -
-Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
-
-Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
-
-Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
-
end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>
-Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
-
false
otherwise]]>
-Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
-
false
otherwise]]>
-Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
-
false
otherwise]]>
-Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
-
false
otherwise]]>primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
-]]>
-Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
-
-Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
-
-Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
-
primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
-]]>primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
-]]>-If a company scope permission is granted to resources that the role already had group scope permissions to, the group scope permissions are deleted. Likewise, if a group scope permission is granted to resources that the role already had company scope permissions to, the company scope permissions are deleted. Be aware that this latter behavior can result in an overall reduction in permissions for the role. -
- -
-Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
-
primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
-]]>
-Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
-
-Depending on the scope, the value of primKey
will have different meanings. For more information, see {@link com.liferay.portal.model.impl.ResourcePermissionImpl}.
-
false
otherwise]]>false
otherwise]]>false
otherwise]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>admin.default.group.names
.]]>admin.default.role.names
.]]>admin.default.user.group.names
.]]>uuid
attribute), asset category IDs, asset tag names, and expando bridge attributes for the user.]]>uuid
attribute), asset category IDs, asset tag names, and expando bridge attributes for the user.]]>password
was null
]]>password
was null
]]>password
was null
]]>
-Authentication type specifies what login
contains.The valid values are:
-
CompanyConstants.AUTH_TYPE_EA
- login
is the
-user's email address
-CompanyConstants.AUTH_TYPE_SN
- login
is the
-user's screen name
-CompanyConstants.AUTH_TYPE_ID
- login
is the
-user's primary key
-false
otherwise]]>sendEmail
attribute) for the user.]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>admin.email.password
keys.]]>portal.properties
will be used.]]>portal.properties
will be used.]]>uuid
attribute), asset category IDs, asset tag names, and expando bridge attributes for the user.]]>login
contains.The valid values are:
-
-
-CompanyConstants.AUTH_TYPE_EA
- login
is the
-user's email address
-CompanyConstants.AUTH_TYPE_SN
- login
is the
-user's screen name
-CompanyConstants.AUTH_TYPE_ID
- login
is the
-user's primary key
-password
was null
]]>uuid
attribute), asset category IDs, asset tag names, and expando bridge attributes for the user.]]>uuid
attribute), asset category IDs, asset tag names, and expando bridge attributes for the user.]]>uuid
attribute), asset category IDs, asset tag names, and expando bridge attributes for the user.]]>uuid
attribute), asset category IDs, asset tag names, and expando bridge attributes for the user.]]>false
otherwise]]>false
otherwise]]>false
otherwise]]>uuid
attribute), asset category IDs, asset tag names, and expando bridge attributes for the user.]]>uuid
attribute), asset category IDs, asset tag names, and expando bridge attributes for the user.]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>
-The repositoryId
parameter used by most of the methods is the primary key of the specific repository. If the repository is a default Liferay repository, the repositoryId
is the groupId
or scopeGroupId
. Otherwise, the repositoryId
will correspond to values obtained from {@link RepositoryLocalServiceUtil}.
-
sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal. If it is null
, the sourceFileName
will be used.
-]]>sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal. If it is null
, the sourceFileName
will be used.
-]]>sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal. If it is null
, the sourceFileName
will be used.
-]]>title
, description
, and parameters in the serviceContext
) will be updated.
-
-
-This method takes two file names, the sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal.
-
null
)]]>title
, description
, and parameters in the serviceContext
) will be updated.
-
-
-This method takes two file names, the sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal.
-
null
)]]>title
, description
, and parameters in the serviceContext
) will be updated.
-
-
-This method takes two file names, the sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal.
-
null
)]]>workflowDefinition
appended by the fileEntryTypeId
(optionally 0
).
-The repositoryId
parameter used by most of the methods is the primary key of the specific repository. If the repository is a default Liferay repository, the repositoryId
is the groupId
or scopeGroupId
. Otherwise, the repositoryId
will correspond to values obtained from {@link RepositoryServiceUtil}.
-
sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal. If it is null
, the sourceFileName
will be used.
-]]>sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal. If it is null
, the sourceFileName
will be used.
-]]>sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal. If it is null
, the sourceFileName
will be used.
-]]>portal.properties>.]]>
end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>portal.properties>.]]>
portal.properties>.]]>
portal.properties>.]]>
title
, description
, and parameters in the serviceContext
) will be updated.
-
-
-This method takes two file names, the sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal.
-
null
)]]>title
, description
, and parameters in the serviceContext
) will be updated.
-
-
-This method takes two file names, the sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal.
-
null
)]]>title
, description
, and parameters in the serviceContext
) will be updated.
-
-
-This method takes two file names, the sourceFileName
and the title
. The sourceFileName
corresponds to the name of the actual file being uploaded. The title
corresponds to a name the client wishes to assign this file after it has been uploaded to the portal.
-
null
)]]>workflowDefinition
appended by the fileEntryTypeId
(optionally 0
). false
otherwise]]>false
otherwise]]>name
is a unique identifier for a given file and is generally numeric, whereas the title
is the actual name specified by the user (such as "Budget.xls").
-]]>+Most of the get- methods in this service order activities in descending order by their execution times, so the most recent activities are listed first. +
]]>extraData
in JSON format. For activities affecting another user, a mirror activity is generated that describes the action from the user's point of view. The target user's ID is passed in via the receiverUserId
.
+
+
+
+Example for a mirrored activity:
When a user replies to a message boards post, the reply action is stored in the database with the receiverUserId
being the ID of the author of the original message. The extraData
contains the ID of the original message in JSON format. A mirror activity is generated with the values of the userId
and the receiverUserId
swapped. This mirror activity basically describes a "replied to" event.
+
+Mirror activities are most often used in relation to friend requests and activities. +
]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>
+Useful when paginating results. Returns a maximum of end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+
+Useful when paginating results. Returns a maximum of end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+
end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, <>0 refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>userId
. This method only finds activities without mirrors.
+
+
+Useful when paginating results. Returns a maximum of end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+
userId
. This method only counts activities without mirrors.]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>+The two users participating in the relation are designated as User1 and User2. In case of unidirectional relations User1 should always be the subject of the relation. You can use the following English sentence to find out which user to use as User1 and which to use as User2: +
+ ++User1 is <relation> of User2 (e.g. User1 is parent of User2; User1 is supervisor of User2) +
+ ++For bidirectional relations, the service automatically generates the inverse relation. +
]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>userId1
is User1 of the relation and the user with the primary key userId2
is User2 of the relation.]]>false
otherwise]]>userId1
is User1 of the relation and the user with the primary key userId2
is User2 of the relation.
+
+
+This method returns false
if User1 and User2 are the same, if either user is the default user, or if a matching relation already exists.
+
false
otherwise]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
+]]>false
otherwise]]>false
otherwise]]>-Most of the get- methods in this service order activities in descending order by their execution times, so the most recent activities are listed first. -
]]>extraData
in JSON format. For activities affecting another user, a mirror activity is generated that describes the action from the user's point of view. The target user's ID is passed in via the receiverUserId
.
-
-
-
-Example for a mirrored activity:
When a user replies to a message boards post, the reply action is stored in the database with the receiverUserId
being the ID of the author of the original message. The extraData
contains the ID of the original message in JSON format. A mirror activity is generated with the values of the userId
and the receiverUserId
swapped. This mirror activity basically describes a "replied to" event.
-
-Mirror activities are most often used in relation to friend requests and activities. -
]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>
-Useful when paginating results. Returns a maximum of end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-
-Useful when paginating results. Returns a maximum of end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-
end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, <>0 refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>userId
. This method only finds activities without mirrors.
-
-
-Useful when paginating results. Returns a maximum of end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-
userId
. This method only counts activities without mirrors.]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>-The two users participating in the relation are designated as User1 and User2. In case of unidirectional relations User1 should always be the subject of the relation. You can use the following English sentence to find out which user to use as User1 and which to use as User2: -
- --User1 is <relation> of User2 (e.g. User1 is parent of User2; User1 is supervisor of User2) -
- --For bidirectional relations, the service automatically generates the inverse relation. -
]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>userId1
is User1 of the relation and the user with the primary key userId2
is User2 of the relation.]]>false
otherwise]]>userId1
is User1 of the relation and the user with the primary key userId2
is User2 of the relation.
-
-
-This method returns false
if User1 and User2 are the same, if either user is the default user, or if a matching relation already exists.
-
false
otherwise]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>false
otherwise]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>false
otherwise]]>false
otherwise]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>end - start
instances. start
and end
are not primary keys, they are indexes in the result set. Thus, 0
refers to the first result in the set. Setting both start
and end
to {@link com.liferay.portal.kernel.dao.orm.QueryUtil#ALL_POS} will return the full result set.
-]]>false
otherwise]]>false
otherwise]]>NULL
value. See http://thedailywtf.com/forums/thread/26879.aspx for more information on this nasty bug.]]>changeType
tells if the change happened in source or target. lineNumber
holds the line number of the first modified line. This line number refers to a line in source or target, depending on the changeType
value. changedLines
is a list of strings, each string is a line that is already highlighted, indicating where the changes are.
+]]>"liferayTransactionManager"
.
+]]>