Re: 4 second page response time
En l'instant précis du 20/07/07 15:02, Martin Denham s'exprimait en ces termes: I have had a performance issue with both the JSF applications I have written. On my windows xp development pc responses are instant. However when deployed to a Sun Ultra 80 Solaris machine every page takes 4 seconds and if I add a redirect the response time increases to 7 seconds. Another application on the same Solaris machine, but written using Struts has instant page response times. Is a simple page response time of 4 seconds expected when using JSF? I have tried all sorts of tweaks during the past year but the response time is unaffected. Simple answere: no. I will have to profile your application to find out where your CPU bottleneck (if it's a CPU bottleneck) is, or where your network bottleneck is. Because JSF uses value binding which can do lots of things, any badly written/badly used bean can be at cause (like a bean loading 50.000 items for a database at each request). Simple suggestion: when you load a JSF page, go in a console to your solaris station and run a kill -3 JVMpid, this will dump to the jvm's stdout a stacktrace of all running threads. From there you could see where the code is waiting / busy. could it be some xml parser uses a xsd/dtd which is not available. If production server is firewalled, maybe the server is just trying to download the schema/dtd and finishes on a timeout of approx 4 seconds? I am using Myfaces tomahawk 1.1.5, Weblogic 8.1sp4, Facelets 1.1.12. One application uses Oracle ADF and the other Ajax4Jsf/Richfaces. Thanks in advance for any pointers. Martin -- http://www.noooxml.org/
AW: [Trinidad] Skin-Bug on AIX
Hello, After some time in other projects and more research fort his bug I have found something. The css file is generated correctly, with compressed styleclass names as it should be. In the generated html code the uncompressed style classes are used, so the names in the css file and in the html file are different. Markus PS. No, I don't get any warnings/errors ect. -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Matthias Wessendorf Gesendet: Freitag, 29. Juni 2007 15:20 An: MyFaces Discussion Betreff: Re: [Trinidad] Skin-Bug on AIX I see. So, you don't get warnings/errors/exceptions ? Anything noticed, during debugging Trinidad ? -M On 6/29/07, Döring Markus [EMAIL PROTECTED] wrote: Yes, retroweaved version works fine on windows + WebSphere and also on windows + JBoss, only AIX + WebSphere makes problems. Because the AIX is located at our costumer and they are very careful with software updates on these machines I don't think testing on AIX with Java5 is an option. I wish we had the hardware for AIX to test it self. -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Matthias Wessendorf Gesendet: Freitag, 29. Juni 2007 14:18 An: MyFaces Discussion Betreff: Re: [Trinidad] Skin-Bug on AIX So, the retroweaved version on windoze and WebSphere, running on Java1.4, works fine ? Any chance to *test* on AIX w/ WebSphere and Java5 ? Just to test the skins? Just curious. -M On 6/29/07, Döring Markus [EMAIL PROTECTED] wrote: Hello, the folder \adf\styles\cache exists on the AIX machine, and there are also .css files generated into the folder( scis-desktop-1_0_0-incubating-en-ie-6.css scis-desktop-1_0_0-incubating-ie-6.css ) The demo could not be deployed because the AIX and the WebSphere running on Java1.4. For our application we use a retroweaved trinidad version. Markus Döring -Ursprüngliche Nachricht- Von: Döring Markus [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 27. Juni 2007 09:39 An: MyFaces Discussion Betreff: AW: [Trinidad] Skin-Bug on AIX Hello, Thanks for the quick reply. I didn't tested the demo app yet, the problem is that the AIX is located by a customer so the testing is a bit tricky, will try to test the demo app if possible. I will also check if the folder is created. Thanks for help Markus Döring TCC Products GmbH Anwendungsentwicklung Benzstr. 3 71696 Möglingen mail: [EMAIL PROTECTED] -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Matthias Wessendorf Gesendet: Mittwoch, 27. Juni 2007 09:30 An: MyFaces Discussion Betreff: Re: [Trinidad] Skin-Bug on AIX Also, is there something generated in your work directory, which is something like this (in tomcat..) apache-tomcat- 5.5.16\work\Catalina\localhost\nameOfMyApp\adf\styles\cache On 6/27/07, Matthias Wessendorf [EMAIL PROTECTED] wrote: Hi Markus, is that true for the demo - app as well ? -Matthias On 6/27/07, Döring Markus [EMAIL PROTECTED] wrote: Hello, We currently developed a wizard application with MyFaces 1.1.5, Facelets 1.1.11 and Trinidad 1.0.0-incubating. For development we use JBoss on Windows XP Machines, for testing we use WebSphere on Windows and WebSphere on AIX. On JBoss and WebShere on Windows everything works fine. Only on WebShere on AIX the skinning don't work. Everything else works fine, but the Trinidad Skins are completely ignored (e.g. validator error messages on InputText is not displayed in red). Are there any known issues with the skin generation on AIX? Maybe some problems with the rights on folders where files are created? Has someone else already used Trinidad on a similar environment? There are no Exceptions, Error Messages, ect. just the skin has no effect. Thanks for help Markus Döring TCC Products GmbH Anwendungsentwicklung Benzstr. 3 71696 Möglingen mail: [EMAIL PROTECTED] -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/
Re: [tobago] an unexpected block is executed with RI 1.2 (in JBoss 4.2.1 GA) // TODO: remove this if block if prooven this never happens anymore
Thxs Bernd,
I think I'll try to install MF 1.2. I didn't compile code from maven until
now, but as I go through, I realize it's more and more necessairy. Why
aren't the nightly builds posted every night?, does it depend on test
results?
Regards,
Zied
2007/7/22, Bernd Bohmann [EMAIL PROTECTED]:
Hello Zied,
the sheet issue should be fixed on trunk.
Please try the next nightly build.
Regards
Bernd
Zied Hamdi wrote:
Hi friends,
I have experienced a problem that seems to come back from rip :-). Seen
that
JBoss 4.2 is now based on tomcat 6 and supports EJB3, I've decided to
jump
my app into it. The problem is that it doesn't rely on myfaces core
anymore,
today to support the JSF 1.2 spec, it uses the sun implementation and
says
it shouldn't expose any problem to use myFaces components with it:
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5AndMyFaces
When I start my app, I have on the first page a visual bug with icons
that
appear before the sheet (see picture) : this doesn't happen when I use
myFaces core. Then on my first click I have the following exception
stack
trace. Looking at the source I found that the code shouldn't enter this
section:
// *TODO*: remove this if block if prooven this never happens anymore
*if* (command == *null*
currentActionId != *null*
currentActionId.matches(.*:\\d+:.*))
{
// If currentActionId component was inside a sheet the id contains
the
// rowindex and is therefore not found here.
// We do not need the row here because we want just to find the
// related form, so removing the rowindex will help here.
currentActionId = currentActionId.replaceAll(:\\d+:, :);
*try* {
command = findComponent(currentActionId);
*LOG*.*info*(command = \ + command + \, *new* Exception());
} *catch* (Exception e) {
// ignore
}
11:14:24,229 INFO [STDOUT] 2007-07-20 11:14:24,229 [
http-127.0.0.1-8080-2]
ERROR
org.apache.myfaces.tobago.context.ResourceManagerImpl.getRenderer(348)
- Don't find any RendererClass for org.apache.myfaces.ScheduleRenderer.
Please check you configuration.
11:14:24,244 INFO [STDOUT] 2007-07-20 11:14:24,244 [
http-127.0.0.1-8080-2]
INFO org.apache.myfaces.tobago.util.DebugPhaseListener.afterPhase(65) -
Total response time : 5936 milliseconds
11:14:24,260 INFO [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter
(204)
- No context init parameter 'org.apache.myfaces.PRETTY_HTML' found,
using
default value true
11:14:24,260 INFO [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter
(204)
- No context init parameter 'org.apache.myfaces.ALLOW_JAVASCRIPT' found,
using default value true
11:14:24,260 INFO [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter
(204)
- No context init parameter '
org.apache.myfaces.READONLY_AS_DISABLED_FOR_SE
LECTS' found, using default value true
11:14:24,260 INFO [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter
(204)
- No context init parameter 'org.apache.myfaces.DETECT_JAVASCRIPT'
found,
using default value false
11:14:24,260 INFO [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter
(204)
- No context init parameter 'org.apache.myfaces.AUTO_SCROLL' found,
using
default value false
11:14:24,260 INFO [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getStringInitParameter
(229)
- No context init parameter 'org.apache.myfaces.ADD_RESOURCE_CLASS'
found,
using default value
org.apache.myfaces.renderkit.html.util.DefaultAddResource
11:14:24,276 INFO [STDOUT] 2007-07-20 11:14:24,276 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getStringInitParameter
(229)
- No context init parameter 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH'
found, using default value /faces/myFacesExtensionResource
11:14:24,276 INFO [STDOUT] 2007-07-20 11:14:24,276 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter
(204)
- No context init parameter 'org.apache.myfaces.CHECK_EXTENSIONS_FILTER'
found, using default value true
11:14:24,276 INFO [STDOUT] 2007-07-20 11:14:24,276 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getCurrentInstance
(177)
- Starting up Tomahawk on the RI-JSF-Implementation.
11:14:36,897 INFO [STDOUT] 2007-07-20 11:14:36,866 [
http-127.0.0.1-8080-3]
INFO
Re: [tobago] an unexpected block is executed with RI 1.2 (in JBoss 4.2.1 GA) // TODO: remove this if block if prooven this never happens anymore
Hello Zied,
the nightly build should posted every night when no compile or test
failures occurs. Unfortunately the continuum version (1.1-alpha-1) has
some memory issues :-(
The nightly build from 22-Jul-2007 on
http://people.apache.org/builds/myfaces/nightly/ should contain the
sheet fix.
Regards
Bernd
Zied Hamdi wrote:
Thxs Bernd,
I think I'll try to install MF 1.2. I didn't compile code from maven until
now, but as I go through, I realize it's more and more necessairy. Why
aren't the nightly builds posted every night?, does it depend on test
results?
Regards,
Zied
2007/7/22, Bernd Bohmann [EMAIL PROTECTED]:
Hello Zied,
the sheet issue should be fixed on trunk.
Please try the next nightly build.
Regards
Bernd
Zied Hamdi wrote:
Hi friends,
I have experienced a problem that seems to come back from rip :-). Seen
that
JBoss 4.2 is now based on tomcat 6 and supports EJB3, I've decided to
jump
my app into it. The problem is that it doesn't rely on myfaces core
anymore,
today to support the JSF 1.2 spec, it uses the sun implementation and
says
it shouldn't expose any problem to use myFaces components with it:
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5AndMyFaces
When I start my app, I have on the first page a visual bug with icons
that
appear before the sheet (see picture) : this doesn't happen when I use
myFaces core. Then on my first click I have the following exception
stack
trace. Looking at the source I found that the code shouldn't enter this
section:
// *TODO*: remove this if block if prooven this never happens
anymore
*if* (command == *null*
currentActionId != *null*
currentActionId.matches(.*:\\d+:.*))
{
// If currentActionId component was inside a sheet the id contains
the
// rowindex and is therefore not found here.
// We do not need the row here because we want just to find the
// related form, so removing the rowindex will help here.
currentActionId = currentActionId.replaceAll(:\\d+:, :);
*try* {
command = findComponent(currentActionId);
*LOG*.*info*(command = \ + command + \, *new*
Exception());
} *catch* (Exception e) {
// ignore
}
11:14:24,229 INFO [STDOUT] 2007-07-20 11:14:24,229 [
http-127.0.0.1-8080-2]
ERROR
org.apache.myfaces.tobago.context.ResourceManagerImpl.getRenderer(348)
- Don't find any RendererClass for org.apache.myfaces.ScheduleRenderer.
Please check you configuration.
11:14:24,244 INFO [STDOUT] 2007-07-20 11:14:24,244 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.tobago.util.DebugPhaseListener.afterPhase(65) -
Total response time : 5936 milliseconds
11:14:24,260 INFO [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter
(204)
- No context init parameter 'org.apache.myfaces.PRETTY_HTML' found,
using
default value true
11:14:24,260 INFO [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter
(204)
- No context init parameter 'org.apache.myfaces.ALLOW_JAVASCRIPT'
found,
using default value true
11:14:24,260 INFO [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter
(204)
- No context init parameter '
org.apache.myfaces.READONLY_AS_DISABLED_FOR_SE
LECTS' found, using default value true
11:14:24,260 INFO [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter
(204)
- No context init parameter 'org.apache.myfaces.DETECT_JAVASCRIPT'
found,
using default value false
11:14:24,260 INFO [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter
(204)
- No context init parameter 'org.apache.myfaces.AUTO_SCROLL' found,
using
default value false
11:14:24,260 INFO [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getStringInitParameter
(229)
- No context init parameter 'org.apache.myfaces.ADD_RESOURCE_CLASS'
found,
using default value
org.apache.myfaces.renderkit.html.util.DefaultAddResource
11:14:24,276 INFO [STDOUT] 2007-07-20 11:14:24,276 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getStringInitParameter
(229)
- No context init parameter 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH'
found, using default value /faces/myFacesExtensionResource
11:14:24,276 INFO [STDOUT] 2007-07-20 11:14:24,276 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter
(204)
- No context init parameter
'org.apache.myfaces.CHECK_EXTENSIONS_FILTER'
found, using default
[Trinidad] Web services data
Hi Guys, I'm interested in getting info how to get Trinidad retrieving and displaying data from web services. I would like to hook up Trinidad components with these external web services. Is there a public example I could see? I'd appreciate anything on this. Thanks. Best regards, Darren. P Please consider the environment before printing this email _ 1. The information contained in this E-mail, including any files transmitted with it, is confidential and may be legally privileged. This E-mail is intended only for the personal attention of the stated addressee(s). Any access to this E-mail, including any files transmitted with it, by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this E-mail or any files transmitted with it. Such unauthorised use may be unlawful. If you have received this E-mail in error, please inform the sender immediately and delete it and all copies from your system. You may not forward this E-mail without the permission of the sender. 2. The views expressed in this E-mail are those of the author, and do not necessarily represent the views of AMT-SYBEX. Internet communications are not secure and AMT-SYBEX cannot, therefore, accept legal responsibility for the contents of this message nor for any damage caused by viruses. AMT-SYBEX Limited is a UK company, registration number GB03036807 at address The Spirella Building, Bridge Road, Letchworth, SG6 4ET. AMT-SYBEX (NI) Limited is a UK company, registration number NI024104 at address Edgewater Office Park, Edgewater Rd, Belfast, BT3 9JQ. For more information on the AMT-SYBEX Group visit http://www.amt-sybex.com _
Re: [tobago] an unexpected block is executed with RI 1.2 (in JBoss 4.2.1 GA) // TODO: remove this if block if prooven this never happens anymore
Hello Bernd Again,
It's ok for me, it's a quality procedure and it must be done that way.
Thanks again,
Zied
2007/7/23, Bernd Bohmann [EMAIL PROTECTED]:
Hello Zied,
the nightly build should posted every night when no compile or test
failures occurs. Unfortunately the continuum version (1.1-alpha-1) has
some memory issues :-(
The nightly build from 22-Jul-2007 on
http://people.apache.org/builds/myfaces/nightly/ should contain the
sheet fix.
Regards
Bernd
Zied Hamdi wrote:
Thxs Bernd,
I think I'll try to install MF 1.2. I didn't compile code from maven
until
now, but as I go through, I realize it's more and more necessairy. Why
aren't the nightly builds posted every night?, does it depend on test
results?
Regards,
Zied
2007/7/22, Bernd Bohmann [EMAIL PROTECTED]:
Hello Zied,
the sheet issue should be fixed on trunk.
Please try the next nightly build.
Regards
Bernd
Zied Hamdi wrote:
Hi friends,
I have experienced a problem that seems to come back from rip :-).
Seen
that
JBoss 4.2 is now based on tomcat 6 and supports EJB3, I've decided to
jump
my app into it. The problem is that it doesn't rely on myfaces core
anymore,
today to support the JSF 1.2 spec, it uses the sun implementation and
says
it shouldn't expose any problem to use myFaces components with it:
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss5AndMyFaces
When I start my app, I have on the first page a visual bug with icons
that
appear before the sheet (see picture) : this doesn't happen when I
use
myFaces core. Then on my first click I have the following exception
stack
trace. Looking at the source I found that the code shouldn't enter
this
section:
// *TODO*: remove this if block if prooven this never happens
anymore
*if* (command == *null*
currentActionId != *null*
currentActionId.matches(.*:\\d+:.*))
{
// If currentActionId component was inside a sheet the id
contains
the
// rowindex and is therefore not found here.
// We do not need the row here because we want just to find the
// related form, so removing the rowindex will help here.
currentActionId = currentActionId.replaceAll(:\\d+:, :);
*try* {
command = findComponent(currentActionId);
*LOG*.*info*(command = \ + command + \, *new*
Exception());
} *catch* (Exception e) {
// ignore
}
11:14:24,229 INFO [STDOUT] 2007-07-20 11:14:24,229 [
http-127.0.0.1-8080-2]
ERROR
org.apache.myfaces.tobago.context.ResourceManagerImpl.getRenderer
(348)
- Don't find any RendererClass for
org.apache.myfaces.ScheduleRenderer.
Please check you configuration.
11:14:24,244 INFO [STDOUT] 2007-07-20 11:14:24,244 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.tobago.util.DebugPhaseListener.afterPhase(65) -
Total response time : 5936 milliseconds
11:14:24,260 INFO [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter
(204)
- No context init parameter 'org.apache.myfaces.PRETTY_HTML' found,
using
default value true
11:14:24,260 INFO [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter
(204)
- No context init parameter 'org.apache.myfaces.ALLOW_JAVASCRIPT'
found,
using default value true
11:14:24,260 INFO [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter
(204)
- No context init parameter '
org.apache.myfaces.READONLY_AS_DISABLED_FOR_SE
LECTS' found, using default value true
11:14:24,260 INFO [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter
(204)
- No context init parameter 'org.apache.myfaces.DETECT_JAVASCRIPT'
found,
using default value false
11:14:24,260 INFO [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getBooleanInitParameter
(204)
- No context init parameter 'org.apache.myfaces.AUTO_SCROLL' found,
using
default value false
11:14:24,260 INFO [STDOUT] 2007-07-20 11:14:24,260 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getStringInitParameter
(229)
- No context init parameter 'org.apache.myfaces.ADD_RESOURCE_CLASS'
found,
using default value
org.apache.myfaces.renderkit.html.util.DefaultAddResource
11:14:24,276 INFO [STDOUT] 2007-07-20 11:14:24,276 [
http-127.0.0.1-8080-2]
INFO
org.apache.myfaces.shared_tomahawk.config.MyfacesConfig.getStringInitParameter
(229)
- No context init parameter 'org.apache.myfaces.RESOURCE_VIRTUAL_PATH
'
found, using default value
RE: Validating Multiple Components in DataTable
David,
Thank you for the suggestion. I have taken a look at the validateEqual
example and produced a AllOrNone item that works in a similar way. The main
differences being that it is attached to any field that is not part of the
validation, appearing after the fields being checked in the row and the
uiComponent.getParent().findComponent(id)
code has been changed to
UIComponent parent = uiComponent.getParent();
while(!(parent instanceof NamingContainer)) {
parent = parent.getParent();
}
parent.findComponent(id);
This is due to the fact that the tr:inputText is inside a tr:column which is
inside tr:table. The easiest thing to do was to navigate to the
NamingContainer, before using findComponent(). Final page looks something like
this:
tr:table
id=tblx
value=#{bean.collection}
binding=#{bean.coreTable}
var=entry
tr:column
tr:inputText value=#{entry.prop1} id=prop1/
/tr:column
tr:column
tr:inputText value=#{entry.prop2} id=prop2 /
/tr:column
...
tr:column
tr:selectBooleanCheckbox id=propx ...
my:allOrNoneValidator componentIds=prop1,prop2,prop3 /
/tr...
This results in a message being displayed in the column for propx for every row
that fails the validation.
I did implement a NotNullIfOtherNotNull, but found that if the field it is
attached to has a null value, then the validation never gets triggered.
As additional feedback, I have also implemented the validator in the backing
bean to provide the message at the table level should any row fail validation.
I will get feedback on which version the users want and retain it. Code
appears below.
/**
* Iterate through component tree and confirm that input values for selected
* items are not null.
*/
private void getStatusBits(UIComponent uiComponentIn) {
Iterator UIComponent iterator =
uiComponentIn.getChildren().iterator();
while (iterator.hasNext()) {
UIComponent uiComponent = iterator.next();
String family = uiComponent.getFamily();
if (!(uiComponent instanceof CoreInputHidden)
(CoreInputText.COMPONENT_FAMILY.equals(family) ||
CoreSelectOneChoice.COMPONENT_FAMILY.equals(family))) {
statusBits = 1;
if (((EditableValueHolder) uiComponent).getLocalValue() != null
((EditableValueHolder) uiComponent).isValid()
!((EditableValueHolder)
uiComponent).getLocalValue().toString().isEmpty()) {
statusBits ^= 1;
}
return;
}
getStatusBits(uiComponent);
}
return;
}
/**
* Validate contents for the table component provided using the expected
* bitmap indicating which fields are to be provided.
*/
private void validateTableComponent(CoreTable table,
final int requiredFieldMap) throws ValidatorException {
UIXCollection uixCollection = (UIXCollection) table;
int oldRowIndex = uixCollection.getRowIndex();
for (int rowNum = 0, numRows = uixCollection.getRowCount(); rowNum
numRows; rowNum++) {
uixCollection.setRowIndex(rowNum);
statusBits = 0;
getStatusBits(uixCollection);
if ((statusBits 0) ((statusBits ^ requiredFieldMap) 0)) {
FacesMessage message = Messages.getMessage(
Constants.LOCALIZATION_RESOURCE,
eduIncompleteRecord, null);
message.setSeverity(FacesMessage.SEVERITY_ERROR);
uixCollection.setRowIndex(oldRowIndex);
throw new ValidatorException(message);
}
}
uixCollection.setRowIndex(oldRowIndex);
}
/**
* Verify that entries contain all required data, if present.
*/
public void validateEntriesComplete(FacesContext facesContext,
UIComponent uIComponent,
Object object) throws ValidatorException {
if (object == null) {
return;
}
validateTableComponent(table, 0x000F); //Alter 0X000F based on
the number of fields that
//must have values.
}
private int _statusBits;
tr:message
id=msg
for=validate /
tr:table...
/tr:table
tr:inputHidden
id=validate
value=valid?
validator=#{bean.validateEntriesComplete} /
A bit messy, but does the trick for my scenario and the coding should improve
as I learn more :-)
Thanks again.
Re: Myfaces 1.2.0 setup issues (again)
Ok I did some testing on friday, as it seems there really are issues the main problem is, I could not nail them down entirely, we speak of different problems here a) The simple examples caused problems with the added web.xml injected bean in jetty (jetty does not seem to have implemented that stuff correctly) once removed it ran. This is an issue or testcase introduced by the geronimo guys, and not a problem of myfaces but a problem of jetty. Once the injection code was removed everything was running fine on Tomcat and Jetty. b) We have dependencies into commons-el from Tomahawk which were introduced by the shared project. (I could not really remove it since I didnt know exactly what the affected code was doing, any el experts here who can remove the code properly?) We need to remove that, there is a huge el clash if you introduce that one on jsp level (the bug already is covered in the bug db) And there are some jasper related issues, which might be caused by the commons-el, I am not sure, but jasper chokes big time on the tomahawk examples, which is a good indicator towards some el clashes or pending jasper issues, I assume it is the second since Matthias, since Trinidad runs fine, which also uses jasper and JSP. Funny thing is, while we cannot do anything about a) except for not using annotation based injection on jetty (which nobody uses for now anyway) for b) I really must say, if you use Tomahawk, for now, use facelets the problems are all on jsp/el level, which facelets provides its own stack, hence no problems should be there if used (and it seems to work fine). The problems will be resolved soon, so have patience for now. This seems to collide with the findings on the net, all projects which where/are facelets based seem to work fine all jsp projects moved up seem to run into issues. (Hence Matt ran into almost no issues at all, same for me, I moved an old facelets based project up in no time) Also use the latest Trunk of MyFaces 1.2, Matthias currently is fixing some bugs in there. Werner Martin Marinschek schrieb: Hear, hear! regards, Martin On 7/21/07, *Bruno Aranda* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, A lot of testing was done after deciding that MyFaces 1.2 could be released. A part from this, the TCK is passed both in tomcat and in jetty. Tomahawk simple examples can be tested with tomahawk 1.2 right away: - Checkout the tomahawk sources and go to the tomahawk/examples/simple folder - Run the examples with mvn -PjettyConfig -Djsf=12 jetty:run Then, you will have jetty running the tomahawk simple examples with MyFaces 1.2. Of course, not everything is covered by the tests and examples we have and it is normal that some bugs appear in the first version when tested with the different environments, and I don't just mean MyFaces bugs, as it can be other bugs with jetty or tomcat that have never been using a different JSF implementation than the RI. We are working on fixing all the issues we see in MyFaces, and here the help of the community is welcome to test everything in the different setups and environments. It is the community that make MyFaces such a powerful implementation and not only this, having a powerful 1.1 implementation of JSF even the JSF RI was forced to improve (and it really has improved). This is where having two main players implementing the JSF Spec is beneficial for everybody. We work hard in both sides to ensure compatibility while we try to make the most performant and stable implementation. Here, in MyFaces, we are of the opinion of releasing sooner rather than later, and as often as we can. This is why we will release a new MyFaces version as soon as we fix some of the bugs in the first 1.2 release, and so on. Here, everybody can help testing it in the different environment and filling JIRA issues, and even giving opinions and submitting patches! MyFaces is built for everybody by everybody, or at least this is the idea. And all ideas and suggestions are welcome. We, the core developers of MyFaces, work on it because we love it :-) Even when the poor user that tries to use our bits complains (oh! how do we enjoy seeing users suffering when trying to use something we have been weeks developing and spending many sleepless nights while trying to find the equilibrium between job, family and our passion), the complaints of the user are taken and given a shape, so the next version out improves. So, in conclusion (and someone should take the keyboard from me!) thanks for trying this first version of MyFaces 1.2, finding the bugs of MyFaces, tomcat and jetty, adding your experiences in the wiki and filling JIRA issues. On the compatibility side, tomahawk is going to be branched soon to be adapted to JSF
[Trinidad] when it decides to render xhtml and when to render html 4.01?
hi, sometimes the tr:document decides to render xhtml and sometimes html4.01. how to control it?
Re: Myfaces 1.2.0 setup issues (again)
Funny thing is, while we cannot do anything about a) except for not using annotation based injection on jetty (which nobody uses for now anyway) can you open an issue, with you details? http://jira.codehaus.org/browse/JETTY Thx, Matthias for b) I really must say, if you use Tomahawk, for now, use facelets the problems are all on jsp/el level, which facelets provides its own stack, hence no problems should be there if used (and it seems to work fine). The problems will be resolved soon, so have patience for now. This seems to collide with the findings on the net, all projects which where/are facelets based seem to work fine all jsp projects moved up seem to run into issues. (Hence Matt ran into almost no issues at all, same for me, I moved an old facelets based project up in no time) Also use the latest Trunk of MyFaces 1.2, Matthias currently is fixing some bugs in there. Werner Martin Marinschek schrieb: Hear, hear! regards, Martin On 7/21/07, *Bruno Aranda* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi, A lot of testing was done after deciding that MyFaces 1.2 could be released. A part from this, the TCK is passed both in tomcat and in jetty. Tomahawk simple examples can be tested with tomahawk 1.2 right away: - Checkout the tomahawk sources and go to the tomahawk/examples/simple folder - Run the examples with mvn -PjettyConfig -Djsf=12 jetty:run Then, you will have jetty running the tomahawk simple examples with MyFaces 1.2. Of course, not everything is covered by the tests and examples we have and it is normal that some bugs appear in the first version when tested with the different environments, and I don't just mean MyFaces bugs, as it can be other bugs with jetty or tomcat that have never been using a different JSF implementation than the RI. We are working on fixing all the issues we see in MyFaces, and here the help of the community is welcome to test everything in the different setups and environments. It is the community that make MyFaces such a powerful implementation and not only this, having a powerful 1.1 implementation of JSF even the JSF RI was forced to improve (and it really has improved). This is where having two main players implementing the JSF Spec is beneficial for everybody. We work hard in both sides to ensure compatibility while we try to make the most performant and stable implementation. Here, in MyFaces, we are of the opinion of releasing sooner rather than later, and as often as we can. This is why we will release a new MyFaces version as soon as we fix some of the bugs in the first 1.2 release, and so on. Here, everybody can help testing it in the different environment and filling JIRA issues, and even giving opinions and submitting patches! MyFaces is built for everybody by everybody, or at least this is the idea. And all ideas and suggestions are welcome. We, the core developers of MyFaces, work on it because we love it :-) Even when the poor user that tries to use our bits complains (oh! how do we enjoy seeing users suffering when trying to use something we have been weeks developing and spending many sleepless nights while trying to find the equilibrium between job, family and our passion), the complaints of the user are taken and given a shape, so the next version out improves. So, in conclusion (and someone should take the keyboard from me!) thanks for trying this first version of MyFaces 1.2, finding the bugs of MyFaces, tomcat and jetty, adding your experiences in the wiki and filling JIRA issues. On the compatibility side, tomahawk is going to be branched soon to be adapted to JSF 1.2 while including a completely performance overhaul (by using the trinidad state management capabilities). But, the current tomahawk should work for any JSF 1.2 implementation, so, if some component doesn't, that is considered a bug. Cheers, Bruno :-) On 21/07/07, Martin Marinschek [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: I am of the opinion that Bruno tested the full set of MyFaces examples before he said we're good for a release. So I'd also want to hear what Bruno has to say about this. regards, Martin On 7/20/07, Werner Punz [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Wolf Benz schrieb: I am currently trying to nail down the bugs I am still not sure about everything, but as it seems there is lots of weird stuff going on -- I'm glad you've found that out as well. Quite frustrating if you get the impression stuff only jamms on your PC. in the various app servers (most of them unified el
Re: Myfaces 1.2.0 setup issues (again)
Matthias Wessendorf schrieb: Funny thing is, while we cannot do anything about a) except for not using annotation based injection on jetty (which nobody uses for now anyway) can you open an issue, with you details? http://jira.codehaus.org/browse/JETTY Certainly, this evening. I have to get the full error (my test setup is at home) Werner
Re: [tobago] integrating Tomahawk Shedule componenent in Tobago
Hi Bernd and Volker,
with the latest shnapshot you should be able to use tomahawk tags inside
tobago
I'm using the last version of tomahawk 1.7 snapshot (23/07) and the tobago
night build (22 jul). When testing I have a schedule that displays (in the
day format) but with no data in it (even though I've inserted it in the
model), there's no reaction on clicks. I think it's all due to the same js
exception that occurs when I hover the page (Hundreds of times):
Erreur : Hash is not a constructor
Fichier source :
http://localhost:8080/IntoServicesTobagoWeb/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11851865/schedule.HtmlSchedule/javascript/domLib.js
Ligne : 514
Maybe I shouldn't post this error here, but I think it's a Tobago luck of
compatibility:
Bernd told me just before your last mail:
just moved the tomahawk example in the sandbox to the example test
project. Some of the js libs of the shedule component clashed with the
prototype js lib of tobago. Maybe you can create a modified tomahawk
version of the shedule js libs in a different namespace.
Is it actually fixed?
2007/7/17, Matthias Wessendorf [EMAIL PROTECTED]:
No, I am not using it at all,
but I was wondering if there are demos online.
Which might be easier for users, that's all...
-M
On 7/17/07, Zied Hamdi [EMAIL PROTECTED] wrote:
Hi Matthias,
I've made a svn checkout if you want to try it today you must download
the
latest version, or wait tomorrow for the snapshot I think.
Anyway the integration is very clean: completely transparent: all you
have
to do is something like this:
%@ taglib uri=http://myfaces.apache.org/tomahawk
prefix=t%
...
t:schedule value=#{tomahawk.schedule} /
...
where schedule is a ScheduleModel. I still don't have enough info to do
it
all, if you experience problems let me know, maybe I could help.
Regards,
(I'm going to try it out ;-))
2007/7/17, Matthias Wessendorf [EMAIL PROTECTED]:
Cool to hear,
are the sandbox demos somewhere online access able ?
-M
On 7/17/07, Volker Weber [EMAIL PROTECTED] wrote:
Hi Zied,
with the latest shnapshot you should be able to use tomahawk tags
inside
tobago.
There is an example with the tomahawk Shedule in the sandbox
examples:
example/sandbox/src/main/webapp/tomahawk.jsp
Regards,
Volker
2007/7/17, Zied Hamdi [EMAIL PROTECTED]:
Hi Again,
I've downloaded the last night build (1.0.12 SNAPSHOT), there's a
lot
of
interesting stuff like radio and checkbox menus, extended text
area,
unfortunately there's nothing dealing with the Shedule yet (I took
a
look at
the tld).
Can someone of the team please tell me if it's planned to be
adapted
in the
near future? I'd like to do and submit it, but I'm not exerienced
with
JSF
and it would take me a lot of time and frustrations (especially
that
I'm
already late for my project :-)...
Regards,
Zied
2007/7/17, Zied Hamdi [EMAIL PROTECTED]:
Thanks for the hint Matthias (and the rapid answer),
I'll take a look there and give a feedback to the mailing list
if
I've
found a solution.
Regards,
Zied
2007/7/17, Matthias Wessendorf [EMAIL PROTECTED]:
I know there is a tobago sandbox, which aims to support some
tomahawk
stuff,
perhaps it's worth to take a look ?
-Matthias
On 7/17/07, Zied Hamdi [EMAIL PROTECTED] wrote:
Hi there,
I have a strong need of a shedule, and I saw
http://myfaces.apache.org/tomahawk/schedule.html that
is
really excellent. I've chosen Tobago because of the time I
can
gain on
design (not developping css files, and have nice skins that
fulfill my
needs), I saw it's not possible to have compatibility
between
tobago
and
other myFaces libs, because of the unique View id imposed by
the
specs. So
the only solution to have the tomahawk schedule in my tobago
app
seems
to be
to port the classes to Tobago. I'm new to JSF so I'd ask: is
it
a big
time
consuming task to do that? or maybe should I ask before
that:
does
Tobgao
plan to have its shedule in the next two months?
If anyone has the answer, please tell me, my project must be
finished
in two
months, so I'm beginning to be scared ;-+;
Regards,
Zied
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
--
Zied Hamdi
zatreex.sourceforge.net
--
Zied Hamdi
zatreex.sourceforge.net
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
--
Zied Hamdi
zatreex.sourceforge.net
Firefox- Menu still shows after selecting an option
Hi, When I click the menu to go into a form, the menu is still showing. Only happens when I run Firefox, ie is OK in this respect. Any ideas please?? Rgds,Mike -- View this message in context: http://www.nabble.com/Firefox--Menu-still-shows-after-selecting-an-option-tf4128977.html#a11741670 Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: [tree2] expand folder by clickling on folder name
I don't use JS approach, so can't help you. You should look look in
.js scripts how +/- work.
On 20/07/07, Tomzi [EMAIL PROTECTED] wrote:
Tank you very much! But I'm looking for a javascript approch, since my tree
is fairly big (300 nodes) And I don't want to have the whole tree rebuild.
Is there a way to do this using javascript, without having to contact the
server. Since +/- seems not to contact the server, but open it using
javascript.
Michał 'Gandalf' Stawicki wrote:
f:facet name=objectProperties
t:commandLink
styleClass=properties
actionListener=#{t.setNodeSelected}
t:outputText
value=#{node.description}
style=#{t.nodeSelected ?
'font-weight: bold; color: #FF3366' :
''} /
t:updateActionListener
property=#{reservationsManager.selectedNode}
value=#{node}/
f:param name=docNum
value=#{node.identifier}/
/t:commandLink
/t:panelGrid
/f:facet
In the setSelectedNode(TreeNode node) method, for ex.:
String id = treeBinding.getNodeId();
String [] path =
treeBinding.getPathInformation(id);
treeBinding.expandPath(path);
On 19/07/07, Tomzi [EMAIL PROTECTED] wrote:
I'd like to have to open a folder not only by clicking on +/- but also
when I
click on the folders name - Is there a way to accomplish that with tree2?
--
View this message in context:
http://www.nabble.com/-tree2--expand-folder-by-clickling-on-folder-name-tf4110244.html#a11687822
Sent from the MyFaces - Users mailing list archive at Nabble.com.
--
Michał Stawicki
[EMAIL PROTECTED]
http://stawicki.jasliska.pl
--
View this message in context:
http://www.nabble.com/-tree2--expand-folder-by-clickling-on-folder-name-tf4110244.html#a11703840
Sent from the MyFaces - Users mailing list archive at Nabble.com.
--
Michał Stawicki
[EMAIL PROTECTED]
http://stawicki.jasliska.pl
Re: [tobago] integrating Tomahawk Shedule componenent in Tobago
Arratum:
The event shows correctly but is not clickable (I don't know in which
circonstances it doesn't show, I can't reproduce it). Anyway the js error is
present and happens even if I hover other panels than the one the schedule
is in.
Regards,
Zied
2007/7/23, Zied Hamdi [EMAIL PROTECTED]:
Hi Bernd and Volker,
with the latest shnapshot you should be able to use tomahawk tags inside
tobago
I'm using the last version of tomahawk 1.7 snapshot (23/07) and the tobago
night build (22 jul). When testing I have a schedule that displays (in the
day format) but with no data in it (even though I've inserted it in the
model), there's no reaction on clicks. I think it's all due to the same js
exception that occurs when I hover the page (Hundreds of times):
Erreur : Hash is not a constructor
Fichier source :
http://localhost:8080/IntoServicesTobagoWeb/faces/myFacesExtensionResource/org.apache.myfaces.renderkit.html.util.MyFacesResourceLoader/11851865/schedule.HtmlSchedule/javascript/domLib.js
Ligne : 514
Maybe I shouldn't post this error here, but I think it's a Tobago luck of
compatibility:
Bernd told me just before your last mail:
just moved the tomahawk example in the sandbox to the example test
project. Some of the js libs of the shedule component clashed with the
prototype js lib of tobago. Maybe you can create a modified tomahawk
version of the shedule js libs in a different namespace.
Is it actually fixed?
2007/7/17, Matthias Wessendorf [EMAIL PROTECTED]:
No, I am not using it at all,
but I was wondering if there are demos online.
Which might be easier for users, that's all...
-M
On 7/17/07, Zied Hamdi [EMAIL PROTECTED] wrote:
Hi Matthias,
I've made a svn checkout if you want to try it today you must download
the
latest version, or wait tomorrow for the snapshot I think.
Anyway the integration is very clean: completely transparent: all you
have
to do is something like this:
%@ taglib uri=http://myfaces.apache.org/tomahawk
prefix=t%
...
t:schedule value=#{ tomahawk.schedule} /
...
where schedule is a ScheduleModel. I still don't have enough info to
do it
all, if you experience problems let me know, maybe I could help.
Regards,
(I'm going to try it out ;-))
2007/7/17, Matthias Wessendorf [EMAIL PROTECTED]:
Cool to hear,
are the sandbox demos somewhere online access able ?
-M
On 7/17/07, Volker Weber [EMAIL PROTECTED] wrote:
Hi Zied,
with the latest shnapshot you should be able to use tomahawk tags
inside
tobago.
There is an example with the tomahawk Shedule in the sandbox
examples:
example/sandbox/src/main/webapp/tomahawk.jsp
Regards,
Volker
2007/7/17, Zied Hamdi [EMAIL PROTECTED]:
Hi Again,
I've downloaded the last night build (1.0.12 SNAPSHOT), there's
a lot
of
interesting stuff like radio and checkbox menus, extended text
area,
unfortunately there's nothing dealing with the Shedule yet (I
took a
look at
the tld).
Can someone of the team please tell me if it's planned to be
adapted
in the
near future? I'd like to do and submit it, but I'm not
exerienced with
JSF
and it would take me a lot of time and frustrations (especially
that
I'm
already late for my project :-)...
Regards,
Zied
2007/7/17, Zied Hamdi [EMAIL PROTECTED]:
Thanks for the hint Matthias (and the rapid answer),
I'll take a look there and give a feedback to the mailing list
if
I've
found a solution.
Regards,
Zied
2007/7/17, Matthias Wessendorf [EMAIL PROTECTED]:
I know there is a tobago sandbox, which aims to support some
tomahawk
stuff,
perhaps it's worth to take a look ?
-Matthias
On 7/17/07, Zied Hamdi [EMAIL PROTECTED] wrote:
Hi there,
I have a strong need of a shedule, and I saw
http://myfaces.apache.org/tomahawk/schedule.html that
is
really excellent. I've chosen Tobago because of the time I
can
gain on
design (not developping css files, and have nice skins
that
fulfill my
needs), I saw it's not possible to have compatibility
between
tobago
and
other myFaces libs, because of the unique View id imposed
by the
specs. So
the only solution to have the tomahawk schedule in my
tobago app
seems
to be
to port the classes to Tobago. I'm new to JSF so I'd ask:
is it
a big
time
consuming task to do that? or maybe should I ask before
that:
does
Tobgao
plan to have its shedule in the next two months?
If anyone has the answer, please tell me, my project must
be
finished
in two
months, so I'm beginning to be scared ;-+;
Regards,
Zied
--
Re: Myfaces 1.2.0 setup issues (again)
I suspect we could just reimplement the coercion stuff we are getting from commons-el? regards, Martin On 7/23/07, Werner Punz [EMAIL PROTECTED] wrote: Matthias Wessendorf schrieb: Funny thing is, while we cannot do anything about a) except for not using annotation based injection on jetty (which nobody uses for now anyway) can you open an issue, with you details? http://jira.codehaus.org/browse/JETTY Certainly, this evening. I have to get the full error (my test setup is at home) Werner -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Myfaces 1.2.0 setup issues (again)
Yes, btw. Bruno just told me there already is a myfaces 1.2 related switch in the maven build to kickstart the tomahawk examples with myfaces 1.2 and tomcat I am giving it a try as we speak mvn clean package cargo:start -Djsf=12 Werner Martin Marinschek schrieb: I suspect we could just reimplement the coercion stuff we are getting from commons-el? regards, Martin On 7/23/07, *Werner Punz* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Matthias Wessendorf schrieb: Funny thing is, while we cannot do anything about a) except for not using annotation based injection on jetty (which nobody uses for now anyway) can you open an issue, with you details? http://jira.codehaus.org/browse/JETTY Certainly, this evening. I have to get the full error (my test setup is at home) Werner -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Myfaces 1.2.0 setup issues (again)
Werner Punz schrieb: Yes, btw. Bruno just told me there already is a myfaces 1.2 related switch in the maven build to kickstart the tomahawk examples with myfaces 1.2 and tomcat I am giving it a try as we speak mvn clean package cargo:start -Djsf=12 Ok thanks to Brunos advice I got a working configuration, I will post a link once I am at home (which is at 9pm gmt+1) The problems were indeed caused by some dependencies into old stuff or a missing jar. Following configuration works for Tomahawk: Checkout the tomcahak examples and do a build via -Djsf=12 then you will get a working war. There seems to be some dependencies into following libs which seem to be weird: a) jstl1.1.0 and 1-2 at the same time b commons-el 1.0 (which is a total clash with the jee5 el) for a) you can remove the jstl1.1 in this case it is not needed there is a slight build bug, anyway if you do a clean package you will get a working war which should be enough to kickstart with tomcat. :-) I will post a working war in a few hours to get you guys up and running. (Once I am at home), and I also will add a wiki article for better documentation. Cheers Werner
Re: Myfaces 1.2.0 setup issues (again)
I have to say, all this is on the latest trunk of myfaces, I dont know if it works with the release, since Matthias was eliminating some bugs the last few days. Werner Werner Punz schrieb: Werner Punz schrieb: Yes, btw. Bruno just told me there already is a myfaces 1.2 related switch in the maven build to kickstart the tomahawk examples with myfaces 1.2 and tomcat I am giving it a try as we speak mvn clean package cargo:start -Djsf=12 Ok thanks to Brunos advice I got a working configuration, I will post a link once I am at home (which is at 9pm gmt+1) The problems were indeed caused by some dependencies into old stuff or a missing jar. Following configuration works for Tomahawk: Checkout the tomcahak examples and do a build via -Djsf=12 then you will get a working war. There seems to be some dependencies into following libs which seem to be weird: a) jstl1.1.0 and 1-2 at the same time b commons-el 1.0 (which is a total clash with the jee5 el) for a) you can remove the jstl1.1 in this case it is not needed there is a slight build bug, anyway if you do a clean package you will get a working war which should be enough to kickstart with tomcat. :-) I will post a working war in a few hours to get you guys up and running. (Once I am at home), and I also will add a wiki article for better documentation. Cheers Werner
Re: Myfaces 1.2.0 setup issues (again)
release often, release early ... :-) On 7/23/07, Werner Punz [EMAIL PROTECTED] wrote: I have to say, all this is on the latest trunk of myfaces, I dont know if it works with the release, since Matthias was eliminating some bugs the last few days. Werner Werner Punz schrieb: Werner Punz schrieb: Yes, btw. Bruno just told me there already is a myfaces 1.2 related switch in the maven build to kickstart the tomahawk examples with myfaces 1.2 and tomcat I am giving it a try as we speak mvn clean package cargo:start -Djsf=12 Ok thanks to Brunos advice I got a working configuration, I will post a link once I am at home (which is at 9pm gmt+1) The problems were indeed caused by some dependencies into old stuff or a missing jar. Following configuration works for Tomahawk: Checkout the tomcahak examples and do a build via -Djsf=12 then you will get a working war. There seems to be some dependencies into following libs which seem to be weird: a) jstl1.1.0 and 1-2 at the same time b commons-el 1.0 (which is a total clash with the jee5 el) for a) you can remove the jstl1.1 in this case it is not needed there is a slight build bug, anyway if you do a clean package you will get a working war which should be enough to kickstart with tomcat. :-) I will post a working war in a few hours to get you guys up and running. (Once I am at home), and I also will add a wiki article for better documentation. Cheers Werner -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org
t:panelTabbedPane - display tabs in multiple rows
Hi, I'm using a t:panelTabbedPane, how can I display the tabs in multiple rows? Best regards, Mike Burton
Re: [Trinidad] when it decides to render xhtml and when to render html 4.01?
As best I know, we never render XHTML, so I'm surprised to hear otherwise. -- Adam On 7/23/07, Burghard Britzke [EMAIL PROTECTED] wrote: hi, sometimes the tr:document decides to render xhtml and sometimes html4.01. how to control it?
Re: [Trinidad] when it decides to render xhtml and when to render html 4.01?
Funny, I should have remembered: https://issues.apache.org/jira/browse/TRINIDAD-78 ... since I fixed it myself... Looks like it's this simple: set the contentType of your JSP page to be XHTML, get XHTML output. And, if you fail to set a content type, then by default you get HTML for .jsp pages, XHTML for .jspx documents. -- Adam On 7/23/07, Adam Winer [EMAIL PROTECTED] wrote: As best I know, we never render XHTML, so I'm surprised to hear otherwise. -- Adam On 7/23/07, Burghard Britzke [EMAIL PROTECTED] wrote: hi, sometimes the tr:document decides to render xhtml and sometimes html4.01. how to control it?
Re: [Trinidad] when it decides to render xhtml and when to render html 4.01?
and for facelets? is it possible to set the content type, too? for facelets .xhtml files it rendered html 4.01. Am 23.07.2007 um 19:58 schrieb Adam Winer: Funny, I should have remembered: https://issues.apache.org/jira/browse/TRINIDAD-78 ... since I fixed it myself... Looks like it's this simple: set the contentType of your JSP page to be XHTML, get XHTML output. And, if you fail to set a content type, then by default you get HTML for .jsp pages, XHTML for .jspx documents. -- Adam On 7/23/07, Adam Winer [EMAIL PROTECTED] wrote: As best I know, we never render XHTML, so I'm surprised to hear otherwise. -- Adam On 7/23/07, Burghard Britzke [EMAIL PROTECTED] wrote: hi, sometimes the tr:document decides to render xhtml and sometimes html4.01. how to control it?
MyFaces 1.2 + Tomahawk Kickstart was: Re: Myfaces 1.2.0 setup issues (again)
Matthias Wessendorf schrieb: release often, release early ... :-) Ok guys I am dropping the tomahawk builds and the blank application as well as a working myfaces 1.2 sandbox war into http://people.apache.org/~werpu/ as we speak, first of all there is a slight build error, once extracted you safely can remove the jstl-1.1.jar from the WEB-INF/lib the wars should work out of the box on a tomcat 6 install with a jdk5+ most tomahawk components seem to work, the same goes for the sandbox, 3-4 fail on tomahawk, and the same on the sandbox for various reasons (most of them are slight programming errors, or misuse of the 1.1 spec to achieve a certain functionality) Note, all this wont work with jdk 1.4 or a non JEE5 compliant servlet runner since myfaces relies on the latest JSP and Servlet implementations (as defined by the spec) The blank application should get you kickstarted and the tomahawk build should give you an overview which components work. Have much fun with myfaces 1.2 As for a short explanation on how to get the build simply check out myfaces and do a mvn clean pack -Djsf=12 on the examples and it will configure everything for myfaces 1.2 a -Djsf=ri12 should make the packing for the ri according to Bruno. I will add a wiki page the next few days explaining everything so that people have an easier time to kickstart with myfaces 1.2. Werner
Re: facelets vs. jsp
Zied Hamdi schrieb: Why didn't Sun adopt Facelets as it adopted Derby??? Too late for jsf 1.2, something along facelets is on the table for jsf 2.0 I hope Jacob can push the guys at sun into the right direction the sooner JSP is abandoned the better, many problems in jsf are caused by jsp. Ideal would be something along facelets for high level templating no tag handlers whatsover, only one component class, and the renderer also written in preferrably the same templating language.
RE: panelTabbedPane - display tabs in multiple rows
writing your own renderer... at least when I looked at it last time that was necessary... Maybe some css.tweaking might also work, but the control what goes into the first and the second row needed the private renderer hth Alexander -Original Message- From: Mike Burton [mailto:[EMAIL PROTECTED] Sent: Monday, July 23, 2007 5:17 PM To: users@myfaces.apache.org Subject: t:panelTabbedPane - display tabs in multiple rows Hi, I'm using a t:panelTabbedPane, how can I display the tabs in multiple rows? Best regards, Mike Burton
Re: panelTabbedPane - display tabs in multiple rows
Thanks, looks like I'll be reverting to my fake tab-panel then, shame. Rgds, Mike. Jesse Alexander (KSFD 121) wrote: writing your own renderer... at least when I looked at it last time that was necessary... Maybe some css.tweaking might also work, but the control what goes into the first and the second row needed the private renderer hth Alexander -Original Message- From: Mike Burton [mailto:[EMAIL PROTECTED] Sent: Monday, July 23, 2007 5:17 PM To: users@myfaces.apache.org Subject: t:panelTabbedPane - display tabs in multiple rows Hi, I'm using a t:panelTabbedPane, how can I display the tabs in multiple rows? Best regards, Mike Burton
Re: [Trinidad] when it decides to render xhtml and when to render html 4.01?
In Facelets, setting contentType on f:view should do the trick, but I don't know for sure. -- Adam On 7/23/07, Burghard Britzke [EMAIL PROTECTED] wrote: and for facelets? is it possible to set the content type, too? for facelets .xhtml files it rendered html 4.01. Am 23.07.2007 um 19:58 schrieb Adam Winer: Funny, I should have remembered: https://issues.apache.org/jira/browse/TRINIDAD-78 ... since I fixed it myself... Looks like it's this simple: set the contentType of your JSP page to be XHTML, get XHTML output. And, if you fail to set a content type, then by default you get HTML for .jsp pages, XHTML for .jspx documents. -- Adam On 7/23/07, Adam Winer [EMAIL PROTECTED] wrote: As best I know, we never render XHTML, so I'm surprised to hear otherwise. -- Adam On 7/23/07, Burghard Britzke [EMAIL PROTECTED] wrote: hi, sometimes the tr:document decides to render xhtml and sometimes html4.01. how to control it?
Re: [Trinidad] when it decides to render xhtml and when to render html 4.01?
I can confirm that it does. f:view contentType=text/html seems to be a necessity if you want Dojo to work. On 7/23/07, Adam Winer [EMAIL PROTECTED] wrote: In Facelets, setting contentType on f:view should do the trick, but I don't know for sure. -- Adam On 7/23/07, Burghard Britzke [EMAIL PROTECTED] wrote: and for facelets? is it possible to set the content type, too? for facelets .xhtml files it rendered html 4.01. Am 23.07.2007 um 19:58 schrieb Adam Winer: Funny, I should have remembered: https://issues.apache.org/jira/browse/TRINIDAD-78 ... since I fixed it myself... Looks like it's this simple: set the contentType of your JSP page to be XHTML, get XHTML output. And, if you fail to set a content type, then by default you get HTML for .jsp pages, XHTML for .jspx documents. -- Adam On 7/23/07, Adam Winer [EMAIL PROTECTED] wrote: As best I know, we never render XHTML, so I'm surprised to hear otherwise. -- Adam On 7/23/07, Burghard Britzke [EMAIL PROTECTED] wrote: hi, sometimes the tr:document decides to render xhtml and sometimes html4.01. how to control it?
Re: MyFaces 1.2 + Tomahawk Kickstart was: Re: Myfaces 1.2.0 setup issues (again)
Very nice, thanks ! On 7/23/07, Werner Punz [EMAIL PROTECTED] wrote: Matthias Wessendorf schrieb: release often, release early ... :-) Ok guys I am dropping the tomahawk builds and the blank application as well as a working myfaces 1.2 sandbox war into http://people.apache.org/~werpu/ as we speak, first of all there is a slight build error, once extracted you safely can remove the jstl-1.1.jar from the WEB-INF/lib the wars should work out of the box on a tomcat 6 install with a jdk5+ most tomahawk components seem to work, the same goes for the sandbox, 3-4 fail on tomahawk, and the same on the sandbox for various reasons (most of them are slight programming errors, or misuse of the 1.1 spec to achieve a certain functionality) Note, all this wont work with jdk 1.4 or a non JEE5 compliant servlet runner since myfaces relies on the latest JSP and Servlet implementations (as defined by the spec) The blank application should get you kickstarted and the tomahawk build should give you an overview which components work. Have much fun with myfaces 1.2 As for a short explanation on how to get the build simply check out myfaces and do a mvn clean pack -Djsf=12 on the examples and it will configure everything for myfaces 1.2 a -Djsf=ri12 should make the packing for the ri according to Bruno. I will add a wiki page the next few days explaining everything so that people have an easier time to kickstart with myfaces 1.2. Werner -- Grant Smith
Re: how can I user t:checkbox of t:selectManyCheckbox to spread checkbox to my page what i wanted.
tomahowk t:selectManyCheckbox new style，add checkbok's spread layout style。
old layout=pageDirection,lineDerection,
tomahowk1.1.6 new layout=spread
and with bellow tag you can display anywhere in your pape.
t:checkbox index=0 for=chk/t:checkbox
[code]
t:selectManyCheckbox id=chk value=#{test.testArrayList}
layout=spread
f:selectItems value=#{test.testAvailableSelectItems}/
/t:selectManyCheckbox
[/code]
[code]
..anywhere in form
t:checkbox index=0 for=chk/t:checkbox
[/code]
song wrote:
how can I user t:checkbox of t:selectManyCheckbox to spread checkbox
to my page what i wanted.
eg.
I want selectManyCheckbox's checkbox show in table some rows,how can i do
it.
--
View this message in context:
http://www.nabble.com/how-can-I-user-%3Ct%3Acheckbox%3E-of-%3Ct%3AselectManyCheckbox%3E-to-spread-checkbox-to-my-page-what-i-wanted.-tf4127588.html#a11755351
Sent from the MyFaces - Users mailing list archive at Nabble.com.
Re: how can I user t:checkbox of t:selectManyCheckbox to spread checkbox to my page what i wanted.
now i find a bug ,wen I display the spread checkbox in t:datatable ,
it difficout to set the sequence number index in t:checkbox index=n .
and when render , the id and name render in datatable's way whitch not you
defined
in t:selectManyCheckbox.
i hope,i can use custom input type=checkbox in jsf,and use it no
chonstrain and freelly.
song wrote:
tomahowk t:selectManyCheckbox new style，add checkbok's spread layout
style。
old layout=pageDirection,lineDerection,
tomahowk1.1.6 new layout=spread
and with bellow tag you can display anywhere in your pape.
t:checkbox index=0 for=chk/t:checkbox
[code]
t:selectManyCheckbox id=chk value=#{test.testArrayList}
layout=spread
f:selectItems value=#{test.testAvailableSelectItems}/
/t:selectManyCheckbox
[/code]
[code]
..anywhere in form
t:checkbox index=0 for=chk/t:checkbox
[/code]
song wrote:
how can I user t:checkbox of t:selectManyCheckbox to spread checkbox
to my page what i wanted.
eg.
I want selectManyCheckbox's checkbox show in table some rows,how can i do
it.
--
View this message in context:
http://www.nabble.com/how-can-I-user-%3Ct%3Acheckbox%3E-of-%3Ct%3AselectManyCheckbox%3E-to-spread-checkbox-to-my-page-what-i-wanted.-tf4127588.html#a11755400
Sent from the MyFaces - Users mailing list archive at Nabble.com.
[OT] Spring2-JPA, tomcat-6, jdk-1.6, jsf-1.2, myfaces-1.2.0
Hi: Has anyone been able to make Spring2-JPA running on tomcat 6? I try to upgrade a jsf application on tomcat. It was compiled but stuck at Spring JPA configuration. Any suggestions? Environment: jdk-1.6U2, tomcat-6.0.13, jsf-1.2, myfaces-1.2.0, trimidad-1.2.1, facelets-1.1.11, Shale-1.0.4, Spring-2.0.5, toplink-2.41, Oracle-XE. More detailed is in the enclosed txt file. Thanks Hi: I try to upgrade a jsf application on tomcat. It was compiled but stuck at Spring configuration. Any suggestion? Environment: jdk-1.6U2, tomcat-6.0.13, jsf-1.2, myfaces-1.2.0, trinidad-1.2.1, facelets-1.1.11, Shale-1.0.4, Spring-2.0.5, topLink-2.41, Oracle-XE. 1) tomcat-6/lib/spring-tomcat-waever-2.0.5.jar, ojdbc14_g-1.4.jar, toplink-essentials-2.41.jar and the context.xml has: Context path= docBase=ROOT crossContext=true debug=0 reloadable=true Loader loaderClass=org.springframework.instrument.classloading.tomcat.TomcatInstrumentableClassLoader useSystemClassLoaderAsParent=false / /Context 2) ant-1.7.0 has used this persistence.xml to generate schema and populate data persistence version=1.0 xmlns=http://java.sun.com/xml/ns/persistence; persistence-unit name=BUDHNET transaction-type=RESOURCE_LOCAL classcom.dbgroups.core.data.Activity/class ... !-- required for toplink to work with Ant in database creation provideroracle.toplink.essentials.PersistenceProvider/provider properties property name=toplink.jdbc.driver value=oracle.jdbc.OracleDriver/ ... /properties -- /persistence-unit /persistence As reported by someone that Spring-JPA only looks at the class root for /META-INF/persistence.xml so we also have /WEB-INF/classes/META-INF/persistence.xml 3) Setting up Spring beans beans xmlns=http://www.springframework.org/schema/beans; ... default-init-method=init default-destroy-method=destroy bean id=userDao scope=singleton class=com.dbgroups.core.user.UserDao/ bean id=userService class=com.dbgroups.core.user.UserService property name=userDao ref=userDao/ /bean bean id=transactionManager scope=singleton class=org.springframework.orm.jpa.JpaTransactionManager property name=entityManagerFactory ref=entityManagerFactory/ /bean bean class=org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor/ bean class=org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor/ tx:annotation-driven / bean id=entityManagerFactory class=org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean property name=persistenceUnitName value=BUDHNET/ property name=dataSource ref=dataSource/ property name=loadTimeWeaver bean class=org.springframework.instrument.classloading.ReflectiveLoadTimeWeaver / /property property name=jpaVendorAdapter ref=vendorAdapter/ /bean bean id=dataSource class=org.apache.commons.dbcp.BasicDataSource property name=driverClassName value=oracle.jdbc.OracleDriver/ property name=url value=jdbc:oracle:thin:@collab.budhnet.com:1521:XE/ property name=username value=XX/ property name=password value=XXX/ /bean bean id=vendorAdapter class=org.springframework.orm.jpa.vendor.TopLinkJpaVendorAdapter property name=databasePlatform value=oracle.toplink.essentials.platform.database.oracle.OraclePlatform/ property name=showSql value=true/ property name=generateDdl value=false/ /bean /beans 4) web.xml has both spring ContextLoaderListener and RequestContextListener. Someone has tried this and make it work on windows with the addition of javaagent (that I do not yet understand): http://asrijaffar.blogspot.com/2007/02/spring-jpa-tomcat.html I am working on CentOS-4 and has the followings: INFO: Bean factory for application context [EMAIL PROTECTED]: [EMAIL PROTECTED] Jul 23, 2007 7:32:21 PM org.springframework.context.support.AbstractApplicationContext$BeanPostProcessorChecker postProcessAfterInitialization INFO: Bean 'dataSource' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) Jul 23, 2007 7:32:21 PM org.springframework.context.support.AbstractApplicationContext$BeanPostProcessorChecker postProcessAfterInitialization INFO: Bean 'org.springframework.instrument.classloading.ReflectiveLoadTimeWeaver#36d047' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) Jul 23, 2007 7:32:21 PM org.springframework.context.support.AbstractApplicationContext$BeanPostProcessorChecker postProcessAfterInitialization INFO: Bean 'vendorAdapter' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) Jul 23, 2007 7:32:21 PM org.springframework.beans.factory.support.DefaultSingletonBeanRegistry destroySingletons INFO: Destroying singletons in [EMAIL PROTECTED]: defining beans
Re: MyFaces 1.2 + Tomahawk Kickstart was: Re: Myfaces 1.2.0 setup issues (again)
So the outcome is that generally it works? What was the difference in the setup then? regards, Martin On 7/23/07, Grant Smith [EMAIL PROTECTED] wrote: Very nice, thanks ! On 7/23/07, Werner Punz [EMAIL PROTECTED] wrote: Matthias Wessendorf schrieb: release often, release early ... :-) Ok guys I am dropping the tomahawk builds and the blank application as well as a working myfaces 1.2 sandbox war into http://people.apache.org/~werpu/ http://people.apache.org/%7Ewerpu/ as we speak, first of all there is a slight build error, once extracted you safely can remove the jstl-1.1.jar from the WEB-INF/lib the wars should work out of the box on a tomcat 6 install with a jdk5+ most tomahawk components seem to work, the same goes for the sandbox, 3-4 fail on tomahawk, and the same on the sandbox for various reasons (most of them are slight programming errors, or misuse of the 1.1 spec to achieve a certain functionality) Note, all this wont work with jdk 1.4 or a non JEE5 compliant servlet runner since myfaces relies on the latest JSP and Servlet implementations (as defined by the spec) The blank application should get you kickstarted and the tomahawk build should give you an overview which components work. Have much fun with myfaces 1.2 As for a short explanation on how to get the build simply check out myfaces and do a mvn clean pack -Djsf=12 on the examples and it will configure everything for myfaces 1.2 a -Djsf=ri12 should make the packing for the ri according to Bruno. I will add a wiki page the next few days explaining everything so that people have an easier time to kickstart with myfaces 1.2. Werner -- Grant Smith -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: [OT] Spring2-JPA, tomcat-6, jdk-1.6, jsf-1.2, myfaces-1.2.0
I found the problem while searching spring forum. The stack-overflow error is caused by an old version of xerces. Use the following in maven will solve the problem: dependency groupIdxerces/groupId artifactIdxercesImpl/artifactId version2.8.1/version /dependency I will report other issues as i go along. BaTien On Mon, 2007-07-23 at 20:06 -0600, Duong BaTien wrote: Hi: Has anyone been able to make Spring2-JPA running on tomcat 6? I try to upgrade a jsf application on tomcat. It was compiled but stuck at Spring JPA configuration. Any suggestions? Environment: jdk-1.6U2, tomcat-6.0.13, jsf-1.2, myfaces-1.2.0, trimidad-1.2.1, facelets-1.1.11, Shale-1.0.4, Spring-2.0.5, toplink-2.41, Oracle-XE. More detailed is in the enclosed txt file. Thanks
Error-Handling
With permission of Jacob Hookom, I've enabled Exception Handling just like in Facelets now also for the rest of the JSF-Lifecycle - it will also work with plain JSP. I've also cleaned up the stack-traces, so that you actually see causing exceptions (if any Servlet-Exceptions are in the chain) - this will make for much less log-scrutinizing for everyone. If you need any further refinements, please tell us. regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
Re: Error-Handling
very nice! On 7/24/07, Martin Marinschek [EMAIL PROTECTED] wrote: With permission of Jacob Hookom, I've enabled Exception Handling just like in Facelets now also for the rest of the JSF-Lifecycle - it will also work with plain JSP. I've also cleaned up the stack-traces, so that you actually see causing exceptions (if any Servlet-Exceptions are in the chain) - this will make for much less log-scrutinizing for everyone. If you need any further refinements, please tell us. regards, Martin -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org
[Trinidad] Are you using Trinidad ?
Please add your company to this list http://wiki.apache.org/myfaces/Companies_using_Trinidad Thx! Matthias -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org
Are you using MyFaces ?
If your are using MyFaces (1.1.x || 1.2.x) and your company isn't listed here: http://wiki.apache.org/myfaces/Companies_Using_MyFaces Please add it! Thx, Matthias -- Matthias Wessendorf further stuff: blog: http://matthiaswessendorf.wordpress.com/ mail: matzew-at-apache-dot-org
