Permission in Application Registry
by Matthew Wringe
I created https://jira.jboss.org/jira/browse/GTNPORTAL-1137 but it seems
like it might be somewhat working depending on what it actually means.
What is the permission setting in application registry suppose to do
actually do? Is it suppose to prevent a user from accessing the content
or to prevent a user from adding that type of portlet to a page?
Each portlet or gadget can specify a 'access permission', but this
doesn't seem to prevent users from viewing the application.
What it does seem to do is if an unauthorized user tries to add this
portlet to a page, they can add the portlet, they just can't view the
added portlet on the page. This doesn't seem like expected behaviour
either.
14 years, 6 months
GateIn extension as war problem
by Vitaly Parfonov
Hi, all!
I have a problem with deploy GateIn extension in tomcat.
My steps:
1. I create ideall-extension.war with next web.xml
<web-app>
<display-name>ideall-extension</display-name>
<filter>
<filter-name>ThreadLocalSessionProviderInitializedFilter</filter-name>
<filter-class>org.exoplatform.frameworks.jcr.web.ThreadLocalSessionProviderInitializedFilter</filter-class>
</filter>
<filter>
<filter-name>SetCurrentIdentityFilter</filter-name>
<filter-class>org.exoplatform.services.security.web.SetCurrentIdentityFilter</filter-class>
</filter>
<filter>
<filter-name>RestEncodingFilter</filter-name>
<filter-class>org.exoplatform.services.rest.servlet.RestEncodingFilter</filter-class>
<init-param>
<param-name>REQUEST_ENCODING</param-name>
<param-value>UTF-8</param-value>
</init-param>
</filter>
<filter-mapping>
<filter-name>ThreadLocalSessionProviderInitializedFilter</filter-name>
<url-pattern>/rest/private/*</url-pattern>
</filter-mapping>
<filter-mapping>
<filter-name>SetCurrentIdentityFilter</filter-name>
<url-pattern>/*</url-pattern>
</filter-mapping>
<filter-mapping>
<filter-name>RestEncodingFilter</filter-name>
<url-pattern>/rest/*</url-pattern>
</filter-mapping>
<!-- END WEBDAV -->
<!--
==================================================================
-->
<!--
LISTENER
-->
<!--
==================================================================
-->
<listener>
<listener-class>org.exoplatform.container.web.PortalContainerConfigOwner</listener-class>
</listener>
<!--
==================================================================
-->
<!--
SERVLET
-->
<!--
==================================================================
-->
<servlet>
<servlet-name>GateInServlet</servlet-name>
<servlet-class>org.gatein.wci.api.GateInServlet</servlet-class>
<load-on-startup>0</load-on-startup>
</servlet>
<!-- WEBDAV -->
<servlet>
<servlet-name>RestServer</servlet-name>
<description>eXo - Platform REST Server</description>
<servlet-class>org.exoplatform.services.rest.servlet.RestServlet</servlet-class>
<load-on-startup>4</load-on-startup>
</servlet>
<!-- END WEBDAV -->
<!--
=================================================================
-->
<servlet-mapping>
<servlet-name>GateInServlet</servlet-name>
<url-pattern>/gateinservlet</url-pattern>
</servlet-mapping>
<!-- WEBDAV -->
<servlet-mapping>
<servlet-name>RestServer</servlet-name>
<url-pattern>/rest/private/*</url-pattern>
</servlet-mapping>
</web-app>
2. Create exo.ideall.extension.config-1.0-SNAPSHOT.jar with next
configuration.xml file
<?xml version="1.0" encoding="UTF-8"?>
<configuration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.exoplaform.org/xml/ns/kernel_1_0.xsd
http://www.exoplaform.org/xml/ns/kernel_1_0.xsd"
xmlns="http://www.exoplaform.org/xml/ns/kernel_1_0.xsd">
<external-component-plugins>
<!-- The full qualified name of the PortalContainerConfig -->
<target-component>org.exoplatform.container.definition.PortalContainerConfig
</target-component>
<component-plugin>
<!-- The name of the plugin -->
<name>Add PortalContainer Definitions</name>
<!--
The name of the method to call on the PortalContainerConfig in order
to register the PortalContainerDefinitions
-->
<set-method>registerPlugin</set-method>
<!-- The full qualified name of the PortalContainerDefinitionPlugin -->
<type>org.exoplatform.container.definition.PortalContainerDefinitionPlugin
</type>
<init-params>
<object-param>
<name>portal</name>
<object
type="org.exoplatform.container.definition.PortalContainerDefinition">
<!-- The name of the portal container -->
<field name="name">
<string>portal</string>
</field>
<!-- The name of the context name of the rest web application -->
<field name="restContextName">
<string>rest</string>
</field>
<!-- The name of the realm -->
<field name="realmName">
<string>exo-domain</string>
</field>
<!--
All the dependencies of the portal container ordered by loading
priority
-->
<field name="dependencies">
<collection type="java.util.ArrayList">
<value>
<string>eXoResources</string>
</value>
<value>
<string>portal</string>
</value>
<value>
<string>dashboard</string>
</value>
<value>
<string>exoadmin</string>
</value>
<value>
<string>eXoGadgets</string>
</value>
<value>
<string>eXoGadgetServer</string>
</value>
<value>
<string>rest</string>
</value>
<value>
<string>web</string>
</value>
<value>
<string>ideall-extension</string>
</value>
</collection>
</field>
</object>
</object-param>
</init-params>
</component-plugin>
</external-component-plugins>
</configuration>
3. Then i run tomcat i get exception
SEVERE: Exception sending context initialized event to listener
instance of class
org.exoplatform.container.web.PortalContainerConfigOwner
java.lang.IllegalStateException: No pre init tasks can be added to the
portal container 'portal', because it has already been initialized.
Check the webapp 'ideall-extension'
<------>at org.exoplatform.container.RootContainer$PortalContainerPreInitTask.onAlreadyExists(RootContainer.java:724)
<------>at org.exoplatform.container.RootContainer.addInitTask(RootContainer.java:542)
<------>at org.exoplatform.container.PortalContainer.addInitTask(PortalContainer.java:387)
<------>at org.exoplatform.container.PortalContainer.addInitTask(PortalContainer.java:361)
<------>at org.exoplatform.container.web.PortalContainerConfigOwner.contextInitialized(PortalContainerConfigOwner.java:57)
<------>at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3972)
<------>at org.apache.catalina.core.StandardContext.start(StandardContext.java:4467)
<------>at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
<------>at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
<------>at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
<------>at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:905)
<------>at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:740)
<------>at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:500)
<------>at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
<------>at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321)
<------>at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
<------>at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
<------>at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
<------>at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
<------>at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
<------>at org.apache.catalina.core.StandardService.start(StandardService.java:516)
<------>at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
<------>at org.apache.catalina.startup.Catalina.start(Catalina.java:593)
<------>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
<------>at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
<------>at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
<------>at java.lang.reflect.Method.invoke(Method.java:597)
<------>at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
<------>at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
I use GateIn 3.0-GA
Server version: Apache Tomcat/6.0.24
Server built: January 19 2010 1439
Server number: 6.0.0.0
OS Name: Linux
OS Version: 2.6.31.12-0.2-desktop
Architecture: i386
JVM Version: 1.6.0_13-b03
JVM Vendor: Sun Microsystems Inc.
Please help me. That i do wrong.
--
Best regards,
Vitaly
14 years, 7 months
GateIn and cross context sessions
by Matthew Wringe
An issue was brought up lately with cross context sessions not working
properly (https://jira.jboss.org/jira/browse/GTNWCI-15, note that its
not really a wci issue and should probably be moved to the gatein pc
integration component)
We have a test^1 in the pc (portlet container) component for cross
context session sharing. For this test to pass we need to make a change
in the JBoss server configuration files^2. But we don't need to make any
changes for Tomcat.
On GateIn its a bit of a different situation. If we make the
configuration change for JBoss^2, then the example in GTNWCI-15 works.
But it doesn't work for Tomcat.
Looking into gtn a bit more, the session in GateIn is coming from the
server (with context path /portal) and not from the context path of the
portlet. In the pc test the session context path is the same as the
portlet.
I can get this to work on Tomcat if I make a change to the http
connector to use emptySessionPath="true"^3.
Do we actually need to make there configuration changes, or I am missing
something and we need to change how the portal and portlet container are
integrated.
Thanks
1)
http://anonsvn.jboss.org/repos/gatein/components/pc/trunk/test/src/test/j...
2)we need to add <SessionCookie path="/"/> in the server context.xml,
this is being done in the pc tests and should have been setup in gatein
at the beginning, but I don't see in gatein anymore. We should add this
option.
3)http://tomcat.apache.org/tomcat-6.0-doc/config/http.html as mention
here that its useful for portlet specification implementations, but I
don't know if we actually need it or not.
14 years, 7 months
WebUI refresh
by Thomas Heute
Tried but failed...
Anyone would know how to refresh the captcha generated image on failure ?
I didn't manage to tell WebUI to refresh the image (which is basically a
link to a servlet)
Thanks for your help,
Thomas
14 years, 7 months
http-equiv metadata extraction from a content
by Luca Stancapiano
I've seen that if we insert some metadata in our document as:
<meta http-equiv="File-NodeType" content="my_ns:my_resource" />
and we upload it through webdav or ftp never happens.
I expect an extraction of theese metadas inside the http headers list. To
implement this feature you could add a read during the creation of the
org.exoplatform.services.rest.impl.ContainerRequest instance.
Here an example:
public ContainerRequest(String method,
URI requestUri,
URI baseUri,
InputStream entityStream,
MultivaluedMap<String, String>
httpHeaders)
{
this.method = method;
this.requestUri = requestUri;
this.baseUri = baseUri;
this.entityStream = entityStream;
this.httpHeaders = httpHeaders;
String[] headersFromContent =
this.reader.read(entityStream, httpHeaders);
}
this reader could extract the 'http-equiv' inside the content and tail in
the httpHeaders
14 years, 7 months
Re: [gatein-dev] http-equiv metadata extraction from a content
by Nicolas Filotto
Thank you very much for this critical information, I will send an email
right now to ask the JIRA Admin to check it, I hope it will be solved soon.
On Fri, Apr 16, 2010 at 10:21 AM, Luca Stancapiano <
l.stancapiano(a)sourcesense.com> wrote:
> one week about... maybe some permission changed?
>
>
> On Fri, Apr 16, 2010 at 9:08 AM, Nicolas Filotto <
> nicolas.filotto(a)exoplatform.com> wrote:
>
>> Since when you cannot create any issue in eXo JCR project?
>>
>>
>> On Fri, Apr 16, 2010 at 9:55 AM, Luca Stancapiano <
>> l.stancapiano(a)sourcesense.com> wrote:
>>
>>> Itried but I have this error when I create an issue in the exo-jcr
>>> project:
>>>
>>> *Step 2 of 2*: Enter the details of the issue...
>>> Errors
>>>
>>> - Error occurred while storing issue.
>>>
>>>
>>>
>>> On Fri, Apr 16, 2010 at 8:47 AM, Nicolas Filotto <
>>> nicolas.filotto(a)exoplatform.com> wrote:
>>>
>>>> Hi Luca,
>>>>
>>>> Could you please, create the related JIRA in the eXo JCR project (
>>>> https://jira.jboss.org/jira/browse/EXOJCR). We will see what we can do.
>>>>
>>>> Thank you in advance,
>>>> Nicolas
>>>>
>>>> On Fri, Apr 9, 2010 at 4:00 PM, Luca Stancapiano <
>>>> l.stancapiano(a)sourcesense.com> wrote:
>>>>
>>>>> I've seen that if we insert some metadata in our document as:
>>>>>
>>>>> <meta http-equiv="File-NodeType" content="my_ns:my_resource" />
>>>>>
>>>>> and we upload it through webdav or ftp never happens.
>>>>>
>>>>> I expect an extraction of theese metadas inside the http headers list.
>>>>> To implement this feature you could add a read during the creation of the
>>>>> org.exoplatform.services.rest.impl.ContainerRequest instance.
>>>>>
>>>>> Here an example:
>>>>>
>>>>> public ContainerRequest(String method,
>>>>> URI requestUri,
>>>>> URI baseUri,
>>>>> InputStream
>>>>> entityStream,
>>>>> MultivaluedMap<String,
>>>>> String> httpHeaders)
{
>>>>> this.method = method;
>>>>> this.requestUri = requestUri;
>>>>> this.baseUri = baseUri;
>>>>> this.entityStream = entityStream;
>>>>> this.httpHeaders = httpHeaders;
>>>>>
>>>>> String[] headersFromContent =
>>>>> this.reader.read(entityStream, httpHeaders);
>>>>>
>>>>> }
>>>>>
>>>>> this reader could extract the 'http-equiv' inside the content and tail
>>>>> in the httpHeaders
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> gatein-dev mailing list
>>>>> gatein-dev(a)lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/gatein-dev
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Nicolas Filotto
>>>> JCR Product Manager
>>>> Project Manager
>>>> eXo Platform SAS
>>>> nicolas.filotto(a)exoplatform.com
>>>> +33 (0)6 31 32 92 19
>>>>
>>>
>>>
>>
>>
>> --
>> Nicolas Filotto
>> JCR Product Manager
>> Project Manager
>> eXo Platform SAS
>> nicolas.filotto(a)exoplatform.com
>> +33 (0)6 31 32 92 19
>>
>
>
--
Nicolas Filotto
JCR Product Manager
Project Manager
eXo Platform SAS
nicolas.filotto(a)exoplatform.com
+33 (0)6 31 32 92 19
14 years, 7 months
Re: [gatein-dev] http-equiv metadata extraction from a content
by Nicolas Filotto
Since when you cannot create any issue in eXo JCR project?
On Fri, Apr 16, 2010 at 9:55 AM, Luca Stancapiano <
l.stancapiano(a)sourcesense.com> wrote:
> Itried but I have this error when I create an issue in the exo-jcr project:
>
> *Step 2 of 2*: Enter the details of the issue...
> Errors
>
> - Error occurred while storing issue.
>
>
>
> On Fri, Apr 16, 2010 at 8:47 AM, Nicolas Filotto <
> nicolas.filotto(a)exoplatform.com> wrote:
>
>> Hi Luca,
>>
>> Could you please, create the related JIRA in the eXo JCR project (
>> https://jira.jboss.org/jira/browse/EXOJCR). We will see what we can do.
>>
>> Thank you in advance,
>> Nicolas
>>
>> On Fri, Apr 9, 2010 at 4:00 PM, Luca Stancapiano <
>> l.stancapiano(a)sourcesense.com> wrote:
>>
>>> I've seen that if we insert some metadata in our document as:
>>>
>>> <meta http-equiv="File-NodeType" content="my_ns:my_resource" />
>>>
>>> and we upload it through webdav or ftp never happens.
>>>
>>> I expect an extraction of theese metadas inside the http headers list. To
>>> implement this feature you could add a read during the creation of the
>>> org.exoplatform.services.rest.impl.ContainerRequest instance.
>>>
>>> Here an example:
>>>
>>> public ContainerRequest(String method,
>>> URI requestUri,
>>> URI baseUri,
>>> InputStream
>>> entityStream,
>>> MultivaluedMap<String,
>>> String> httpHeaders)
{
>>> this.method = method;
>>> this.requestUri = requestUri;
>>> this.baseUri = baseUri;
>>> this.entityStream = entityStream;
>>> this.httpHeaders = httpHeaders;
>>>
>>> String[] headersFromContent =
>>> this.reader.read(entityStream, httpHeaders);
>>>
>>> }
>>>
>>> this reader could extract the 'http-equiv' inside the content and tail in
>>> the httpHeaders
>>>
>>>
>>> _______________________________________________
>>> gatein-dev mailing list
>>> gatein-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/gatein-dev
>>>
>>>
>>
>>
>> --
>> Nicolas Filotto
>> JCR Product Manager
>> Project Manager
>> eXo Platform SAS
>> nicolas.filotto(a)exoplatform.com
>> +33 (0)6 31 32 92 19
>>
>
>
--
Nicolas Filotto
JCR Product Manager
Project Manager
eXo Platform SAS
nicolas.filotto(a)exoplatform.com
+33 (0)6 31 32 92 19
14 years, 7 months
