Re: [Trinidad] I updated the Trinidad site (browsers.xml), any one know how to get it updated on the web?
nightly is on hudson. the side build is still on continuum, as porting it to hudson is not straightforward - at least it requires some work... -Matthias On Thu, Oct 28, 2010 at 5:41 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: I thought that continuum was discontinued and we are supposed to be using hudson now. Is this not true? On Thu, Oct 28, 2010 at 6:00 AM, Matthias Wessendorf mat...@apache.org wrote: The continuum (that publishes the site) is down. You could manually replace the file on the server, in the meantime -Matthias On Wed, Oct 27, 2010 at 10:57 PM, Andrew Robinson arobinso...@apache.org wrote: Looks like the trinidad pom file is wrong and still lists continuum as the continuous integration piece in the pom.xml. I do not see where on hudson that the Trinidad site is listed as a project. Anyone know how to get the site re-deployed? Also anyone know the correct URL for hudson in the pom.xml? It is currently: ciManagement systemcontinuum/system urlhttp://myfaces.zones.apache.org:8080/continuum/url notifiers notifier typemail/type sendOnSuccesstrue/sendOnSuccess configuration addresscomm...@myfaces.apache.org/address /configuration /notifier /notifiers /ciManagement Thanks, Andrew -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [Trinidad] I updated the Trinidad site (browsers.xml), any one know how to get it updated on the web?
On Fri, Oct 29, 2010 at 9:47 AM, Matthias Wessendorf mat...@apache.org wrote: nightly is on hudson. the side build is still on continuum, as porting it to hudson is not straightforward - at least it requires some work... http://markmail.org/message/pmhdwqxifruc7thd also, please see: https://issues.apache.org/jira/browse/PDFBOX-623 -Matthias On Thu, Oct 28, 2010 at 5:41 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: I thought that continuum was discontinued and we are supposed to be using hudson now. Is this not true? On Thu, Oct 28, 2010 at 6:00 AM, Matthias Wessendorf mat...@apache.org wrote: The continuum (that publishes the site) is down. You could manually replace the file on the server, in the meantime -Matthias On Wed, Oct 27, 2010 at 10:57 PM, Andrew Robinson arobinso...@apache.org wrote: Looks like the trinidad pom file is wrong and still lists continuum as the continuous integration piece in the pom.xml. I do not see where on hudson that the Trinidad site is listed as a project. Anyone know how to get the site re-deployed? Also anyone know the correct URL for hudson in the pom.xml? It is currently: ciManagement systemcontinuum/system urlhttp://myfaces.zones.apache.org:8080/continuum/url notifiers notifier typemail/type sendOnSuccesstrue/sendOnSuccess configuration addresscomm...@myfaces.apache.org/address /configuration /notifier /notifiers /ciManagement Thanks, Andrew -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Resolved: (TRINIDAD-1890) NullPointerException when using file upload with trinidad
[ https://issues.apache.org/jira/browse/TRINIDAD-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias Weßendorf resolved TRINIDAD-1890. -- Resolution: Cannot Reproduce Assignee: Matthias Weßendorf NullPointerException when using file upload with trinidad - Key: TRINIDAD-1890 URL: https://issues.apache.org/jira/browse/TRINIDAD-1890 Project: MyFaces Trinidad Issue Type: Bug Environment: Linux x64 Java 1.6 Reporter: Thomas Müller Assignee: Matthias Weßendorf Hi, I tried to use the file upload in trinidad. When I want to submit a file, I get ther following exception: java.lang.NullPointerException org.apache.myfaces.trinidadinternal.config.upload.UploadRequestWrapper.setCharacterEncoding(UploadRequestWrapper.java:83) com.sun.faces.context.ExternalContextImpl.setRequestCharacterEncoding(ExternalContextImpl.java:165) org.apache.myfaces.trinidad.context.ExternalContextDecorator.setRequestCharacterEncoding(ExternalContextDecorator.java:266) org.apache.myfaces.trinidad.context.ExternalContextDecorator.setRequestCharacterEncoding(ExternalContextDecorator.java:266) javax.faces.application.ViewHandler.initView(ViewHandler.java:270) com.sun.faces.application.ViewHandlerImpl.initView(ViewHandlerImpl.java:119) javax.faces.application.ViewHandlerWrapper.initView(ViewHandlerWrapper.java:175) com.sun.faces.lifecycle.RestoreViewPhase.doPhase(RestoreViewPhase.java:102) com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118) javax.faces.webapp.FacesServlet.service(FacesServlet.java:265) Can you help me if this is a bug or something is wrong in my enviroment properties? web.xml: ?xml version=1.0 encoding=UTF-8? web-app id=WebApp_ID version=2.5 xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd; display-namepferdemarkt.tv/display-name welcome-file-list welcome-fileindex.html/welcome-file welcome-fileindex.htm/welcome-file welcome-fileindex.jsp/welcome-file welcome-filedefault.html/welcome-file welcome-filedefault.htm/welcome-file welcome-filedefault.jsp/welcome-file /welcome-file-list jsp-config jsp-property-group url-pattern*.jsp/url-pattern url-pattern*.jspf/url-pattern page-encodingUTF-8/page-encoding scripting-invalidtrue/scripting-invalid is-xmltrue/is-xml /jsp-property-group /jsp-config context-param param-namejavax.faces.STATE_SAVING_METHOD/param-name param-valueclient/param-value /context-param context-param param-namecom.sun.faces.enableLazyBeanValidation/param-name param-valuefalse/param-value /context-param context-param param-namecom.sun.faces.validateXml/param-name param-valuefalse/param-value /context-param context-param param-namecom.sun.faces.verifyObjects/param-name param-valuefalse/param-value /context-param context-param !-- Maximum memory per request (in bytes) -- param-nameorg.apache.myfaces.trinidad.UPLOAD_MAX_MEMORY/param-name !-- Use 500K -- param-value512000/param-value /context-param context-param !-- Maximum disk space per request (in bytes) -- param-nameorg.apache.myfaces.trinidad.UPLOAD_MAX_DISK_SPACE/param-name !-- Use 5,000K -- param-value512/param-value /context-param context-param !-- directory to store temporary files -- param-nameorg.apache.myfaces.trinidad.UPLOAD_TEMP_DIR/param-name !-- Use a TrinidadUploads subdirectory of /tmp -- param-value/tmp//param-value /context-param !-- Faces Servlet -- servlet servlet-nameFaces Servlet/servlet-name servlet-classjavax.faces.webapp.FacesServlet/servlet-class load-on-startup1/load-on-startup /servlet servlet-mapping servlet-nameFaces Servlet/servlet-name url-pattern*.html/url-pattern /servlet-mapping filter filter-nametrinidad/filter-name filter-classorg.apache.myfaces.trinidad.webapp.TrinidadFilter/filter-class /filter filter-mapping filter-nametrinidad/filter-name !-- This assumes that the FacesServlet has been registered -- !-- under the name faces -- servlet-namefaces/servlet-name /filter-mapping servlet servlet-nameresources/servlet-name servlet-classorg.apache.myfaces.trinidad.webapp.ResourceServlet/servlet-class /servlet !-- This cannot be configured currently -- servlet-mapping servlet-nameresources/servlet-name url-pattern/adf/*/url-pattern /servlet-mapping /web-app faces-config.xml: ?xml version=1.0
[jira] Commented: (TRINIDAD-1586) The tr:inputFile input box is not disabled on Internet Explorer.
[ https://issues.apache.org/jira/browse/TRINIDAD-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12926207#action_12926207 ] Matthias Weßendorf commented on TRINIDAD-1586: -- what IE version are you on ? The tr:inputFile input box is not disabled on Internet Explorer. --- Key: TRINIDAD-1586 URL: https://issues.apache.org/jira/browse/TRINIDAD-1586 Project: MyFaces Trinidad Issue Type: Bug Components: Components Affects Versions: 1.0.10-core Environment: Chordiant Foundation server 6.3.1 Reporter: Prasanna Original Estimate: 24h Remaining Estimate: 24h Hi, I am using trinidad-api-1.0.10.jar, trinidad-impl-1.0.10.jar. In the application i am using tr:inputFile Input box is not disabled in IE browser. So any user can enter text, which is not valid file path in this field. Sytem gets hanged even if we remove the enterd field. Please help me out to resolve this problem. It oes not allow to proceed with rthe application. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1096) IE 7 Support
[ https://issues.apache.org/jira/browse/TRINIDAD-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12926208#action_12926208 ] Matthias Weßendorf commented on TRINIDAD-1096: -- can you add more details ? probably a better way is to create a single ticket per issue IE 7 Support Key: TRINIDAD-1096 URL: https://issues.apache.org/jira/browse/TRINIDAD-1096 Project: MyFaces Trinidad Issue Type: Bug Affects Versions: 1.2.7-core Environment: JBoss 4.3 GA CP 01 Reporter: selvaraju perumal We are using trinidad 1.2.7 with JBoss 4.3 GA CP01. We have a problem in supporting browser IE 7. We have functionality like opening a pop up window and having the parent as molded. The issue is when we move the mouse pointer from child window to the parent, mouse pointer displays as busy (i.e changes to busy icon). Anybody have this issue or tried with IE7. Regards, Selva -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
MYFACES-2952 - Improve Atmosphere Meteor support of MyFaces
Currently MyFaces stops initializing when there is no (My)FacesServlet
configured in the (present) web.xml.
I am sure this is in 99.99% of all cases right. However there is a
chance that a wrapping framework will
instantiate the (My)FacesServlet, inside a wrapping Servlet.
An example of that is the WebSocket/Comet Framework Atmosphere.
As mentioned in [1] a typical configuration looks like:
servlet
descriptionMeteorServlet/description
servlet-nameMeteorServlet/servlet-name
servlet-classorg.atmosphere.cpr.MeteorServlet/servlet-class
init-param
param-nameorg.atmosphere.servlet/param-name
param-valuejavax.faces.webapp.FacesServlet/param-value
/init-param
init-param
param-nameorg.atmosphere.useWebSocket/param-name
param-valuetrue/param-value
/init-param
init-param
param-nameorg.atmosphere.useNative/param-name
param-valuetrue/param-value
/init-param
/servlet
So in order to enable the AbstractFacesInitializer.java to see that it
can continue the initialization work, I thought about adding the
following to shared WebXml.java:
Index: src/main/java/org/apache/myfaces/shared/webapp/webxml/WebXml.java
===
--- src/main/java/org/apache/myfaces/shared/webapp/webxml/WebXml.java
(revision
1028633)
+++ src/main/java/org/apache/myfaces/shared/webapp/webxml/WebXml.java (working
copy)
@@ -107,6 +107,11 @@
public abstract boolean isErrorPagePresent();
/**
+ * Determines, if the web.xml contains the Atmosphere Meteor Servlet
+ */
+public abstract boolean isAtmosphereMeteorServletPresent();
+
+/**
* Returns true if the given servlet class is a valid FacesServlet.
* This is the FacesServlet itself or any DelegatedFacesServlet.
*
The AbstractFacesInitializer would be changed to something like:
Index:
impl/src/main/java/org/apache/myfaces/webapp/AbstractFacesInitializer.java
===
--- impl/src/main/java/org/apache/myfaces/webapp/AbstractFacesInitializer.java
(revision
1028633)
+++ impl/src/main/java/org/apache/myfaces/webapp/AbstractFacesInitializer.java
(working
copy)
@@ -79,6 +79,7 @@
* application.
*/
public void initFaces(ServletContext servletContext) {
+
try {
if (log.isLoggable(Level.FINEST)) {
log.finest(Initializing MyFaces);
@@ -102,7 +103,9 @@
}
return;
-} else if (webXml.getFacesServletMappings().isEmpty()) {
+} else if (webXml.getFacesServletMappings().isEmpty()
!webXml.isAtmosphereMeteorServletPresent()) {
+// IF the
+
// check if the FacesServlet has been added dynamically
// in a Servlet 3.0 environment by MyFacesContainerInitializer
Boolean mappingAdded = (Boolean)
servletContext.getAttribute(FACES_SERVLET_ADDED_ATTRIBUTE);
What do you think?
Noteof course - today we have Atmoshpere, tomorrow we may have
different use cases to see if a different Servlet (and/or Filter) is
present.
Hence we could have something like instead:
WebXml_API
public abstract boolean containsServlet(String fullQualifiedClassName);
/WebXml_API
(we want String here, since (with Atmosphere) we can't compile against
it (-(L)GPL))... but we can use the String-based name
as a constant in our code)
Oh yes... a similar change would be needed for the
MyFacesContainerInitializer.java from our implee6 module.
-Matthias
[1] https://issues.apache.org/jira/browse/MYFACES-2952
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: MYFACES-2952 - Improve Atmosphere Meteor support of MyFaces
Or a ctx param : o.a.m.INIT_ALWAYS
default = false
sent from my Android phone
On Oct 29, 2010 12:41 PM, Matthias Wessendorf mat...@apache.org wrote:
Currently MyFaces stops initializing when there is no (My)FacesServlet
configured in the (present) web.xml.
I am sure this is in 99.99% of all cases right. However there is a
chance that a wrapping framework will
instantiate the (My)FacesServlet, inside a wrapping Servlet.
An example of that is the WebSocket/Comet Framework Atmosphere.
As mentioned in [1] a typical configuration looks like:
servlet
descriptionMeteorServlet/description
servlet-nameMeteorServlet/servlet-name
servlet-classorg.atmosphere.cpr.MeteorServlet/servlet-class
init-param
param-nameorg.atmosphere.servlet/param-name
param-valuejavax.faces.webapp.FacesServlet/param-value
/init-param
init-param
param-nameorg.atmosphere.useWebSocket/param-name
param-valuetrue/param-value
/init-param
init-param
param-nameorg.atmosphere.useNative/param-name
param-valuetrue/param-value
/init-param
/servlet
So in order to enable the AbstractFacesInitializer.java to see that it
can continue the initialization work, I thought about adding the
following to shared WebXml.java:
Index: src/main/java/org/apache/myfaces/shared/webapp/webxml/WebXml.java
===
--- src/main/java/org/apache/myfaces/shared/webapp/webxml/WebXml.java
(revision
1028633)
+++ src/main/java/org/apache/myfaces/shared/webapp/webxml/WebXml.java
(working
copy)
@@ -107,6 +107,11 @@
public abstract boolean isErrorPagePresent();
/**
+ * Determines, if the web.xml contains the Atmosphere Meteor Servlet
+ */
+ public abstract boolean isAtmosphereMeteorServletPresent();
+
+ /**
* Returns true if the given servlet class is a valid FacesServlet.
* This is the FacesServlet itself or any DelegatedFacesServlet.
*
The AbstractFacesInitializer would be changed to something like:
Index:
impl/src/main/java/org/apache/myfaces/webapp/AbstractFacesInitializer.java
===
---
impl/src/main/java/org/apache/myfaces/webapp/AbstractFacesInitializer.java
(revision
1028633)
+++
impl/src/main/java/org/apache/myfaces/webapp/AbstractFacesInitializer.java
(working
copy)
@@ -79,6 +79,7 @@
* application.
*/
public void initFaces(ServletContext servletContext) {
+
try {
if (log.isLoggable(Level.FINEST)) {
log.finest(Initializing MyFaces);
@@ -102,7 +103,9 @@
}
return;
- } else if (webXml.getFacesServletMappings().isEmpty()) {
+ } else if (webXml.getFacesServletMappings().isEmpty()
!webXml.isAtmosphereMeteorServletPresent()) {
+ // IF the
+
// check if the FacesServlet has been added dynamically
// in a Servlet 3.0 environment by MyFacesContainerInitializer
Boolean mappingAdded = (Boolean)
servletContext.getAttribute(FACES_SERVLET_ADDED_ATTRIBUTE);
What do you think?
Noteof course - today we have Atmoshpere, tomorrow we may have
different use cases to see if a different Servlet (and/or Filter) is
present.
Hence we could have something like instead:
WebXml_API
public abstract boolean containsServlet(String fullQualifiedClassName);
/WebXml_API
(we want String here, since (with Atmosphere) we can't compile against
it (-(L)GPL))... but we can use the String-based name
as a constant in our code)
Oh yes... a similar change would be needed for the
MyFacesContainerInitializer.java from our implee6 module.
-Matthias
[1] https://issues.apache.org/jira/browse/MYFACES-2952
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
Re: MYFACES-2952 - Improve Atmosphere Meteor support of MyFaces
+1 for: Or a ctx param : o.a.m.INIT_ALWAYS.
Nothing meteor-specific, I would say.
best regards,
Martin
On 10/29/10, Matthias Wessendorf mat...@apache.org wrote:
Or a ctx param : o.a.m.INIT_ALWAYS
default = false
sent from my Android phone
On Oct 29, 2010 12:41 PM, Matthias Wessendorf mat...@apache.org wrote:
Currently MyFaces stops initializing when there is no (My)FacesServlet
configured in the (present) web.xml.
I am sure this is in 99.99% of all cases right. However there is a
chance that a wrapping framework will
instantiate the (My)FacesServlet, inside a wrapping Servlet.
An example of that is the WebSocket/Comet Framework Atmosphere.
As mentioned in [1] a typical configuration looks like:
servlet
descriptionMeteorServlet/description
servlet-nameMeteorServlet/servlet-name
servlet-classorg.atmosphere.cpr.MeteorServlet/servlet-class
init-param
param-nameorg.atmosphere.servlet/param-name
param-valuejavax.faces.webapp.FacesServlet/param-value
/init-param
init-param
param-nameorg.atmosphere.useWebSocket/param-name
param-valuetrue/param-value
/init-param
init-param
param-nameorg.atmosphere.useNative/param-name
param-valuetrue/param-value
/init-param
/servlet
So in order to enable the AbstractFacesInitializer.java to see that it
can continue the initialization work, I thought about adding the
following to shared WebXml.java:
Index: src/main/java/org/apache/myfaces/shared/webapp/webxml/WebXml.java
===
--- src/main/java/org/apache/myfaces/shared/webapp/webxml/WebXml.java
(revision
1028633)
+++ src/main/java/org/apache/myfaces/shared/webapp/webxml/WebXml.java
(working
copy)
@@ -107,6 +107,11 @@
public abstract boolean isErrorPagePresent();
/**
+ * Determines, if the web.xml contains the Atmosphere Meteor Servlet
+ */
+ public abstract boolean isAtmosphereMeteorServletPresent();
+
+ /**
* Returns true if the given servlet class is a valid FacesServlet.
* This is the FacesServlet itself or any DelegatedFacesServlet.
*
The AbstractFacesInitializer would be changed to something like:
Index:
impl/src/main/java/org/apache/myfaces/webapp/AbstractFacesInitializer.java
===
---
impl/src/main/java/org/apache/myfaces/webapp/AbstractFacesInitializer.java
(revision
1028633)
+++
impl/src/main/java/org/apache/myfaces/webapp/AbstractFacesInitializer.java
(working
copy)
@@ -79,6 +79,7 @@
* application.
*/
public void initFaces(ServletContext servletContext) {
+
try {
if (log.isLoggable(Level.FINEST)) {
log.finest(Initializing MyFaces);
@@ -102,7 +103,9 @@
}
return;
- } else if (webXml.getFacesServletMappings().isEmpty()) {
+ } else if (webXml.getFacesServletMappings().isEmpty()
!webXml.isAtmosphereMeteorServletPresent()) {
+ // IF the
+
// check if the FacesServlet has been added dynamically
// in a Servlet 3.0 environment by MyFacesContainerInitializer
Boolean mappingAdded = (Boolean)
servletContext.getAttribute(FACES_SERVLET_ADDED_ATTRIBUTE);
What do you think?
Noteof course - today we have Atmoshpere, tomorrow we may have
different use cases to see if a different Servlet (and/or Filter) is
present.
Hence we could have something like instead:
WebXml_API
public abstract boolean containsServlet(String fullQualifiedClassName);
/WebXml_API
(we want String here, since (with Atmosphere) we can't compile against
it (-(L)GPL))... but we can use the String-based name
as a constant in our code)
Oh yes... a similar change would be needed for the
MyFacesContainerInitializer.java from our implee6 module.
-Matthias
[1] https://issues.apache.org/jira/browse/MYFACES-2952
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
--
http://www.irian.at
Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German
Professional Support for Apache MyFaces
[site] Branding requirements
All Apache projects have been asked to abide by these foundation-wide guidelines [1]. Having a quick look down the list of things that are expected, it seems we have a few site patches to make. [1] http://www.apache.org/foundation/marks/pmcs -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
Re: [site] Branding requirements
E.g. -CWiki link missing -check trademark -Foundation: License and Security are missing -Trademark Attributions = to be done... -Logos And Graphics = To be changed... -Powered By... Logos = Do we have those ? -Matthias On Fri, Oct 29, 2010 at 1:24 PM, Matthias Wessendorf mat...@apache.org wrote: All Apache projects have been asked to abide by these foundation-wide guidelines [1]. Having a quick look down the list of things that are expected, it seems we have a few site patches to make. [1] http://www.apache.org/foundation/marks/pmcs -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Resolved: (TRINIDAD-1798) XSS attack while launching Pop up
[
https://issues.apache.org/jira/browse/TRINIDAD-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf resolved TRINIDAD-1798.
--
Resolution: Fixed
Fix Version/s: 2.0.0.4-core
1.2.15-core
Assignee: Matthias Weßendorf
XSS attack while launching Pop up
-
Key: TRINIDAD-1798
URL: https://issues.apache.org/jira/browse/TRINIDAD-1798
Project: MyFaces Trinidad
Issue Type: Bug
Affects Versions: 1.2.9-core
Reporter: Virginie reverse
Assignee: Matthias Weßendorf
Priority: Critical
Fix For: 1.2.15-core , 2.0.0.4-core
hello,
I am using Tinidad 1.2.9, JSF 1.2 and tomcat 5.5.26.
I am launching a pop up with this command :
tr:commandLink id=idAddCurrencyDialog
text=#{msg.updateAttributes_add_currency}
action=dialog:addModifyAttribute useWindow=true partialSubmit=true
launchListener=#{updateAttributesController.launchAddCurrencyDialog}
returnListener=#{updateAttributesController.returnFromDialogAttribute}
windowHeight=500 windowWidth=500/
Here is the command generated :
https://xxx/yyy/faces/__ADFv__?_afPfm=-543e4359_t=fred_vir=/common/pages/secure/common/dialog/addModifyAttribute.jspxloc=en_minWidth=500_minHeight=500_rtrnId=1
The problem is that it's allowing cross site script attack , you can insert
javascript in the :
_minWidth, _minHeight or_rtrnId
For exple :
https://xxx//faces/__ADFv__?_afPfm=-543e4359_t=fred_vir=/common/pages/secure/common/dialog/addModifyAttribute.jspxloc=en_minWidth=500_minHeight=500});alert(document.cookie);//_rtrnId=1
I tried to upgrade to 1.2.13, but there was still the problem.
Do you know a work around or is it possible to fix this security breach ?
thxs
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [Trinidad] I updated the Trinidad site (browsers.xml), any one know how to get it updated on the web?
Andrew, as a quick fix, I am building site locally and will replace the browsers.html output on the server, later today -M On Fri, Oct 29, 2010 at 9:49 AM, Matthias Wessendorf mat...@apache.org wrote: On Fri, Oct 29, 2010 at 9:47 AM, Matthias Wessendorf mat...@apache.org wrote: nightly is on hudson. the side build is still on continuum, as porting it to hudson is not straightforward - at least it requires some work... http://markmail.org/message/pmhdwqxifruc7thd also, please see: https://issues.apache.org/jira/browse/PDFBOX-623 -Matthias On Thu, Oct 28, 2010 at 5:41 PM, Andrew Robinson andrew.rw.robin...@gmail.com wrote: I thought that continuum was discontinued and we are supposed to be using hudson now. Is this not true? On Thu, Oct 28, 2010 at 6:00 AM, Matthias Wessendorf mat...@apache.org wrote: The continuum (that publishes the site) is down. You could manually replace the file on the server, in the meantime -Matthias On Wed, Oct 27, 2010 at 10:57 PM, Andrew Robinson arobinso...@apache.org wrote: Looks like the trinidad pom file is wrong and still lists continuum as the continuous integration piece in the pom.xml. I do not see where on hudson that the Trinidad site is listed as a project. Anyone know how to get the site re-deployed? Also anyone know the correct URL for hudson in the pom.xml? It is currently: ciManagement systemcontinuum/system urlhttp://myfaces.zones.apache.org:8080/continuum/url notifiers notifier typemail/type sendOnSuccesstrue/sendOnSuccess configuration addresscomm...@myfaces.apache.org/address /configuration /notifier /notifiers /ciManagement Thanks, Andrew -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf
[jira] Commented: (TOBAGO-926) tc:popup transparent
[
https://issues.apache.org/jira/browse/TOBAGO-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12926323#action_12926323
]
Guido Dubois commented on TOBAGO-926:
-
Thanks for the suggestion! I droped this code from the style-file and now it
works fine...
.tobago-popup {
opacity: 0.75;
filter: alpha(opacity = 75);
-moz-opacity: 0.75;
}
tc:popup transparent
--
Key: TOBAGO-926
URL: https://issues.apache.org/jira/browse/TOBAGO-926
Project: MyFaces Tobago
Issue Type: Bug
Components: Core
Affects Versions: 1.5.0-alpha-2
Environment: Facelets
Reporter: Guido Dubois
Attachments: transparent_popup.png
Popup trought tc:toolBarCommand is transparent.
tc:toolBarCommand id=toolbarButtonNewProduct
actionListener=#{toolbarController.newProductClick}
label=#{bundle.toolNewProduct} image=image/filenew.png
tip=#{bundle.tooltipNewProduct} immediate=false
transition=true
tc:popupReference for=popupNewProduct /
ui:include src=/overview/popupNewProduct.xhtml /
/tc:toolBarCommand
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1948) Trinidad's Agent API Should Support Detection of Web Crawlers
[ https://issues.apache.org/jira/browse/TRINIDAD-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Max Starets updated TRINIDAD-1948: -- Resolution: Fixed Fix Version/s: 2.0.0.3-core Status: Resolved (was: Patch Available) Trinidad's Agent API Should Support Detection of Web Crawlers - Key: TRINIDAD-1948 URL: https://issues.apache.org/jira/browse/TRINIDAD-1948 Project: MyFaces Trinidad Issue Type: New Feature Affects Versions: 2.0.0.3-core Reporter: Max Starets Assignee: Max Starets Fix For: 2.0.0.3-core Attachments: trinidad-1948.patch We should add support for detecting web crawlers at runtime. This would allow page authors to generate special content for the search engines, and would enable us in the future to implement a special rendering mode if we choose to do so. Proposal: - Add new TYPE_WEBCRAWLER Agent type - Add AGENT_GOOGLEBOT and AGENT_MSNBOT agents - Use the desktop rendering kit and the default output mode when generating content for web crawlers (for now). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TRINIDAD-1937) beef up -tr-property-ref to work in compact css properties like border
[
https://issues.apache.org/jira/browse/TRINIDAD-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeanne Waldman resolved TRINIDAD-1937.
--
Resolution: Fixed
Fix Version/s: 2.0.0.3-core
beef up -tr-property-ref to work in compact css properties like border
--
Key: TRINIDAD-1937
URL: https://issues.apache.org/jira/browse/TRINIDAD-1937
Project: MyFaces Trinidad
Issue Type: Improvement
Components: Skinning
Reporter: Jeanne Waldman
Assignee: Jeanne Waldman
Fix For: 2.0.0.3-core
We have compact css properties in our skin files, like
border: red solid 2px;
We also have a -tr-property-ref feature so you can set the property to
another selector's property value.
.AFDarkColor { color: #cc}
.AFDarkBG {background-color: -tr-property-ref(color, .AFDarkColor)}
But currently -tr-property-ref does not work within a compact css property.
We would like to do this:
border: -tr-property-ref(color, .AFDarkColor); solid 2px;
We worked around not having this feature by breaking out border: red solid
2px into verbose styles
border-style: solid;
border-width: 2px;
border-color: -tr-property-ref(color, .AFDarkColor);
, but this is not backward compatible; it might break a person's skin
extension.
--
If someone skinned
border: purple solid 2px, they will overwrite the current border: red solid
2px. The merged property is border: purple solid 2px;
But if we changed our skin to be border-style, border-width, border-color,
then their border override isn't overriding any more since it is a different
property. border vs border-style, etc.
So the properties get merged to border, border-style, border-width,
border-color. And we currently cannot rely on the ordering of the css
properties, so they could get border: purple solid 2px; border-style: solid;
border-width: 2px; border-color: red.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TRINIDAD-1936) merge skin (server-side) properties the same as skin css properties
[ https://issues.apache.org/jira/browse/TRINIDAD-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeanne Waldman resolved TRINIDAD-1936. -- Resolution: Fixed Fix Version/s: 2.0.0.4-core merge skin (server-side) properties the same as skin css properties --- Key: TRINIDAD-1936 URL: https://issues.apache.org/jira/browse/TRINIDAD-1936 Project: MyFaces Trinidad Issue Type: Improvement Components: Skinning Reporter: Jeanne Waldman Assignee: Jeanne Waldman Fix For: 2.0.0.4-core For the simplified fusion skin project, -tr-property-ref support was added to enable CSS attribute values from one selector to be referenced by a different CSS attribute in another selector. For details, see https://issues.apache.org/jira/browse/TRINIDAD-1680. This issue is to support a similar -tr-property-ref mechanism, but for skin properties related to a selector ( e.g. -tr-font-color: #cc ) instead of CSS attributes related to a selector. Also, we want to support -tr-rule-ref for skin properties. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TRINIDAD-1914) provide a hook for external decorator to find trinidad-skins.xml from a location other than META-INF or WEB-INF.
[
https://issues.apache.org/jira/browse/TRINIDAD-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeanne Waldman resolved TRINIDAD-1914.
--
Resolution: Fixed
Fix Version/s: 2.0.0.4-core
provide a hook for external decorator to find trinidad-skins.xml from a
location other than META-INF or WEB-INF.
--
Key: TRINIDAD-1914
URL: https://issues.apache.org/jira/browse/TRINIDAD-1914
Project: MyFaces Trinidad
Issue Type: Improvement
Components: Skinning
Reporter: Jeanne Waldman
Assignee: Jeanne Waldman
Fix For: 2.0.0.4-core
Attachments: patchForSkinResourceLoader.patch
Our design time team needs a way to have the Trinidad Skinning Framework find
trinidad-skins.xml from a location other than META-INF or WEB-INF.
The implementation I have in mind is similar to
https://issues.apache.org/jira/browse/TRINIDAD-1729 provide a hook for for
an external decorator of Skin InputStreamProvider.
I've mocked up a solution that works for our design time team. It is outlined
below with questions I'll ask on the dev list.
1. Add a public API
public interface TrinidadSkinsURLProvider (name to be determined)
{
// returns an Iterator of all the URLs that have this resource
(trinidad-skins.xml)
// Design time team needs the ExternalContext to be able to find their
trinidad-skins.xml files.
// They put a parameter on the ServletContext to help them.
public IteratorURL findResources(ExternalContext context);
}
2. Usage in SkinUtils.java
a. Call ListTrinidadSkinsURLProvider urlProviders =
ClassLoaderUtils.getServices(
org.apache.myfaces.trinidad.share.io.TrinidadSkinsURLProvider);
to get the List of TrinidadSkinsURLProviders.
b. Call findResources for each TrinidadSkinsURLProvider
c. Call the existing trinidad-skins.xml parse code.
Questions I plan to ask on the dev list:
a. Is this idea acceptable?
b. Are there existing Trinidad APIs that I'm not aware of that I could use
instead, like an existing ResourceLoader?
org.apache.myfaces.trinidad.resource.ResourceLoader does not have a
findResources method of any kind.
c. Should we have a more generic class name, like URLProvider? Or
URLResourceProvider? If so, then we can pass in the filename to
findResources().
d. What package should this go in? My mockup is in
org.apache.myfaces.trinidad.share.io.
e. ClassLoader#getResources returns an EnumerationURL. Should this new API
be IteratorURL or should it match ClassLoader#getResources?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[TRINIDAD] public API review - SkinVersion
Hi,
I've been asked to implement something called skin versioning into the
skinning framework. This is useful when you (the skinning developer)
want to update your skin, and you want to version it, so that an end
user can decide if he wants to uptake your new version without changing
the skin-family name, and keeping the skin-family name version-free.
In trinidad-config.xml, the application developer chooses the
skin-family to use. We will now have a skin-version field as well:
skin-familypurple/skin-family
skin-versionv2/skin-version
The syntax skin-versiondefault/skin-version can
be supported as well to return the purple skin whose version is marked
to be the default skin in that skin-family.
We could also add a skin-versionlatest/skin-version
so an end user can say, "I always want the latest purple skin", and
they'll never have to change their trinidad-config.xml every time a new
purple skin version comes out.
In trinidad-skins.xml (the skin developer) could add versioning to the
skins like this. The name of the version can be any String the skin
developer wants. Here we've chosen "v1" and "v2".
skin
idpurple-v1.desktop/id
familypurple/family
version
namev1/name
defaulttrue/default
/version
...
/skin
skin
idpurple-v2.desktop/id
familypurple/family
version
namev2/name
/version
...
/skin
The SkinVersion will be a class and not simply a String so we can add
'default' and maybe 'latest' flags to it.
A Skin object will have a SkinVersion. A Skin object already has an id,
a family, a styleSheetName, etc.
package org.apache.myfaces.trinidad.skin;
/**
* You can version skins. The skin version works tightly with the skin
family.
* This allows someone to create versions of their skin, like purple,
purple-v2,
* purple-v3. Then the user can say which skin version they want, like:
*
skin-familypurple/skin-familyskin-versionv3/skin-version
when they
* pick a skin in trinidad-config.xml.
* When creating a skin, you give it a version if you care about
versioning.
* When extending this class, you must override equals.
*/
abstract public class SkinVersion
{
// when extending this class, you must override equals
abstract public boolean equals(Object o);
abstract public boolean isDefault();
abstract public String getName();
}
Let me know what you think.
Thanks!
Jeanne
Re: [TRINIDAD] public API review - SkinVersion
I'm wondering if we're making the subclasser implement equals() in
SkinVersion if we should make hashCode() abstract as well so that they
remember to provide their own implementation there as well.
-- Blake
On 10/29/10 2:30 PM, Jeanne Waldman wrote:
Hi,
I've been asked to implement something called skin versioning into the
skinning framework. This is useful when you (the skinning developer)
want to update your skin, and you want to version it, so that an end
user can decide if he wants to uptake your new version without
changing the skin-family name, and keeping the skin-family name
version-free.
In trinidad-config.xml, the application developer chooses the
skin-family to use. We will now have a skin-version field as well:
skin-familypurple/skin-family
*skin-versionv2/skin-version*
The syntax *skin-versiondefault/skin-version* can be supported as
well to return the purple skin whose version is marked to be the
default skin in that skin-family.
We could also add a *skin-versionlatest/skin-version* so an end
user can say, I always want the latest purple skin, and they'll
never have to change their trinidad-config.xml every time a new purple
skin version comes out.
In trinidad-skins.xml (the skin developer) could add versioning to the
skins like this. The name of the version can be any String the skin
developer wants. Here we've chosen v1 and v2.
skin
idpurple-v1.desktop/id
familypurple/family
*version
namev1/name
defaulttrue/default
/version*
...
/skin
skin
idpurple-v2.desktop/id
familypurple/family
*version
namev2/name
/version*
...
/skin
The SkinVersion will be a class and not simply a String so we can add
'default' and maybe 'latest' flags to it.
A Skin object will have a SkinVersion. A Skin object already has an
id, a family, a styleSheetName, etc.
package org.apache.myfaces.trinidad.skin;
/**
* You can version skins. The skin version works tightly with the skin
family.
* This allows someone to create versions of their skin, like purple,
purple-v2,
* purple-v3. Then the user can say which skin version they want, like:
* skin-familypurple/skin-familyskin-versionv3/skin-version
when they
* pick a skin in trinidad-config.xml.
* When creating a skin, you give it a version if you care about
versioning.
* When extending this class, you must override equals.
*/
abstract public class SkinVersion
{
// when extending this class, you must override equals
abstract public boolean equals(Object o);
abstract public boolean isDefault();
abstract public String getName();
}
Let me know what you think.
Thanks!
Jeanne
[jira] Commented: (TRINIDAD-1816) Unicode ¿ character (\u00BF) is escaped to iquest instead of iquest; for example:a titl e=This is a bug amp;iquestAre you there?
[ https://issues.apache.org/jira/browse/TRINIDAD-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12926492#action_12926492 ] Gabrielle Crawford commented on TRINIDAD-1816: -- https://issues.apache.org/jira/browse/TRINIDAD-1928 Unicode ¿ character (\u00BF) is escaped to iquest instead of iquest; for example:a title=This is a bug amp;iquestAre you there? Key: TRINIDAD-1816 URL: https://issues.apache.org/jira/browse/TRINIDAD-1816 Project: MyFaces Trinidad Issue Type: Bug Components: Facelets Affects Versions: 1.2.13-core , 1.2.14-core Environment: myfaces 1.2.8, facelets 1.1.5 Reporter: victor Priority: Minor Unicode '¿' character (\u00BF) is escaped to iquest instead of iquest; for example:a title=This is a bug amp;iquestAre you there? I'm using UTF-8 char encoding. Updated commons-lang.jar don´t solve it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MYFACES-2952) Improve Atmosphere Meteor support of MyFaces
[ https://issues.apache.org/jira/browse/MYFACES-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonardo Uribe resolved MYFACES-2952. - Resolution: Fixed Fix Version/s: 2.0.3-SNAPSHOT Assignee: Leonardo Uribe Added org.apache.myfaces.INITIALIZE_ALWAYS param as suggested on the list. Improve Atmosphere Meteor support of MyFaces Key: MYFACES-2952 URL: https://issues.apache.org/jira/browse/MYFACES-2952 Project: MyFaces Core Issue Type: Improvement Affects Versions: 2.0.3-SNAPSHOT Reporter: Matthias Weßendorf Assignee: Leonardo Uribe Fix For: 2.0.3-SNAPSHOT Currently MyFaces aborts the initialization when there is no configured FacesServlet. While this does make sense in almost all cases, there are options when we do want the framework to initialize in a proper way: Atmoshpere's Meteor framework to support comet/websocket -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
