[japplicoon]

"bfo81" wrote:
Sorry, but if you use JSP this might be correct. But for Facelets you do defintely need an extra *.taglib.xml file plus an entry in the web.xml referencing that file.

Hi, bfo81!
Did you get your sandbox components running with facelets and seam? I have tomahawk up and running, but if I do the very same thing with the sandbox libraries (SNAPSHOT-1.1.5, just like tomahawk), facelets ignores any

<s:xxxx/>

tag, that is, prints it out as is. In the logs I see that the faces-config in the sandbox jar is read, but the libariy doesn't seem to be loaded ....
The sandbox-SNAPSHOT.jar is in place, the sandbox.taglib.xml too, it is referenced in web.xml, the namespace is mapped in the xhtml file.
Too keep the first test simple, I tried the

<s:inputSuggest/>

tag, without Ajax or thelike.

Any idea?
Which version of the sandbox do you use with which taglib.xml? Perhaps

Thank you : )

sonja

[japplicoon]

Sorry - Don't waste time - I got it ! The extra classes referenced in the taglib were missing ...

[japplicoon]

... but no Ajax :-( ...

When I try <s:inputSuggestAjax> I get the exception also described here:

http://jira.jboss.com/jira/browse/JBSEAM-342

Reading Gavin King's answer ... Is there no way to use the ajax-related Tags from the sandbox with Seam (and Facelets) ?
I put the "InputSuggestAjaxComponentHandler" inside a jar ending up in WEB-INF/lib of the war file, just besides the sandbox jar.

Who did get the inputSuggestAjax running with Seam?

Thanks in advance!

[gavin.king]

Seriosly guys, I would stay away from all the MyFaces taglibs apart from the new Trinidad stuff. The quality of these taglibs seems very low, they tie you directly to MyFaces, and they don't play nicely with other things like Seam.

The Trinidad stuff created by Oracle is great, however.

[japplicoon]

Gavin,
are there some seam-specific jsf-components available that use Seam Remoting? Something like special ajax-input components similar to the ones in the myfaces sandbox or in trinidad?

I don't know how "in trinidad" the ajax components work, but I guess it would be much simpler to use Remoting than to build Renderkits, Handlers and so on? Are there any efforts?

[gavin.king]

Personally i think the Avatar/Ajax4JSF/Dynafaces/etc approach of supporting partial-page update is a *much* more elegant path forward. Can't do *everything* you might want to use Ajax for, but it can do a lot.

Or, if you want to use Seam remoting, you don't need a JSF tag library, why not just use scriptaculous or dojo with Seam remoting?

[bfo81]

Well, there are many useful Tomahawk components that I do not want to miss anymore (e.g. t:inputFileUpload or t:column). But there are even many sloppy components or code parts.

E.g. the schedule component supports a lot of custom style classes (as per API) but the corresponding attributes are not implemented (and thus ignored)!!! The shuttle selectmanymenu is very nice, too, but there are no headlines (so which box represents the selected items and which one the non-selected ones?). And the best is the UploadedFile class: getName() used to return the filename, but in the newest release this method returns the filename PLUS the local path in front. You update your jars and BANG your app doesn't work anymore as expected. *imagine some insulting words targeted at the Tomahawk developers responsible for those cardinal errors here >:D*

The idea of components is a huge strength but also a weakness of the JSF technology. There are many good components you can easily apply in your app and that save you lot of time, but there's also very much rubbish out there that can drive you crazy.

[mikedanese]

I have been trying for 2 days to get tomahawk running under jb4.04, followed all these instructions and those on the *jboss-faces* setup page. Currently, I get an empty page w the tags not rendering any content. No exceptions but an abrupt msg in the logfile: 2006-10-18 11:01:50,013 [http-0.0.0.0-8080-5] INFO org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No context init parameter 'org.apache.myfaces.PRETTY_HTML' found, using default value true
2006-10-18 11:01:50,013 [http-0.0.0.0-8080-5] INFO org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No context init parameter 'org.apache.myfaces.ALLOW_JAVASCRIPT' found, using default value true
2006-10-18 11:01:50,013 [http-0.0.0.0-8080-5] INFO org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No context init parameter 'org.apache.myfaces.DETECT_JAVASCRIPT' found, using default value false
2006-10-18 11:01:50,013 [http-0.0.0.0-8080-5] INFO org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No context init parameter 'org.apache.myfaces.AUTO_SCROLL' found, using default value false2006-10-18 11:01:50,013 [http-0.0.0.0-8080-5] INFO org.apache.myfaces.shared_tomahawk.config.MyfacesConfig - No context init parameter 'org.apache.myfaces.ADD_RESOURCE_CLASS' found, using default value org.apache.myfaces.renderkit.html.util.DefaultAddResource
2006-10-18 11:06:13,356 [http-0.0.0.0-8080-3] DEBUG org.jboss.web.tomcat.tc5.jasper.TagLibCache - Scanning for tlds in: file:/C:/Javasoft/appservers/jboss4/server/default/deploy/jbossweb-tomcat55.sar/jsf-libs/myfaces-impl.jar
2006-10-18 11:06:13,481 [http-0.0.0.0-8080-3] DEBUG org.jboss.web.tomcat.tc5.jasper.TagLibCache - Scanning for tlds in: file:/C:/Javasoft/appservers/jboss4/server/default/deploy/jbossweb-tomcat55.sar/jsf-libs/tomahawk-1.1.3.jar

[jbossjbh]

Personally i think the Avatar/Ajax4JSF/Dynafaces/etc approach of supporting partial-page update is a *much* more elegant path forward. Can't do *everything* you might want to use Ajax for, but it can do a lot.

Or, if you want to use Seam remoting, you don't need a JSF tag library, why not just use scriptaculous or dojo with Seam remoting?

Gavin or others,

Any thoughts / experience using the jMaki project stuff with seams?

[japplicoon]

Or, if you want to use Seam remoting, you don't need a JSF tag library, why not just use scriptaculous or dojo with Seam remoting?

My current problem is getting an HTML Editor setting one of my entity properties.
I just throw away my <t:inputHtml> tags in favour of using the dojoInitializer (ok, once again a sandbox component ...) following the instructions in http://wiki.apache.org/myfaces/WYSIWYG_Editor.

The editor displays and the editing works fine, but the bean's value isn't updated and the action command is never executed (which works fine if I replace the dojo-ized textarea with an <h:inputText>). I also use Facelets (indeed, the textarea sits inside a facelets-tag xhtml), Trinidad and have the ajax4jsf Filter installed (but no ajax4jsf tags around on that particular page)

Do I have to dive into Dojo and set my entity bean property via Remoting?
Or is there another approach without Dojo (and without t:inputHtml)?

Thanks again!

[japplicoon]

@jbossjbh

Now I've also tried the jMaki approach. The very same results.

[shundavid]

The step by step instructions that "nhpvti" wrote are perfect! Thanks!