date:20100315

Implementation of MockHttpSession.invalidate()
--

 Key: MYFACESTEST-5
 URL: https://issues.apache.org/jira/browse/MYFACESTEST-5
 Project: Apache MyFaces Test
  Issue Type: Improvement
Reporter: Christoph Göldner
 Attachments: MockHttpSession.patch

Currently MockHttpSession.invalidate() throws an UnsupportedOperationException.
See attached patch which implements the invalidate() logic inside 
MockHttpSession.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (MYFACESTEST-5) Implementation of MockHttpSession.invalidate()


 [ 
https://issues.apache.org/jira/browse/MYFACESTEST-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christoph Göldner updated MYFACESTEST-5:


Status: Patch Available  (was: Open)

 Implementation of MockHttpSession.invalidate()
 --

 Key: MYFACESTEST-5
 URL: https://issues.apache.org/jira/browse/MYFACESTEST-5
 Project: Apache MyFaces Test
  Issue Type: Improvement
Reporter: Christoph Göldner
 Attachments: MockHttpSession.patch


 Currently MockHttpSession.invalidate() throws an 
 UnsupportedOperationException.
 See attached patch which implements the invalidate() logic inside 
 MockHttpSession.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (MYFACESTEST-4) Unable to call setValue of ValueExpression in test


 [ 
https://issues.apache.org/jira/browse/MYFACESTEST-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christoph Göldner updated MYFACESTEST-4:


Status: Patch Available  (was: Open)

 Unable to call setValue of ValueExpression in test
 --

 Key: MYFACESTEST-4
 URL: https://issues.apache.org/jira/browse/MYFACESTEST-4
 Project: Apache MyFaces Test
  Issue Type: Bug
 Environment: See attached JUnit test case which fails with 
 myfaces-test20-1.0.0-SNAPSHOT
 Tested with Mojarra-2.0.2
Reporter: Christoph Göldner
 Attachments: MockApplication12.patch, ValueExpressionTest.java


 Components tested inside a test case inherited from AbstractJsfTestCase are 
 not able to do following:
   ELContext elContext = facesContext.getELContext();
   ValueExpression ve = 
 application.getExpressionFactory().createValueExpression(elContext, #{foo}, 
 String.class);
   ve.setValue(elContext, BAR);
 The error is caused by the FacesResourceBundleELResolver inside the setValue 
 method, where it tries to get a ResourceBundle from MockApplication12 for the 
 given ValueExpression. Unfortunately the MockApplication12 getResourceBundle 
 method throws a MissingResourceException instead of returning null.
 Please apply attached patch to the code base.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (MYFACESTEST-4) Unable to call setValue of ValueExpression in test

Unable to call setValue of ValueExpression in test
--

 Key: MYFACESTEST-4
 URL: https://issues.apache.org/jira/browse/MYFACESTEST-4
 Project: Apache MyFaces Test
  Issue Type: Bug
 Environment: See attached JUnit test case which fails with 
myfaces-test20-1.0.0-SNAPSHOT
Tested with Mojarra-2.0.2

Reporter: Christoph Göldner


Components tested inside a test case inherited from AbstractJsfTestCase are not 
able to do following:

  ELContext elContext = facesContext.getELContext();
  ValueExpression ve = 
application.getExpressionFactory().createValueExpression(elContext, #{foo}, 
String.class);
  ve.setValue(elContext, BAR);

The error is caused by the FacesResourceBundleELResolver inside the setValue 
method, where it tries to get a ResourceBundle from MockApplication12 for the 
given ValueExpression. Unfortunately the MockApplication12 getResourceBundle 
method throws a MissingResourceException instead of returning null.

Please apply attached patch to the code base.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (MYFACESTEST-4) Unable to call setValue of ValueExpression in test


[ 
https://issues.apache.org/jira/browse/MYFACESTEST-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845264#action_12845264
 ] 

Christoph Göldner commented on MYFACESTEST-4:
-

I assume that it also fails with JSF 1.2 implementations

 Unable to call setValue of ValueExpression in test
 --

 Key: MYFACESTEST-4
 URL: https://issues.apache.org/jira/browse/MYFACESTEST-4
 Project: Apache MyFaces Test
  Issue Type: Bug
 Environment: See attached JUnit test case which fails with 
 myfaces-test20-1.0.0-SNAPSHOT
 Tested with Mojarra-2.0.2
Reporter: Christoph Göldner
 Attachments: MockApplication12.patch, ValueExpressionTest.java


 Components tested inside a test case inherited from AbstractJsfTestCase are 
 not able to do following:
   ELContext elContext = facesContext.getELContext();
   ValueExpression ve = 
 application.getExpressionFactory().createValueExpression(elContext, #{foo}, 
 String.class);
   ve.setValue(elContext, BAR);
 The error is caused by the FacesResourceBundleELResolver inside the setValue 
 method, where it tries to get a ResourceBundle from MockApplication12 for the 
 given ValueExpression. Unfortunately the MockApplication12 getResourceBundle 
 method throws a MissingResourceException instead of returning null.
 Please apply attached patch to the code base.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Classloader Problems running JSF in jetty equinox

2010-03-15 Thread arnold4sho


Hi

Thanks for your effort. Would it be advisable for me to use Spring DM
instead of deploying a jetty web container into osgi, like i was trying to
do? If Spring provides the better solution then i would gladly use Spring DM
for it. 


Arnold

Leonardo Uribe wrote:
 
 Hi
 
 On this link:
 
 https://issues.apache.org/jira/browse/MYFACES-2290
 
 There is an example that runs myfaces in osgi using spring dm. Look at the
 comments, because it is required to download two artifacts not available
 on
 spring osgi repository.
 
 Really, I'm trying to find other example configuration that does not use
 spring dm.
 
 regards,
 
 Leonardo Uribe
 
 2010/3/13 arnold4sho tung_twist...@hotmail.com
 

 I checked out your link, which bundles do you suggest i use for the
 MyFaces
 and Jsp?

 Arnold

 arnold4sho wrote:
 
  Hi
 
  Thanks for your reply, were you able to get my application to run?
  I have been looking at many possibilies of making the application run
 but
  up until now i have none which actually works. Do you have any
  suggestions?
 
 
 
 
  Leonardo Uribe wrote:
 
  Hi
 
  Checking this page:
 
 
 http://download.eclipse.org/equinox/drops/R-3.5.2-201002111343/index.php
 
  There is no javax.servlet.jsp bundle for 2.1. Myfaces 1.2.x or 2.0.x
  requires servlet 2.5 / jsp 2.1 to run. It could be possible, but I'm
 not
  100% sure that it is possible to run but using facelets + servlet 2.4
 +
  jsp
  2.1, but I have never tried before.
 
  regards,
 
  Leonardo Uribe
 
  2010/3/13 arnold4sho tung_twist...@hotmail.com
 
 
  Hi
 
  Once again, the problem is that the bean class in the second bundle
 is
  not
  resolved. If you type in
  http://localhost:8081/clintweb.xhtml. Clintweb.xhtml is in the second
  bundle.
 
  in the browser, the checkbox does not show the property value in the
  SimpleTestBean. I would like to know how i can be able to get that to
  work.
  I would like to be able to access the beans in other bundles. That is
 my
  main problem
 
  thanks alot!
 
  Arnold
 
  Leonardo Uribe wrote:
  
   Hi
  
   Can you list what bundles are you using for? I would like to
 reproduce
  it
   and it is necessary to know which bundles are you usings to run
 jetty
  and
   servlet stuff, and all configuration hacks you are using for it.
  
   regards,
  
   Leonardo Uribe
  
   2010/3/13 arnold4sho tung_twist...@hotmail.com
  
  
  
   Hi
  
   I have problems running JSF in an OSGi environment. I am using
 jetty
  web
   container and equinox to provide the OSGi functionality. The
  structure
  of
   my
   application is as follows:
   The first bundle has all the JSF libs, web.xml and a config.xml.
 It
  looks
   as
   the following:
 webapplication1
 src/main/java
 ---de/package
 --Activator.java
 --JSFResolver.java
 src/main/resource
 -- WebContent
 --META-INF
 -face-config.xml
--web.xhtml
 --start.xhtml
---include.xhtml
libs (containing all JSF required
 Jars)
  
   The structure of the second bundle is as follows:
 webapplication2
 ---src/main/java
 --de/package
 --Bean.java
 ---src/main/resource
 --META-INF
 -face-config.xml
 --WebContent
 -index.xhtml
  
   When running the application of equinox, the webapplication1 is
 the
  main
   bundle where all the browser requests are sent to. In the second
  bundle,
   the
   'index.xhtml' file can be retrieved the by first bundle upon
 request.
  The
   'index.xhtml' in bundle 2 gets its values and properties from the
   'Bean.java' in bundle 2. The problem comes when i request the
   'index.xhtml',
   the Bean.java class is not found. I think this is because the
 class
   loader
   of bundle1 cannot find it, it has no knowledge of it. So i would
 like
  to
   ask
   if anyone knows how to solve this problem. If so please do assist
 me,
  i
   have
   tried all the possibilities i had.. I have provided my
   http://old.nabble.com/file/p27887386/workspace_current.rar
   workspace_current.rar bundles as attatchments.
  
   Is it infact possible  to have JSF run on multiple bundles using
 the
  same
   FaceletsContex? Can i be able to have seperate faces-config.xml
 files
  in
   each bundle, which can all be connected other faces-config.xml in
  other
   bundles? Can anyone please provide me a solution. Sample code
 would
  help.

[jira] Commented: (MYFACES-2599) ajax javascript checks for existence of triggering html element


[ 
https://issues.apache.org/jira/browse/MYFACES-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845280#action_12845280
 ] 

Werner Punz commented on MYFACES-2599:
--

Ok I have comitted everything that a detachment case is doable under certain 
conditions. Have in mind I am bending the spec here a little bit.
First of all, if the element is replaced with an element with the same 
identifier within a form, we are set and can pass through.
This would even pass through with the old code.

Second if the element is passed as domNode but the replacement has happend by a 
named element of the same name as the original identifier and no other equally 
named element under a form exists, we have case 1 here again, we do not have to 
do anything.

Now to the difficult cases, if the element is detached a and replaced by an 
element with a different identifier and same name and to the worse only the 
identifier string is passed down to jsf.ajax.request, which is probably the 
most common usecase:

This passes if only one element under a form with the same name , otherwise I 
cannot determine the source of the ajax request anymore and I am absolutely 
forced to throw an error (have in mind the id - naming assumption is already a 
bending of the spec which clearly says If the DOM element could not be 
determined, throw an error, I assume having a matching name and only one within 
the bounds of a form
is valid within the spec.



 ajax javascript checks for existence of triggering html element
 ---

 Key: MYFACES-2599
 URL: https://issues.apache.org/jira/browse/MYFACES-2599
 Project: MyFaces Core
  Issue Type: Bug
  Components: JSR-314
Affects Versions: 2.0.0-beta-2
 Environment: Javascript
Reporter: Ganesh Jung

 This one is a bit special. I remove the triggering element from the DOM, 
 afterwards I trigger it's onchange method. Works with Mojarra, but MyFaces 
 insists, that the triggering element must exist in the DOM, though this isn't 
 necessary from the spec.
   h:form id=testForm
   h:inputText id=test value=#{myBean.test} 
   f:ajax render=test2/
   /h:inputText
   h:inputText id=test2 value=#{myBean.test} /
   script type=text/javascript
   //![CDATA[
   var myTest = document.getElementById(testForm:test);
   var test_onchange = myTest.onchange;
   myTest.parentNode.removeChild(myTest);
   test_onchange();
   //]]
   /script
   /h:form

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (MYFACES-2599) ajax javascript checks for existence of triggering html element


 [ 
https://issues.apache.org/jira/browse/MYFACES-2599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Werner Punz resolved MYFACES-2599.
--

Resolution: Fixed

 ajax javascript checks for existence of triggering html element
 ---

 Key: MYFACES-2599
 URL: https://issues.apache.org/jira/browse/MYFACES-2599
 Project: MyFaces Core
  Issue Type: Bug
  Components: JSR-314
Affects Versions: 2.0.0-beta-2
 Environment: Javascript
Reporter: Ganesh Jung

 This one is a bit special. I remove the triggering element from the DOM, 
 afterwards I trigger it's onchange method. Works with Mojarra, but MyFaces 
 insists, that the triggering element must exist in the DOM, though this isn't 
 necessary from the spec.
   h:form id=testForm
   h:inputText id=test value=#{myBean.test} 
   f:ajax render=test2/
   /h:inputText
   h:inputText id=test2 value=#{myBean.test} /
   script type=text/javascript
   //![CDATA[
   var myTest = document.getElementById(testForm:test);
   var test_onchange = myTest.onchange;
   myTest.parentNode.removeChild(myTest);
   test_onchange();
   //]]
   /script
   /h:form

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Classloader Problems running JSF in jetty equinox

2010-03-15 Thread Werner Punz


Am 15.03.10 12:19, schrieb arnold4sho:

Thanks for your effort. Would it be advisable for me to use Spring DM
instead of deploying a jetty web container into osgi, like i was trying to
do? If Spring provides the better solution then i would gladly use Spring DM
for it.

It is definitely advisable because you might run into issues on the JPA 
side was well, due to the javaagent class recompilation jpa does.
As far as I know there are some issues regarding class weaving which the 
spring people apparently have solved.

Re: Classloader Problems running JSF in jetty equinox

2010-03-15 Thread Leonardo Uribe

Hi

From jsf side, Spring DM set the context classloader and allows to
Thread.getCurrentThread().getContextClassLoader() to work. Note in OSGi,
trying to locate a class through the context classloader could cause a
ClassNotFoundException, and use the BundleClassLoader through
jsfclass.class.getClassLoader() is not right in cases like the one found in
javax.faces.FactoryFinder.

regards,

Leonardo Uribe

2010/3/15 Werner Punz werner.p...@gmail.com

 Am 15.03.10 12:19, schrieb arnold4sho:

  Thanks for your effort. Would it be advisable for me to use Spring DM
 instead of deploying a jetty web container into osgi, like i was trying to
 do? If Spring provides the better solution then i would gladly use Spring
 DM
 for it.

  It is definitely advisable because you might run into issues on the JPA
 side was well, due to the javaagent class recompilation jpa does.
 As far as I know there are some issues regarding class weaving which the
 spring people apparently have solved.

[jira] Created: (TRINIDAD-1755) Refresh problems with tr:tabel using a filter string defined in a tr_inputText

2010-03-15 Thread Markus Petri (JIRA)

Refresh problems with tr:tabel using a filter string defined in a tr_inputText
--

 Key: TRINIDAD-1755
 URL: https://issues.apache.org/jira/browse/TRINIDAD-1755
 Project: MyFaces Trinidad
  Issue Type: Bug
  Components: Components
Affects Versions: 1.2.13-core 
 Environment: Trinidad 1.2.13, MyFaces 1.2.8, Tomahawk 1.1.9, Facelets 
1.1.15, Tomcat 6.0.20 
Reporter: Markus Petri


In our application, we use a tr:inputText to filter the tables data using PPR.

1st problem:
When the filter method of the backing bean deliveres 1-4 matches, everything 
works fine. But if there are more than 5 matches, I need to press the button 
twice to get the table re-rendered.

2nd problem:
We use the rows attribute to show 10 entries each page. If the filter method 
deliveres more than 10 rows, I need also to click twice the show next link 
(but only the first time) to get to the next page. After the first click, I can 
switch the pages as purposed. 

Here our *.jspx (this *jspx is included into a t:panelTabbedPanet:panelTab )
[...]
tr:panelCaptionGroup captionText=#{resource['label.section.filteroptions']} 
inlineStyle=margin-bottom:10px;
 table border=0 cellpadding=0 cellspacing=0
 tr
  tdtr:inputText id=filterString 
value=#{listing.filterString} partialTriggers=cmd_reset 
styleClass=filterInput 
onblur=if(this.value == 
''){this.value='#{resource['text.filteroptions.default']}';this.style.color = 
'#A0A0A0';} 
onfocus=if(this.value == 
'#{resource['text.filteroptions.default']}'){this.value='';this.style.color = 
'#00';}

onkeyup=if(event.keyCode==13)document.getElementById('tab2:listForm:cmd_filter').click();/
  /td
  td
   tr:selectOneChoice value=#{listing.filterDate} 
f:selectItem itemLabel=#{resource['selectBox.choice.allRegistrations']} 
itemValue=0/
f:selectItem 
itemLabel=#{resource['selectBox.choice.todaysRegistrations']} itemValue=1/
   /tr:selectOneChoice
  /td
  tdtr:commandButton id=cmd_filter 
  text=#{resource['button.filterList']}
  shortDesc=#{resource['tooltip.action.filterList']}
  actionListener=#{listing.filter} partialSubmit=true /
   /td
   tdtr:commandButton id=cmd_reset
  text=#{resource['button.filterReset']}
  shortDesc=#{resource['tooltip.action.reset']}
  blocking=true 
  actionListener=#{listing.reset} partialSubmit=true/
   /td
  /tr
 /table
/tr:panelCaptionGroup
tr:table binding=#{listing.table} value=#{listing.regInfos} var=regs 
rowBandingInterval=1 rows=10 partialTriggers=::cmd_filter ::cmd_reset 
::pollid immediate=true
 tr:column width=160 inlineStyle=vertical-align:top; sortable=true 
sortProperty=date
  f:facet name=header
   tr:outputText value=#{resource['table.registrations.plannedArrival']}/
  /f:facet
  tr:outputText value=#{regs.date} id=date
   tr:convertDateTime pattern=#{resource['pattern.dateTime']} type=both / 

  /tr:outputText
 /tr:column
 tr:column width=100 inlineStyle=vertical-align:top;
  f:facet name=header
   tr:outputText value=#{resource['table.registrations.room']}/
  /f:facet
  tr:outputText value=#{regs.roomNumber}/
 /tr:column
[...]

and the relevant part of the backing bean (using SESSION_SCOPE):
/**
 * Process the filter action.
 */
public void filter(ActionEvent e) {
refreshTable();
}
public void refreshTable(){
initialize();
RequestContext.getCurrentInstance().addPartialTarget(getTable());
}   
private void initialize(){
Authentication auth = 
SecurityContextHolder.getContext().getAuthentication();
if (auth instanceof VirAuthenticationToken) {
String login = ((VirAuthenticationToken)auth).getLogin();
try {
setRegInfos(ServiceUtils.getOpenRegistrations(login, 
getDefaultSearchString().equals(getFilterString())?  : 
getFilterString(),getFilterReriod()));
}catch (RemoteException exc) {
log.fatal(Error processing business method - Remote 
error -  + ServiceManager.getInstance().getServiceExceptionMessage(exc));  
   
}
}
}

When debugging, it shows the same values both at the first and at the second 
click, but as told before the table is only re-rendered after the second click.

Any suggestions?

Thanks in advance,
 Markus


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (EXTSCRIPT-41) Write the documentation


 [ 
https://issues.apache.org/jira/browse/EXTSCRIPT-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Werner Punz resolved EXTSCRIPT-41.
--

Resolution: Fixed
  Assignee: Werner Punz

 Write the documentation
 ---

 Key: EXTSCRIPT-41
 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-41
 Project: MyFaces Extensions Scripting
  Issue Type: Bug
Reporter: Werner Punz
Assignee: Werner Punz



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (EXTSCRIPT-41) Write the documentation


[ 
https://issues.apache.org/jira/browse/EXTSCRIPT-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845317#action_12845317
 ] 

Werner Punz commented on EXTSCRIPT-41:
--

I am closing this for now, the docs should be enough for a beta release


 Write the documentation
 ---

 Key: EXTSCRIPT-41
 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-41
 Project: MyFaces Extensions Scripting
  Issue Type: Bug
Reporter: Werner Punz
Assignee: Werner Punz



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (EXTSCRIPT-95) Source and full bundle

Source and full bundle
--

 Key: EXTSCRIPT-95
 URL: https://issues.apache.org/jira/browse/EXTSCRIPT-95
 Project: MyFaces Extensions Scripting
  Issue Type: Bug
Reporter: Werner Punz
Assignee: Werner Punz
Priority: Minor


Check how to make source and full bundles for the final release


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (TOBAGO-657) not running at all

2010-03-15 Thread Udo Schnurpfeil (JIRA)


 [ 
https://issues.apache.org/jira/browse/TOBAGO-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Udo Schnurpfeil resolved TOBAGO-657.


Resolution: Invalid

Such kind of questions should asked on the user mailing list.

 not running at all
 --

 Key: TOBAGO-657
 URL: https://issues.apache.org/jira/browse/TOBAGO-657
 Project: MyFaces Tobago
  Issue Type: Bug
Reporter: adam
 Attachments: small application.rar


 Hey Guys .. I'm new with Tobago and i make small example to test my knowledge 
 and when i press the button nothing run plz can any one help me and tell me 
 why not running?
 I attached all files that u will need to see it 
 Waiting for ur replay as soon as possible
 plz any one help me on my first application 
 faces-config.xml:
 ?xml version=1.0 encoding=UTF-8?
 !DOCTYPE faces-config PUBLIC
 -//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN
 http://java.sun.com/dtd/web-facesconfig_1_1.dtd;
 faces-config
   managed-bean
   managed-bean-name
   goClass/managed-bean-name
   managed-bean-class
   com.GoClass/managed-bean-class
   managed-bean-scope
   session/managed-bean-scope
   /managed-bean
   navigation-rule
   display-name
   index/display-name
   from-view-id
   /index.jsp/from-view-id
   navigation-case
   from-outcomesuccess/from-outcome
   to-view-id
   /success.jsp/to-view-id
   /navigation-case
   /navigation-rule
 /faces-config
 tobago-config.xml : 
 ?xml version=1.0 encoding=UTF-8?
 !DOCTYPE tobago-config PUBLIC
 -//The Apache Software Foundation//DTD Tobago Config 1.0//EN 
 tobago-config_1_0.dtd
 tobago-config
   theme-config
 default-themespeyside/default-theme
 supported-themescarborough/supported-theme
 supported-themerichmond/supported-theme
 supported-themecharlotteville/supported-theme
   /theme-config
   resource-dirtobago-resource/resource-dir
   ajax-enabledtrue/ajax-enabled
 /tobago-config
 web.xml : 
 ?xml version=1.0 encoding=UTF-8?
 web-app id=WebApp_ID version=2.4
   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/j2ee 
 http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd;
   display-nameTestJSF/display-name
   !-- add filter to tobago facet --
   filter
   filter-namemultipartFormdataFilter/filter-name
   filter-class
   
 org.apache.myfaces.tobago.webapp.TobagoMultipartFormdataFilter
   /filter-class
   init-param
   description
   Set the size limit for uploaded files. Default 
 value is
   1 MB. Format: 10 = 10 bytes 10k = 10 KB 10m = 
 10 MB 1g =
   1 GB
   /description
   param-nameuploadMaxFileSize/param-name
   param-value20m/param-value
   /init-param
   !--init-param
   descriptionSet the upload repository path for 
 uploaded files. Default value is java.io.tmpdir./description
   param-nameuploadRepositoryPath/param-name
   param-value/tmp/param-value
   /init-param--
   /filter
   filter-mapping
   filter-namemultipartFormdataFilter/filter-name
   url-pattern/faces/*/url-pattern
   /filter-mapping
   !-- add listener to tobago facet --
   listener
   listener-class
   
 org.apache.myfaces.tobago.webapp.TobagoServletContextListener
   /listener-class
   /listener
   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/faces/*/url-pattern
   /servlet-mapping
   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
 /web-app
 index.jsp: 
 %@ taglib uri=http://java.sun.com/jsf/core; prefix=f%
 %@ taglib uri=http://java.sun.com/jsf/html; prefix=h%
 %@ taglib uri=http://myfaces.apache.org/tobago/component; prefix=tc%
 %@ taglib

[jira] Created: (TOBAGO-862) Remove the template mechanism of Tobago

2010-03-15 Thread Udo Schnurpfeil (JIRA)

Remove the template mechanism of Tobago
---

 Key: TOBAGO-862
 URL: https://issues.apache.org/jira/browse/TOBAGO-862
 Project: MyFaces Tobago
  Issue Type: Task
  Components: Core
Reporter: Udo Schnurpfeil
Priority: Minor


The template mechanism of Tobago is deprecated for a long time.
It was initiated before JSP-Tag Files and Facelets are existing.
In these days there is no longer a good reason to offer an own template 
mechanism.

It will be remove in Tobago 1.5.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Ext-Script Logo Request

2010-03-15 Thread Werner Punz

Hello everyone I am busy currently preparing a beta 1 tag for 
Ext-Scripting I have a small request.


First I would like to get a logo, I have none

http://people.apache.org/~werpu/ext-script-site/

See the left corner above. This is as far as my graphical capabilities 
go :-)



Seondly not important for now since the docs are not finalized but post 
beta 1 I would love to have one english speaking person doing some 
proofreading of the docs and correcting them or simply sending me the 
errata. For now since the docs are not finalized this is not important.

(But feel free to read over them now and send me the errors or fix them)


Werner

Re: Ext-Script Logo Request

2010-03-15 Thread Matthias Wessendorf

On Mon, Mar 15, 2010 at 9:10 AM, Werner Punz werner.p...@gmail.com wrote:
 Hello everyone I am busy currently preparing a beta 1 tag for Ext-Scripting
 I have a small request.

 First I would like to get a logo, I have none

 http://people.apache.org/~werpu/ext-script-site/

 See the left corner above. This is as far as my graphical capabilities go
 :-)

I like it, same skill set here ;-)

I like the youtube link in the startpage :-



 Seondly not important for now since the docs are not finalized but post beta
 1 I would love to have one english speaking person doing some proofreading
 of the docs and correcting them or simply sending me the errata. For now
 since the docs are not finalized this is not important.
 (But feel free to read over them now and send me the errors or fix them)


 Werner





-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

Re: Ext-Script Logo Request

2010-03-15 Thread Werner Punz


Am 15.03.10 17:14, schrieb Matthias Wessendorf:

On Mon, Mar 15, 2010 at 9:10 AM, Werner Punzwerner.p...@gmail.com  wrote:

Hello everyone I am busy currently preparing a beta 1 tag for Ext-Scripting
I have a small request.

First I would like to get a logo, I have none

http://people.apache.org/~werpu/ext-script-site/

See the left corner above. This is as far as my graphical capabilities go
:-)


I like it, same skill set here ;-)

I like the youtube link in the startpage :-

Yes the video still is pending in its final form, I will add some spoken 
stuff and a better example. It just was what I had lingering.
There are several additional videos in the users guide showing various 
aspects.


I probably also will add some screencasts in the yet very unfinished ide 
configuration section before hitting the final release.








Seondly not important for now since the docs are not finalized but post beta
1 I would love to have one english speaking person doing some proofreading
of the docs and correcting them or simply sending me the errata. For now
since the docs are not finalized this is not important.
(But feel free to read over them now and send me the errors or fix them)


Werner

[jira] Resolved: (TOBAGO-308) Tree Rendering Only Root Node

2010-03-15 Thread Udo Schnurpfeil (JIRA)


 [ 
https://issues.apache.org/jira/browse/TOBAGO-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Udo Schnurpfeil resolved TOBAGO-308.


Resolution: Cannot Reproduce

 Tree Rendering Only Root Node
 -

 Key: TOBAGO-308
 URL: https://issues.apache.org/jira/browse/TOBAGO-308
 Project: MyFaces Tobago
  Issue Type: Bug
  Components: Core
Affects Versions: 1.0.9, 1.0.10
Reporter: Mark P. Mullally

 Only the root node of a tree renders because the 
 TreeOldNode.getRendersChildren() returns true.  Susequently, the 
 TreeOldRenderer.getNodesAsJavascript() -- RenderUtil.encode(facesContext, 
 root) method executes component.encodeChildren(faceContext) instead of the 
 the recusive child loop, which relies on the 
 TreeOldNodeRenderer.encodeChildren() method that is NOT OVERRIDDEN and the 
 base implementation is a no-op.  Therefore, I don't see how trees ever 
 rendered correctly?  I extended the TreeOldNode to return false from 
 getRendersChildren() so that the TreeOldRenderer.getNodesAsJavascript() -- 
 RenderUtil.encode() method executes the recursive child loop FIXING THE 
 ISSUE.  Again, HOW DID THIS EVER WORK? AM I MISSING SOMETHING?
 Also, The Old code is deprecated but no standard in favor of comments 
 exist.  What should I be using? MyFaces or Tomahawk tree?
 btw...I am using the Feb 28 nightly build snapshot for 1.0.10

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (MYFACES-2604) Unresolved dependency of org.apache.commons.el.Logger


[ 
https://issues.apache.org/jira/browse/MYFACES-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845399#action_12845399
 ] 

Jakob Korherr commented on MYFACES-2604:


I don't think this is a MyFaces core problem. Take a look at the code that 
calls ClassUtils.classForName(): 
org.apache.myfaces.orchestra.annotation.spring.AnnotationsInfoInitializer.postProcessBeanFactory

This method simply gets all class names from the bean definitions from the 
given ConfigurableListableBeanFactory and tries to retrieve the right Class 
Objects via ClassUtils.classForName(). Unfortunately 
org.apache.commons.el.Logger seems to be one of the beans from the 
ConfigurableListableBeanFactory and thus it has to be on the classpath in order 
to function properly.

The code from MyFaces shared has no relation to org.apache.commons.el.Logger 
and thus it does not need this dependency. It's just used by Orchestra to 
retrieve the right Class object in this scenario.

So this is either a configuration problem (is org.apache.commons.el.Logger 
really supposed to be a bean?) or a missing orchestra dependency. Thus, I will 
close this as invalid.

 Unresolved dependency of org.apache.commons.el.Logger
 -

 Key: MYFACES-2604
 URL: https://issues.apache.org/jira/browse/MYFACES-2604
 Project: MyFaces Core
  Issue Type: Bug
 Environment: Deploying to Glassfish v2
Reporter: Bart Kummel
Priority: Minor

 When deploying an application that uses Orchestra Core 1.3.1, I get a 
 ClassNotFoundException on org.apache.commons.el.Logger. The work around is of 
 course to manually download Apache Commons EL and add is as a dependency. The 
 solution to this bug can be:
 - removing the dependency
 - mentioning the dependency in the docs.
 Stack trace:
 java.lang.NoClassDefFoundError: org/apache/commons/el/Logger
   at 
 org.apache.myfaces.shared_orchestra.util.ClassUtils.clinit(ClassUtils.java:44)
   at 
 org.apache.myfaces.orchestra.annotation.spring.AnnotationsInfoInitializer.postProcessBeanFactory(AnnotationsInfoInitializer.java:93)
   at 
 org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:553)
   at 
 org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:536)
   at 
 org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:362)
   at 
 org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
   at 
 org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
   at 
 org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
   at 
 org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4523)
   at 
 org.apache.catalina.core.StandardContext.start(StandardContext.java:5184)
   at com.sun.enterprise.web.WebModule.start(WebModule.java:326)
   at 
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:973)
   at 
 org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:957)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:688)
   at 
 com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1584)
   at 
 com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1222)
   at 
 com.sun.enterprise.web.WebContainer.loadJ2EEApplicationWebModules(WebContainer.java:1147)
   at 
 com.sun.enterprise.server.TomcatApplicationLoader.doLoad(TomcatApplicationLoader.java:141)
   at 
 com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:244)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:336)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:210)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:645)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:928)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:912)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:461)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:176)
   at 
 com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
   at

[jira] Commented: (MYFACES-2604) Unresolved dependency of org.apache.commons.el.Logger

2010-03-15 Thread Aleksei Valikov (JIRA)


[ 
https://issues.apache.org/jira/browse/MYFACES-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845469#action_12845469
 ] 

Aleksei Valikov commented on MYFACES-2604:
--

 Unfortunately org.apache.commons.el.Logger seems to be one of the beans from 
 the ConfigurableListableBeanFactory and thus it has to be on the classpath in 
 order to function properly. 

Below is the source code from the current Orchestra distribution:

package org.apache.myfaces.shared_orchestra.util;

import org.apache.commons.el.Coercions;
import org.apache.commons.el.Logger;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;

import javax.faces.FacesException;
import javax.servlet.jsp.el.ELException;
import java.io.InputStream;
import java.io.IOException;
import java.lang.reflect.Array;
import java.util.*;


public final class ClassUtils
{
//~ Static fields/initializers 
-

private static final Log log  = 
LogFactory.getLog(ClassUtils.class);
private static final Logger COERCION_LOGGER   = new Logger(System.out);

...

}


 The code from MyFaces shared has no relation to org.apache.commons.el.Logger 
 and thus it does not need this dependency.

Apparently Orchestra uses an older version of MyFaces Shared. Would you please 
reopen the issue and assign it back to Mario so that Orchestra team would make 
sure that a newer Share is used in the next release? Thank you.

 Unresolved dependency of org.apache.commons.el.Logger
 -

 Key: MYFACES-2604
 URL: https://issues.apache.org/jira/browse/MYFACES-2604
 Project: MyFaces Core
  Issue Type: Bug
 Environment: Deploying to Glassfish v2
Reporter: Bart Kummel
Priority: Minor

 When deploying an application that uses Orchestra Core 1.3.1, I get a 
 ClassNotFoundException on org.apache.commons.el.Logger. The work around is of 
 course to manually download Apache Commons EL and add is as a dependency. The 
 solution to this bug can be:
 - removing the dependency
 - mentioning the dependency in the docs.
 Stack trace:
 java.lang.NoClassDefFoundError: org/apache/commons/el/Logger
   at 
 org.apache.myfaces.shared_orchestra.util.ClassUtils.clinit(ClassUtils.java:44)
   at 
 org.apache.myfaces.orchestra.annotation.spring.AnnotationsInfoInitializer.postProcessBeanFactory(AnnotationsInfoInitializer.java:93)
   at 
 org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:553)
   at 
 org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:536)
   at 
 org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:362)
   at 
 org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
   at 
 org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
   at 
 org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
   at 
 org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4523)
   at 
 org.apache.catalina.core.StandardContext.start(StandardContext.java:5184)
   at com.sun.enterprise.web.WebModule.start(WebModule.java:326)
   at 
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:973)
   at 
 org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:957)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:688)
   at 
 com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1584)
   at 
 com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1222)
   at 
 com.sun.enterprise.web.WebContainer.loadJ2EEApplicationWebModules(WebContainer.java:1147)
   at 
 com.sun.enterprise.server.TomcatApplicationLoader.doLoad(TomcatApplicationLoader.java:141)
   at 
 com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:244)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:336)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:210)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:645)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:928)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:912)
   at

[jira] Commented: (MYFACES-2604) Unresolved dependency of org.apache.commons.el.Logger


[ 
https://issues.apache.org/jira/browse/MYFACES-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845476#action_12845476
 ] 

Jakob Korherr commented on MYFACES-2604:


Oh, I did not see that. Things have changed here, there a no dependencies to 
commons-el anymore in shared. I guess new orchestra releases will include the 
newest code from shared, so this should be automatically solved in the next 
release!

 Unresolved dependency of org.apache.commons.el.Logger
 -

 Key: MYFACES-2604
 URL: https://issues.apache.org/jira/browse/MYFACES-2604
 Project: MyFaces Core
  Issue Type: Bug
 Environment: Deploying to Glassfish v2
Reporter: Bart Kummel
Priority: Minor

 When deploying an application that uses Orchestra Core 1.3.1, I get a 
 ClassNotFoundException on org.apache.commons.el.Logger. The work around is of 
 course to manually download Apache Commons EL and add is as a dependency. The 
 solution to this bug can be:
 - removing the dependency
 - mentioning the dependency in the docs.
 Stack trace:
 java.lang.NoClassDefFoundError: org/apache/commons/el/Logger
   at 
 org.apache.myfaces.shared_orchestra.util.ClassUtils.clinit(ClassUtils.java:44)
   at 
 org.apache.myfaces.orchestra.annotation.spring.AnnotationsInfoInitializer.postProcessBeanFactory(AnnotationsInfoInitializer.java:93)
   at 
 org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:553)
   at 
 org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:536)
   at 
 org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:362)
   at 
 org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
   at 
 org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
   at 
 org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
   at 
 org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4523)
   at 
 org.apache.catalina.core.StandardContext.start(StandardContext.java:5184)
   at com.sun.enterprise.web.WebModule.start(WebModule.java:326)
   at 
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:973)
   at 
 org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:957)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:688)
   at 
 com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1584)
   at 
 com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1222)
   at 
 com.sun.enterprise.web.WebContainer.loadJ2EEApplicationWebModules(WebContainer.java:1147)
   at 
 com.sun.enterprise.server.TomcatApplicationLoader.doLoad(TomcatApplicationLoader.java:141)
   at 
 com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:244)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:336)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:210)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:645)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:928)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:912)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:461)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:176)
   at 
 com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
   at 
 com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:226)
   at 
 com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
   at 
 com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
   at 
 com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
   at 
 com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919)
   at 
 com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:276)
   at 
 com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:294)
   at

[jira] Commented: (MYFACES-2604) Unresolved dependency of org.apache.commons.el.Logger


[ 
https://issues.apache.org/jira/browse/MYFACES-2604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845479#action_12845479
 ] 

Jakob Korherr commented on MYFACES-2604:


Actually, this has not changed in the version of shared which orchestra uses 
(2.0.x). However, the pom.xml includes the following:

dependency
  groupIdcommons-el/groupId
  artifactIdcommons-el/artifactId
  version1.0/version
  scopecompile/scope
/dependency

This should be taken into account for the next orchestra release with shared 
2.0.x.

 Unresolved dependency of org.apache.commons.el.Logger
 -

 Key: MYFACES-2604
 URL: https://issues.apache.org/jira/browse/MYFACES-2604
 Project: MyFaces Core
  Issue Type: Bug
 Environment: Deploying to Glassfish v2
Reporter: Bart Kummel
Priority: Minor

 When deploying an application that uses Orchestra Core 1.3.1, I get a 
 ClassNotFoundException on org.apache.commons.el.Logger. The work around is of 
 course to manually download Apache Commons EL and add is as a dependency. The 
 solution to this bug can be:
 - removing the dependency
 - mentioning the dependency in the docs.
 Stack trace:
 java.lang.NoClassDefFoundError: org/apache/commons/el/Logger
   at 
 org.apache.myfaces.shared_orchestra.util.ClassUtils.clinit(ClassUtils.java:44)
   at 
 org.apache.myfaces.orchestra.annotation.spring.AnnotationsInfoInitializer.postProcessBeanFactory(AnnotationsInfoInitializer.java:93)
   at 
 org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:553)
   at 
 org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:536)
   at 
 org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:362)
   at 
 org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
   at 
 org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
   at 
 org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
   at 
 org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4523)
   at 
 org.apache.catalina.core.StandardContext.start(StandardContext.java:5184)
   at com.sun.enterprise.web.WebModule.start(WebModule.java:326)
   at 
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:973)
   at 
 org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:957)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:688)
   at 
 com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1584)
   at 
 com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1222)
   at 
 com.sun.enterprise.web.WebContainer.loadJ2EEApplicationWebModules(WebContainer.java:1147)
   at 
 com.sun.enterprise.server.TomcatApplicationLoader.doLoad(TomcatApplicationLoader.java:141)
   at 
 com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:244)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:336)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:210)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:645)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:928)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:912)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:461)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:176)
   at 
 com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
   at 
 com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:226)
   at 
 com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
   at 
 com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
   at 
 com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
   at 
 com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919)
   at 
 com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:276)
   at

[jira] Reopened: (ORCHESTRA-50) Unresolved dependency of org.apache.commons.el.Logger


 [ 
https://issues.apache.org/jira/browse/ORCHESTRA-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Korherr reopened ORCHESTRA-50:



Moved and reopened.

This is an orchestra issue: Due to the fact that orchestra uses shared version 
2.0.x, commons-el still is a dependency and has to be added to the pom.

 Unresolved dependency of org.apache.commons.el.Logger
 -

 Key: ORCHESTRA-50
 URL: https://issues.apache.org/jira/browse/ORCHESTRA-50
 Project: MyFaces Orchestra
  Issue Type: Bug
 Environment: Deploying to Glassfish v2
Reporter: Bart Kummel
Priority: Minor

 When deploying an application that uses Orchestra Core 1.3.1, I get a 
 ClassNotFoundException on org.apache.commons.el.Logger. The work around is of 
 course to manually download Apache Commons EL and add is as a dependency. The 
 solution to this bug can be:
 - removing the dependency
 - mentioning the dependency in the docs.
 Stack trace:
 java.lang.NoClassDefFoundError: org/apache/commons/el/Logger
   at 
 org.apache.myfaces.shared_orchestra.util.ClassUtils.clinit(ClassUtils.java:44)
   at 
 org.apache.myfaces.orchestra.annotation.spring.AnnotationsInfoInitializer.postProcessBeanFactory(AnnotationsInfoInitializer.java:93)
   at 
 org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:553)
   at 
 org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:536)
   at 
 org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:362)
   at 
 org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
   at 
 org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
   at 
 org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
   at 
 org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4523)
   at 
 org.apache.catalina.core.StandardContext.start(StandardContext.java:5184)
   at com.sun.enterprise.web.WebModule.start(WebModule.java:326)
   at 
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:973)
   at 
 org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:957)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:688)
   at 
 com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1584)
   at 
 com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1222)
   at 
 com.sun.enterprise.web.WebContainer.loadJ2EEApplicationWebModules(WebContainer.java:1147)
   at 
 com.sun.enterprise.server.TomcatApplicationLoader.doLoad(TomcatApplicationLoader.java:141)
   at 
 com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:244)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:336)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:210)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:645)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:928)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:912)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:461)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:176)
   at 
 com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
   at 
 com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:226)
   at 
 com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
   at 
 com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
   at 
 com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
   at 
 com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919)
   at 
 com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:276)
   at 
 com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:294)
   at 
 com.sun.enterprise.admin.mbeans.ApplicationsConfigMBean.deploy(ApplicationsConfigMBean.java:555)
   at

[jira] Created: (TRINIDAD-1756) Trinidad IFrame PPR does not work in google chrome

2010-03-15 Thread Andrew Robinson (JIRA)

Trinidad IFrame PPR does not work in google chrome
--

 Key: TRINIDAD-1756
 URL: https://issues.apache.org/jira/browse/TRINIDAD-1756
 Project: MyFaces Trinidad
  Issue Type: Bug
  Components: Components
Affects Versions: 1.2.13-core 
 Environment: Google Chrome 5.0.307.11 (Official Build 39572) beta
WebKit  532.9
V8  2.0.6.6
User Agent  Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/532.9 
(KHTML, like Gecko) Chrome/5.0.307.11 Safari/532.9
Reporter: Andrew Robinson
Assignee: Andrew Robinson
Priority: Critical


iframe based PPR, used for input file post backs does not work in google 
chrome. The resulting DOM document is just an empty HTML document:
htmlhead/headbody/body/html

The PPR contents are completely lost when the browser parses the request.

Either the payload needs to be changed or some kind of XML header needs to be 
sent down to stop Chrome from obliterating the content. My guess is that it 
sees a non-HTML page and ignores the response as invalid content.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (TRINIDAD-1756) Trinidad IFrame PPR does not work in google chrome

2010-03-15 Thread Andrew Robinson (JIRA)


[ 
https://issues.apache.org/jira/browse/TRINIDAD-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845496#action_12845496
 ] 

Andrew Robinson commented on TRINIDAD-1756:
---

Just had Matt Cooper test it and found the same results with Safari 4.0.4

 Trinidad IFrame PPR does not work in google chrome
 --

 Key: TRINIDAD-1756
 URL: https://issues.apache.org/jira/browse/TRINIDAD-1756
 Project: MyFaces Trinidad
  Issue Type: Bug
  Components: Components
Affects Versions: 1.2.13-core 
 Environment: Google Chrome5.0.307.11 (Official Build 39572) beta
 WebKit532.9
 V82.0.6.6
 User AgentMozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/532.9 
 (KHTML, like Gecko) Chrome/5.0.307.11 Safari/532.9
Reporter: Andrew Robinson
Assignee: Andrew Robinson
Priority: Critical

 iframe based PPR, used for input file post backs does not work in google 
 chrome. The resulting DOM document is just an empty HTML document:
 htmlhead/headbody/body/html
 The PPR contents are completely lost when the browser parses the request.
 Either the payload needs to be changed or some kind of XML header needs to be 
 sent down to stop Chrome from obliterating the content. My guess is that it 
 sees a non-HTML page and ignores the response as invalid content.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (ORCHESTRA-50) Unresolved dependency of org.apache.commons.el.Logger


[ 
https://issues.apache.org/jira/browse/ORCHESTRA-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845504#action_12845504
 ] 

Jakob Korherr commented on ORCHESTRA-50:


After a lot of digging I found out that commons-el should be a valid dependency 
of orchestra since orchestra has a dependency to myfaces-shared-orchestra which 
itself has a dependency to commons-el and so it should be included in the 
releases correctly. See this mvn dependency:tree:

org.apache.myfaces.orchestra:myfaces-orchestra-core:jar:1.5-SNAPSHOT
[INFO] +- org.apache.myfaces.core:myfaces-api:jar:1.1.6:provided
[INFO] |  \- javax.servlet:jstl:jar:1.1.0:provided
[INFO] +- org.apache.myfaces.shared:myfaces-shared-orchestra:jar:2.0.7:provided
[INFO] |  +- commons-el:commons-el:jar:1.0:provided
[INFO] |  \- commons-codec:commons-codec:jar:1.3:provided
// cut for clarity

In theory this should enough to have maven include it in your projects. Any 
idea why this does not work?

Maybe because the version of myfaces-shared-orchestra is set via property, but 
I really don't know.


 Unresolved dependency of org.apache.commons.el.Logger
 -

 Key: ORCHESTRA-50
 URL: https://issues.apache.org/jira/browse/ORCHESTRA-50
 Project: MyFaces Orchestra
  Issue Type: Bug
 Environment: Deploying to Glassfish v2
Reporter: Bart Kummel
Priority: Minor

 When deploying an application that uses Orchestra Core 1.3.1, I get a 
 ClassNotFoundException on org.apache.commons.el.Logger. The work around is of 
 course to manually download Apache Commons EL and add is as a dependency. The 
 solution to this bug can be:
 - removing the dependency
 - mentioning the dependency in the docs.
 Stack trace:
 java.lang.NoClassDefFoundError: org/apache/commons/el/Logger
   at 
 org.apache.myfaces.shared_orchestra.util.ClassUtils.clinit(ClassUtils.java:44)
   at 
 org.apache.myfaces.orchestra.annotation.spring.AnnotationsInfoInitializer.postProcessBeanFactory(AnnotationsInfoInitializer.java:93)
   at 
 org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:553)
   at 
 org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:536)
   at 
 org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:362)
   at 
 org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
   at 
 org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
   at 
 org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
   at 
 org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4523)
   at 
 org.apache.catalina.core.StandardContext.start(StandardContext.java:5184)
   at com.sun.enterprise.web.WebModule.start(WebModule.java:326)
   at 
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:973)
   at 
 org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:957)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:688)
   at 
 com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1584)
   at 
 com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1222)
   at 
 com.sun.enterprise.web.WebContainer.loadJ2EEApplicationWebModules(WebContainer.java:1147)
   at 
 com.sun.enterprise.server.TomcatApplicationLoader.doLoad(TomcatApplicationLoader.java:141)
   at 
 com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:244)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:336)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:210)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:645)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:928)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:912)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:461)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:176)
   at 
 com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
   at 
 com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:226)
   at

[jira] Created: (TRINIDAD-1757) Allow (or support) decorator pattern for the UploadedFileProcessor

Allow (or support) decorator pattern for the UploadedFileProcessor
--

 Key: TRINIDAD-1757
 URL: https://issues.apache.org/jira/browse/TRINIDAD-1757
 Project: MyFaces Trinidad
  Issue Type: Bug
Reporter: Matthias Weßendorf


Currently it is only possible to replace the entire UploadedFileProcessor, with 
a custom one.

A neat improvement (crap, this should not be a bug) would be supporting the 
decorator pattern.

The tricky part is that we need a buffer inside of the implementation of the 
file
that get's passed into the Processor.

currently you can call only once the getInputStream, so we need a buffer here
(that works with the impl's writeFile()/getInputStream()):
There are some ways for that. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (TRINIDAD-1757) Allow (or support) decorator pattern for the UploadedFileProcessor


[ 
https://issues.apache.org/jira/browse/TRINIDAD-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845525#action_12845525
 ] 

Matthias Weßendorf commented on TRINIDAD-1757:
--

Applying the actual decorator pattern just needs some extra lines in the 
ConfigParser.
Check for the right constructor to delegate:
-If no such constructor is there, we just use the class provided in the 
trindiad-config.xml file, w/o decoration.
= that way we have still backwards compatibility. 
-Otherwise, we decorate and stick in ours to the one provided by the customer.

 Allow (or support) decorator pattern for the UploadedFileProcessor
 --

 Key: TRINIDAD-1757
 URL: https://issues.apache.org/jira/browse/TRINIDAD-1757
 Project: MyFaces Trinidad
  Issue Type: Improvement
Reporter: Matthias Weßendorf

 Currently it is only possible to replace the entire UploadedFileProcessor, 
 with a custom one.
 A neat improvement (crap, this should not be a bug) would be supporting the 
 decorator pattern.
 The tricky part is that we need a buffer inside of the implementation of the 
 file
 that get's passed into the Processor.
 currently you can call only once the getInputStream, so we need a buffer 
 here
 (that works with the impl's writeFile()/getInputStream()):
 There are some ways for that. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (TRINIDAD-1757) Allow (or support) decorator pattern for the UploadedFileProcessor


[ 
https://issues.apache.org/jira/browse/TRINIDAD-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845528#action_12845528
 ] 

Matthias Weßendorf commented on TRINIDAD-1757:
--

The tricky part is the handling of the input stream (its buffering)
However, it is kinda odd that the JavaDoc says getInputStream can be called 
repeatedly,
since the processFile() takes an _internal_ impl of the UploadedFile. This guy 
does not allow
getInputStream() called repeatedly so a customer could be confused here.. 
That's why we
need some buffer/byte-array...

The implementation of the passed in UploadedFile points to the IMPL-specific 
MultipartFormItem interface implementation:
== MultipartFormItemImpl

Its writeFile/getInputStream() check if they have been called (and cause the 
trouble).
So here we need to introduce the buffer. 

 Allow (or support) decorator pattern for the UploadedFileProcessor
 --

 Key: TRINIDAD-1757
 URL: https://issues.apache.org/jira/browse/TRINIDAD-1757
 Project: MyFaces Trinidad
  Issue Type: Improvement
Reporter: Matthias Weßendorf

 Currently it is only possible to replace the entire UploadedFileProcessor, 
 with a custom one.
 A neat improvement (crap, this should not be a bug) would be supporting the 
 decorator pattern.
 The tricky part is that we need a buffer inside of the implementation of the 
 file
 that get's passed into the Processor.
 currently you can call only once the getInputStream, so we need a buffer 
 here
 (that works with the impl's writeFile()/getInputStream()):
 There are some ways for that. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (ORCHESTRA-50) Unresolved dependency of org.apache.commons.el.Logger

2010-03-15 Thread Aleksei Valikov (JIRA)


[ 
https://issues.apache.org/jira/browse/ORCHESTRA-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845535#action_12845535
 ] 

Aleksei Valikov commented on ORCHESTRA-50:
--

Clearly because myfaces-shared-orchestra is a provided-scope dependency. The 
classes are added to the jar so the dependency is made provided.

Possible solutions are:
* add commons-el to the orchestra dependencies
* move to a later version of myfaces-shared-orchestra
* rewrite the orchestra code to avoid dependencies of myfaces-shared

 Unresolved dependency of org.apache.commons.el.Logger
 -

 Key: ORCHESTRA-50
 URL: https://issues.apache.org/jira/browse/ORCHESTRA-50
 Project: MyFaces Orchestra
  Issue Type: Bug
 Environment: Deploying to Glassfish v2
Reporter: Bart Kummel
Priority: Minor

 When deploying an application that uses Orchestra Core 1.3.1, I get a 
 ClassNotFoundException on org.apache.commons.el.Logger. The work around is of 
 course to manually download Apache Commons EL and add is as a dependency. The 
 solution to this bug can be:
 - removing the dependency
 - mentioning the dependency in the docs.
 Stack trace:
 java.lang.NoClassDefFoundError: org/apache/commons/el/Logger
   at 
 org.apache.myfaces.shared_orchestra.util.ClassUtils.clinit(ClassUtils.java:44)
   at 
 org.apache.myfaces.orchestra.annotation.spring.AnnotationsInfoInitializer.postProcessBeanFactory(AnnotationsInfoInitializer.java:93)
   at 
 org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:553)
   at 
 org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:536)
   at 
 org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:362)
   at 
 org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
   at 
 org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
   at 
 org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
   at 
 org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4523)
   at 
 org.apache.catalina.core.StandardContext.start(StandardContext.java:5184)
   at com.sun.enterprise.web.WebModule.start(WebModule.java:326)
   at 
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:973)
   at 
 org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:957)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:688)
   at 
 com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1584)
   at 
 com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1222)
   at 
 com.sun.enterprise.web.WebContainer.loadJ2EEApplicationWebModules(WebContainer.java:1147)
   at 
 com.sun.enterprise.server.TomcatApplicationLoader.doLoad(TomcatApplicationLoader.java:141)
   at 
 com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:244)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:336)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:210)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:645)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:928)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:912)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:461)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:176)
   at 
 com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
   at 
 com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:226)
   at 
 com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
   at 
 com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
   at 
 com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
   at 
 com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919)
   at 
 com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:276)
   at

[jira] Commented: (MYFACESTEST-4) Unable to call setValue of ValueExpression in test


[ 
https://issues.apache.org/jira/browse/MYFACESTEST-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845427#action_12845427
 ] 

Jakob Korherr commented on MYFACESTEST-4:
-

Oh, I almost forgot: The MyFaces test code for 2.0 uses most of the parts of 
MyFaces test 1.2. Also the class for which you provided the patch 
(MockApplication12) is from MyFaces test 1.2. So there is no need to change 
this twice!

 Unable to call setValue of ValueExpression in test
 --

 Key: MYFACESTEST-4
 URL: https://issues.apache.org/jira/browse/MYFACESTEST-4
 Project: Apache MyFaces Test
  Issue Type: Bug
 Environment: See attached JUnit test case which fails with 
 myfaces-test20-1.0.0-SNAPSHOT
 Tested with Mojarra-2.0.2
Reporter: Christoph Göldner
Assignee: Jakob Korherr
 Attachments: MockApplication12.patch, ValueExpressionTest.java


 Components tested inside a test case inherited from AbstractJsfTestCase are 
 not able to do following:
   ELContext elContext = facesContext.getELContext();
   ValueExpression ve = 
 application.getExpressionFactory().createValueExpression(elContext, #{foo}, 
 String.class);
   ve.setValue(elContext, BAR);
 The error is caused by the FacesResourceBundleELResolver inside the setValue 
 method, where it tries to get a ResourceBundle from MockApplication12 for the 
 given ValueExpression. Unfortunately the MockApplication12 getResourceBundle 
 method throws a MissingResourceException instead of returning null.
 Please apply attached patch to the code base.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (MYFACESTEST-4) Unable to call setValue of ValueExpression in test


 [ 
https://issues.apache.org/jira/browse/MYFACESTEST-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Korherr updated MYFACESTEST-4:


Resolution: Fixed
Status: Resolved  (was: Patch Available)

 Unable to call setValue of ValueExpression in test
 --

 Key: MYFACESTEST-4
 URL: https://issues.apache.org/jira/browse/MYFACESTEST-4
 Project: Apache MyFaces Test
  Issue Type: Bug
 Environment: See attached JUnit test case which fails with 
 myfaces-test20-1.0.0-SNAPSHOT
 Tested with Mojarra-2.0.2
Reporter: Christoph Göldner
Assignee: Jakob Korherr
 Attachments: MockApplication12.patch, ValueExpressionTest.java


 Components tested inside a test case inherited from AbstractJsfTestCase are 
 not able to do following:
   ELContext elContext = facesContext.getELContext();
   ValueExpression ve = 
 application.getExpressionFactory().createValueExpression(elContext, #{foo}, 
 String.class);
   ve.setValue(elContext, BAR);
 The error is caused by the FacesResourceBundleELResolver inside the setValue 
 method, where it tries to get a ResourceBundle from MockApplication12 for the 
 given ValueExpression. Unfortunately the MockApplication12 getResourceBundle 
 method throws a MissingResourceException instead of returning null.
 Please apply attached patch to the code base.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (MYFACESTEST-4) Unable to call setValue of ValueExpression in test


[ 
https://issues.apache.org/jira/browse/MYFACESTEST-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845424#action_12845424
 ] 

Jakob Korherr commented on MYFACESTEST-4:
-

Thank you very much for the patch and the test case for this one and also for 
MYFACESTEST-5, Christoph.

However, please try to follow the code guidelines of MyFaces in your next 
patch(es). I know, the code in MyFaces test does not really do this either, but 
if we keep on committing the code in any style, it will become a bigger mess 
with every commit.

 Unable to call setValue of ValueExpression in test
 --

 Key: MYFACESTEST-4
 URL: https://issues.apache.org/jira/browse/MYFACESTEST-4
 Project: Apache MyFaces Test
  Issue Type: Bug
 Environment: See attached JUnit test case which fails with 
 myfaces-test20-1.0.0-SNAPSHOT
 Tested with Mojarra-2.0.2
Reporter: Christoph Göldner
Assignee: Jakob Korherr
 Attachments: MockApplication12.patch, ValueExpressionTest.java


 Components tested inside a test case inherited from AbstractJsfTestCase are 
 not able to do following:
   ELContext elContext = facesContext.getELContext();
   ValueExpression ve = 
 application.getExpressionFactory().createValueExpression(elContext, #{foo}, 
 String.class);
   ve.setValue(elContext, BAR);
 The error is caused by the FacesResourceBundleELResolver inside the setValue 
 method, where it tries to get a ResourceBundle from MockApplication12 for the 
 given ValueExpression. Unfortunately the MockApplication12 getResourceBundle 
 method throws a MissingResourceException instead of returning null.
 Please apply attached patch to the code base.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (MYFACESTEST-5) Implementation of MockHttpSession.invalidate()


 [ 
https://issues.apache.org/jira/browse/MYFACESTEST-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jakob Korherr updated MYFACESTEST-5:


Resolution: Fixed
Status: Resolved  (was: Patch Available)

I committed the patch and a simple test case to test this method.

 Implementation of MockHttpSession.invalidate()
 --

 Key: MYFACESTEST-5
 URL: https://issues.apache.org/jira/browse/MYFACESTEST-5
 Project: Apache MyFaces Test
  Issue Type: Improvement
Reporter: Christoph Göldner
Assignee: Jakob Korherr
 Attachments: MockHttpSession.patch


 Currently MockHttpSession.invalidate() throws an 
 UnsupportedOperationException.
 See attached patch which implements the invalidate() logic inside 
 MockHttpSession.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (ORCHESTRA-50) Unresolved dependency of org.apache.commons.el.Logger

2010-03-15 Thread Leonardo Uribe (JIRA)


[ 
https://issues.apache.org/jira/browse/ORCHESTRA-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845551#action_12845551
 ] 

Leonardo Uribe commented on ORCHESTRA-50:
-

We should remove the commons-el dependency from shared. This dependency was 
removed from shared 3.0.x and 4.0.x, but on 2.0.x was not (but in theory code 
is never used). The problem here is orchestra jars are used on jsf 1.2. Anyway, 
before remove it we should check if myfaces core 1.1.x and if so, update/move 
the code from commons-el to prevent this dependency.

 Unresolved dependency of org.apache.commons.el.Logger
 -

 Key: ORCHESTRA-50
 URL: https://issues.apache.org/jira/browse/ORCHESTRA-50
 Project: MyFaces Orchestra
  Issue Type: Bug
 Environment: Deploying to Glassfish v2
Reporter: Bart Kummel
Priority: Minor

 When deploying an application that uses Orchestra Core 1.3.1, I get a 
 ClassNotFoundException on org.apache.commons.el.Logger. The work around is of 
 course to manually download Apache Commons EL and add is as a dependency. The 
 solution to this bug can be:
 - removing the dependency
 - mentioning the dependency in the docs.
 Stack trace:
 java.lang.NoClassDefFoundError: org/apache/commons/el/Logger
   at 
 org.apache.myfaces.shared_orchestra.util.ClassUtils.clinit(ClassUtils.java:44)
   at 
 org.apache.myfaces.orchestra.annotation.spring.AnnotationsInfoInitializer.postProcessBeanFactory(AnnotationsInfoInitializer.java:93)
   at 
 org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:553)
   at 
 org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:536)
   at 
 org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:362)
   at 
 org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
   at 
 org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
   at 
 org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
   at 
 org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4523)
   at 
 org.apache.catalina.core.StandardContext.start(StandardContext.java:5184)
   at com.sun.enterprise.web.WebModule.start(WebModule.java:326)
   at 
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:973)
   at 
 org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:957)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:688)
   at 
 com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1584)
   at 
 com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1222)
   at 
 com.sun.enterprise.web.WebContainer.loadJ2EEApplicationWebModules(WebContainer.java:1147)
   at 
 com.sun.enterprise.server.TomcatApplicationLoader.doLoad(TomcatApplicationLoader.java:141)
   at 
 com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:244)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:336)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:210)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:645)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:928)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:912)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:461)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:176)
   at 
 com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
   at 
 com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:226)
   at 
 com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
   at 
 com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
   at 
 com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
   at 
 com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:919)
   at 
 com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:276)
   at

[jira] Resolved: (TRINIDAD-1756) Trinidad IFrame PPR does not work in google chrome

2010-03-15 Thread Andrew Robinson (JIRA)


 [ 
https://issues.apache.org/jira/browse/TRINIDAD-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Robinson resolved TRINIDAD-1756.
---

   Resolution: Fixed
Fix Version/s: 2.0.0.3-core
   1.2.14-core 

Fixed in Safari and Chrome. Tested using Chrome beta on mac and linux and 
Safari on mac.

 Trinidad IFrame PPR does not work in google chrome
 --

 Key: TRINIDAD-1756
 URL: https://issues.apache.org/jira/browse/TRINIDAD-1756
 Project: MyFaces Trinidad
  Issue Type: Bug
  Components: Components
Affects Versions: 1.2.13-core 
 Environment: Google Chrome5.0.307.11 (Official Build 39572) beta
 WebKit532.9
 V82.0.6.6
 User AgentMozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/532.9 
 (KHTML, like Gecko) Chrome/5.0.307.11 Safari/532.9
Reporter: Andrew Robinson
Assignee: Andrew Robinson
Priority: Critical
 Fix For: 1.2.14-core , 2.0.0.3-core


 iframe based PPR, used for input file post backs does not work in google 
 chrome. The resulting DOM document is just an empty HTML document:
 htmlhead/headbody/body/html
 The PPR contents are completely lost when the browser parses the request.
 Either the payload needs to be changed or some kind of XML header needs to be 
 sent down to stop Chrome from obliterating the content. My guess is that it 
 sees a non-HTML page and ignores the response as invalid content.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (MYFACES-2605) java.lang.LinkageError loader constraint violation: loader (instance of org/mortbay/jetty/webapp/WebAppClassLoader) previously initiated loading for a different type wit

java.lang.LinkageError loader constraint violation: loader (instance of 
org/mortbay/jetty/webapp/WebAppClassLoader) previously initiated loading for a 
different type with name javax/el/ExpressionFactory


 Key: MYFACES-2605
 URL: https://issues.apache.org/jira/browse/MYFACES-2605
 Project: MyFaces Core
  Issue Type: Bug
  Components: JSR-314
Affects Versions: 2.0.0-beta-3
Reporter: Matthias Weßendorf


running Trinidad 2.x (trunk) with the MyFaces2 trunk, gives me this error:

(you don't see that with the older beta-2 release...


java.lang.LinkageError: loader constraint violation: loader (instance of 
org/mortbay/jetty/webapp/WebAppClassLoader) previously initiated loading for a 
different type with name javax/el/ExpressionFactory
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at 
org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:392)
at 
org.mortbay.jetty.webapp.WebAppClassLoader.loadClass(WebAppClassLoader.java:363)
at 
org.apache.myfaces.trinidadinternal.config.LazyValueExpression._createValueExpressionFromApplication(LazyValueExpression.java:182)
at 
org.apache.myfaces.trinidadinternal.config.LazyValueExpression.createValueExpression(LazyValueExpression.java:56)
at 
org.apache.myfaces.trinidadinternal.skin.SkinUtils._createTranslationSourceValueExpression(SkinUtils.java:649)
at 
org.apache.myfaces.trinidadinternal.skin.SkinUtils._addSkinToFactory(SkinUtils.java:612)
at 
org.apache.myfaces.trinidadinternal.skin.SkinUtils._registerSkinExtensionsAndAdditions(SkinUtils.java:411)
at 
org.apache.myfaces.trinidadinternal.skin.SkinUtils.registerSkinExtensions(SkinUtils.java:131)
at 
org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.init(GlobalConfiguratorImpl.java:409)
at 
org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.beginRequest(GlobalConfiguratorImpl.java:208)
at 
org.apache.myfaces.trinidadinternal.config.GlobalConfiguratorImpl.getExternalContext(GlobalConfiguratorImpl.java:331)
at 
org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl$CacheRenderKit.init(FacesContextFactoryImpl.java:90)
at 
org.apache.myfaces.trinidadinternal.context.FacesContextFactoryImpl.getFacesContext(FacesContextFactoryImpl.java:68)
at 
org.apache.myfaces.webapp.AbstractFacesInitializer.dispatchInitDestroyEvent(AbstractFacesInitializer.java:195)
at 
org.apache.myfaces.webapp.AbstractFacesInitializer.initFaces(AbstractFacesInitializer.java:124)
at 
org.apache.myfaces.webapp.StartupServletContextListener.initFaces(StartupServletContextListener.java:182)
at 
org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:155)
at 
org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:548)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
at 
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1250)
at 
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
at 
org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
at 
org.mortbay.jetty.plugin.Jetty6PluginWebAppContext.doStart(Jetty6PluginWebAppContext.java:115)
at 
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at 
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at 
org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:156)
at 
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at 
org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:152)
at 
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at 
org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:224)
at 
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at

[jira] Commented: (ORCHESTRA-50) Unresolved dependency of org.apache.commons.el.Logger

2010-03-15 Thread Leonardo Uribe (JIRA)


[ 
https://issues.apache.org/jira/browse/ORCHESTRA-50?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845582#action_12845582
 ] 

Leonardo Uribe commented on ORCHESTRA-50:
-

Myfaces core 1.1.x depends on commons-el in many parts. So, the solution I 
propose is do not call ClassUtils.convertToType from myfaces core, and call 
directly to Coercions.coerce. If some code somewhere else uses this call, copy 
the required core to shared an make it class scoped, so the code will continue 
working and we can finally kick out commons-el dependency from shared and also 
for orchestra.

If no objections I'll commit this code soon.

 Unresolved dependency of org.apache.commons.el.Logger
 -

 Key: ORCHESTRA-50
 URL: https://issues.apache.org/jira/browse/ORCHESTRA-50
 Project: MyFaces Orchestra
  Issue Type: Bug
 Environment: Deploying to Glassfish v2
Reporter: Bart Kummel
Priority: Minor
 Attachments: ORCHESTRA-50-core.patch, ORCHESTRA-50-shared.patch


 When deploying an application that uses Orchestra Core 1.3.1, I get a 
 ClassNotFoundException on org.apache.commons.el.Logger. The work around is of 
 course to manually download Apache Commons EL and add is as a dependency. The 
 solution to this bug can be:
 - removing the dependency
 - mentioning the dependency in the docs.
 Stack trace:
 java.lang.NoClassDefFoundError: org/apache/commons/el/Logger
   at 
 org.apache.myfaces.shared_orchestra.util.ClassUtils.clinit(ClassUtils.java:44)
   at 
 org.apache.myfaces.orchestra.annotation.spring.AnnotationsInfoInitializer.postProcessBeanFactory(AnnotationsInfoInitializer.java:93)
   at 
 org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:553)
   at 
 org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:536)
   at 
 org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:362)
   at 
 org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
   at 
 org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
   at 
 org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
   at 
 org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4523)
   at 
 org.apache.catalina.core.StandardContext.start(StandardContext.java:5184)
   at com.sun.enterprise.web.WebModule.start(WebModule.java:326)
   at 
 org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:973)
   at 
 org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:957)
   at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:688)
   at 
 com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1584)
   at 
 com.sun.enterprise.web.WebContainer.loadWebModule(WebContainer.java:1222)
   at 
 com.sun.enterprise.web.WebContainer.loadJ2EEApplicationWebModules(WebContainer.java:1147)
   at 
 com.sun.enterprise.server.TomcatApplicationLoader.doLoad(TomcatApplicationLoader.java:141)
   at 
 com.sun.enterprise.server.AbstractLoader.load(AbstractLoader.java:244)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:336)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:210)
   at 
 com.sun.enterprise.server.ApplicationManager.applicationDeployed(ApplicationManager.java:645)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.invokeApplicationDeployEventListener(AdminEventMulticaster.java:928)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.handleApplicationDeployEvent(AdminEventMulticaster.java:912)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.processEvent(AdminEventMulticaster.java:461)
   at 
 com.sun.enterprise.admin.event.AdminEventMulticaster.multicastEvent(AdminEventMulticaster.java:176)
   at 
 com.sun.enterprise.admin.server.core.DeploymentNotificationHelper.multicastEvent(DeploymentNotificationHelper.java:308)
   at 
 com.sun.enterprise.deployment.phasing.DeploymentServiceUtils.multicastEvent(DeploymentServiceUtils.java:226)
   at 
 com.sun.enterprise.deployment.phasing.ServerDeploymentTarget.sendStartEvent(ServerDeploymentTarget.java:298)
   at 
 com.sun.enterprise.deployment.phasing.ApplicationStartPhase.runPhase(ApplicationStartPhase.java:132)
   at 
 com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108)
   at

[Trinidad] Plugins for 2.x making trunk ?

2010-03-15 Thread Matthias Wessendorf

Hi,

since we now moved the trinidad2 stuff to be trunk, I'd also move over
the plugins for 2.x

Any objections?

-Matthias

-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf

Re: [Trinidad] Plugins for 2.x making trunk ?

2010-03-15 Thread Gerhard Petracek

+1

regards,
gerhard

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces


2010/3/16 Matthias Wessendorf mat...@apache.org

 Hi,

 since we now moved the trinidad2 stuff to be trunk, I'd also move over
 the plugins for 2.x

 Any objections?

 -Matthias

 --
 Matthias Wessendorf

 blog: http://matthiaswessendorf.wordpress.com/
 sessions: http://www.slideshare.net/mwessendorf
 twitter: http://twitter.com/mwessendorf

[jira] Created: (MYFACES-2606) javax.crypto.BadPaddingException on Google App Engine

javax.crypto.BadPaddingException on Google App Engine
-

 Key: MYFACES-2606
 URL: https://issues.apache.org/jira/browse/MYFACES-2606
 Project: MyFaces Core
  Issue Type: Bug
  Components: JSR-314
Affects Versions: 2.0.0-beta-3
 Environment: Google App Engine
Reporter: Ali Ok


javax.crypto.BadPaddingException is thrown after some time (a few minutes) 
while restoring the state on Google App Engine.
Some discussion on https://issues.apache.org/jira/browse/MYFACES-2559.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (MYFACES-2606) javax.crypto.BadPaddingException on Google App Engine


[ 
https://issues.apache.org/jira/browse/MYFACES-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845608#action_12845608
 ] 

Ali Ok commented on MYFACES-2606:
-

I found the reason:
StartupServletContextListener.contextInitialized is called after some time(ie. 
5 minutes).
This results in a BadPaddingException since encoding key of viewstate is 
re-generated, thus viewstate cannot be encoded.

There is a check if private servletContext is set, but even states of other 
stuff is OK, StartupServletContextListener is recreated and so servletContext 
is gone.
This can be solved with specifying the org.apache.myfaces.SECRET context param, 
but I will find another a way to solve this problem.

There is a bug report [1] for this problem on GAE.

[1]: http://code.google.com/p/googleappengine/issues/detail?id=1828

 javax.crypto.BadPaddingException on Google App Engine
 -

 Key: MYFACES-2606
 URL: https://issues.apache.org/jira/browse/MYFACES-2606
 Project: MyFaces Core
  Issue Type: Bug
  Components: JSR-314
Affects Versions: 2.0.0-beta-3
 Environment: Google App Engine
Reporter: Ali Ok

 javax.crypto.BadPaddingException is thrown after some time (a few minutes) 
 while restoring the state on Google App Engine.
 Some discussion on https://issues.apache.org/jira/browse/MYFACES-2559.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Issue Comment Edited: (MYFACES-2606) javax.crypto.BadPaddingException on Google App Engine

[
https://issues.apache.org/jira/browse/MYFACES-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845608#action_12845608
]

Ali Ok edited comment on MYFACES-2606 at 3/16/10 12:08 AM:
---

I found the reason:
StartupServletContextListener.contextInitialized is called after some time(ie.
5 minutes).
This results in a BadPaddingException since encoding key of viewstate is
re-generated, thus viewstate cannot be decoded.

There is a check if private servletContext is set, but even states of other
stuff is OK, StartupServletContextListener is recreated and so servletContext
is gone.
This can be solved with specifying the org.apache.myfaces.SECRET context param,
but I will find another a way to solve this problem.

There is a bug report [1] for this problem on GAE.

[1]: http://code.google.com/p/googleappengine/issues/detail?id=1828

was (Author: aliok-com-tr):
I found the reason:
StartupServletContextListener.contextInitialized is called after some time(ie.
5 minutes).
This results in a BadPaddingException since encoding key of viewstate is
re-generated, thus viewstate cannot be encoded.

There is a bug report [1] for this problem on GAE.

[1]: http://code.google.com/p/googleappengine/issues/detail?id=1828

javax.crypto.BadPaddingException on Google App Engine
-

Key: MYFACES-2606
URL: https://issues.apache.org/jira/browse/MYFACES-2606
Project: MyFaces Core
Issue Type: Bug
Components: JSR-314
Affects Versions: 2.0.0-beta-3
Environment: Google App Engine
Reporter: Ali Ok

javax.crypto.BadPaddingException is thrown after some time (a few minutes)
while restoring the state on Google App Engine.
Some discussion on https://issues.apache.org/jira/browse/MYFACES-2559.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (MYFACES-2559) Google App Engine Support for Myfaces 2


[ 
https://issues.apache.org/jira/browse/MYFACES-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12845612#action_12845612
 ] 

Ali Ok commented on MYFACES-2559:
-

I fired another ticket for this problem:
https://issues.apache.org/jira/browse/MYFACES-2606

 Google App Engine Support for Myfaces 2
 ---

 Key: MYFACES-2559
 URL: https://issues.apache.org/jira/browse/MYFACES-2559
 Project: MyFaces Core
  Issue Type: Improvement
  Components: JSR-314
Affects Versions: 2.0.0-beta
 Environment: Google App Engine
Reporter: Ali Ok
Assignee: Matthias Weßendorf
Priority: Minor
 Fix For: 2.0.0-beta-3

 Attachments: 2559-doc.patch, 2559.patch


 Google App Engine Support for Myfaces 2

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (TRINIDAD-1758) warnings with the new skin