Sure,
it's possible.
there is a demo inside of Trinidad (you have to update the config)
There is also a sweet email lib @Jakarta:
http://commons.apache.org/email/
that makes it very easy to send emails.
-Matthias
On 8/16/07, ignicolist [EMAIL PROTECTED] wrote:
Its is possible send mails with
hi,
what are your feelings on starting the 1.2.2 release procedure by next
week, or the week after the next week ?
-Matthias
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail: matzew-at-apache-dot-org
Clean up build files
Key: ORCHESTRA-4
URL: https://issues.apache.org/jira/browse/ORCHESTRA-4
Project: MyFaces Orchestra
Issue Type: Improvement
Affects Versions: 1.0-SNAPSHOT
Environment: xp
Redirecting Error Handler
--
Key: MYFACES-1711
URL: https://issues.apache.org/jira/browse/MYFACES-1711
Project: MyFaces Core
Issue Type: New Feature
Components: General
Affects Versions: 1.2.1-SNAPSHOT
[
https://issues.apache.org/jira/browse/TOBAGO-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520513
]
Helmut Swaczinna commented on TOBAGO-416:
-
See Tobago-84
Sheet StateChangeListener doesn´t called on
[
https://issues.apache.org/jira/browse/TOBAGO-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520515
]
Helmut Swaczinna commented on TOBAGO-436:
-
See Tobago-84
tc:sheet rowClick facet
---
Hi Simon!
Thanks for all the hard work you put into documentation and cleanup of
the Orchestra API.
This really brings the project even further!
Have a nice Weekend!
Ciao,
Mario
[EMAIL PROTECTED] schrieb:
Author: skitching
Date: Fri Aug 17 04:19:22 2007
New Revision: 567017
URL:
[
https://issues.apache.org/jira/browse/MYFACES-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520533
]
Thomas Fischer commented on MYFACES-1711:
-
Added a second version of the patch.
The first version ( File
Hello Matthias,
On my side, I tested the new branch enough to vote on it whenever.
~ Simon
On 8/17/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
hi,
what are your feelings on starting the 1.2.2 release procedure by next
week, or the week after the next week ?
-Matthias
--
Matthias
[
https://issues.apache.org/jira/browse/MYFACES-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520540
]
Bernhard Huemer commented on MYFACES-1693:
--
I'll attach a patch whitch enables you to run MyFaces in a
[
https://issues.apache.org/jira/browse/TOBAGO-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bernd Bohmann resolved TOBAGO-472.
--
Resolution: Fixed
Rename the contrib directory to extension
[
https://issues.apache.org/jira/browse/MYFACES-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520571
]
Leonardo Uribe commented on MYFACES-1704:
-
I tried to replicate the error without success. Myfaces +
Hey everyone. After tearing though the buerocracy much slower then I
would have liked, I uploaded the code to MYFACES-1664 for the JSR-301
Portlet Bridge. This code should comply with the latest public draft of
the JSR-301 specification and, once we figure out where to put this and
get it
Hey everyone. After tearing though the bureaucracy much slower then I
would have liked, I uploaded the code to MYFACES-1664 for the JSR-301
Portlet Bridge. This code should comply with the latest public draft of
the JSR-301 specification and, once we figure out where to put this and
get it
If you want to build an email using JSF components and send it, have a
look at JBoss Seam.
FYI - this message should be on the users list, not the dev list
On 8/17/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Sure,
it's possible.
there is a demo inside of Trinidad (you have to update the
I can't reproduce a problem on that page using the latest 1.2.2,
and Glassfish with the JSF RI 1.2_04-b10-p01. I haven't had
a chance to test against the MyFaces 1.2.
-- Adam
On 8/15/07, Leonardo Uribe [EMAIL PROTECTED] wrote:
Hi
I have probed the trinidad demo example of 1.2.2 branch of
Sounds good to me. Should we open up a discussion though on where
this should be committed so that we can hit the ground running once the
paperwork is listed?
Scott
Matthias Wessendorf wrote:
On 8/17/07, Scott O'Bryan [EMAIL PROTECTED] wrote:
Hey everyone. After tearing though the
Me too.
-- Adam
On 8/17/07, Simon Lessard [EMAIL PROTECTED] wrote:
Hello Matthias,
On my side, I tested the new branch enough to vote on it whenever.
~ Simon
On 8/17/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
hi,
what are your feelings on starting the 1.2.2 release
ok, I think I'll do the plugins stuff early next week
-M
On 8/17/07, Adam Winer [EMAIL PROTECTED] wrote:
Me too.
-- Adam
On 8/17/07, Simon Lessard [EMAIL PROTECTED] wrote:
Hello Matthias,
On my side, I tested the new branch enough to vote on it whenever.
~ Simon
On
there was no real tomahawk bridge.
that stuff is part of myfaces 1.1 (the core impl)
the difference here is that 301 specifies a way, how a JSF 1.2
application should work inside a portal.
for jsf 1.1 there was just a note like JSF 1.1 should run in a
portlet... (very simplified statement)
So,
On 8/17/07, Scott O'Bryan [EMAIL PROTECTED] wrote:
Hey everyone. After tearing though the bureaucracy much slower then I
would have liked, I uploaded the code to MYFACES-1664 for the JSR-301
Portlet Bridge. This code should comply with the latest public draft of
the JSR-301 specification
Or yeah, what Matthias said. :)
Matthias Wessendorf wrote:
there was no real tomahawk bridge.
that stuff is part of myfaces 1.1 (the core impl)
the difference here is that 301 specifies a way, how a JSF 1.2
application should work inside a portal.
for jsf 1.1 there was just a note like JSF
sure, that's fine.
I think somewhere like
-myfaces
-portal-bridge
like a regular subproject, since it should be independent from myfaces 1.2.x
-Matthias
On 8/17/07, Scott O'Bryan [EMAIL PROTECTED] wrote:
Sounds good to me. Should we open up a discussion though on where
this should be
Yeah, I agree with that one. That was kinda my thought as well. Other
then the fact that it will be used for the R.I., we're going to have a
need to release versions of the bridge as EITHER JSF OR the portlet
framework rev. So we'll need to be a little more dynamic I'm thinking
on our
Does this bridge replace Tomahawk bridge?
On Aug 17, 2007, at 10:39 AM, Scott O'Bryan wrote:
Sounds good to me. Should we open up a discussion though on
where this should be committed so that we can hit the ground
running once the paperwork is listed?
Scott
Matthias Wessendorf wrote:
Excellent news!
Thanks!
On Aug 17, 2007, at 10:59 AM, Scott O'Bryan wrote:
Not yet, but I think it should eventually. This bridge is going to
be the standard as far as the JCP is concerned and the R.I. will be
taken from the work done here at Apache. It's going to evolve with
Portal
yeah, sort of.
there are currently (mainly for JSF 1.1) tons of JSF-Bridges
-Apache MyFaces Core (not Tomahawk ;-) )
-Apache Portals Bridges (they have that for old school struts as well)
-Suns RI has a module for JSF-Portlet integration
-,,,
so, this one fixes that.
It's a standard
javax.
Right. But for 1.2 and higher JSF implementations, you would not need
to use another bridge. This one should be the only one you'd need.
Scott
Matthias Wessendorf wrote:
yeah, sort of.
there are currently (mainly for JSF 1.1) tons of JSF-Bridges
-Apache MyFaces Core (not Tomahawk ;-) )
:-)
Yes, but I guess there might be some more impls out there,
like one that comes with the container ;-)
So, yes only one that goes with 301 (like this one ;-) )
-M
On 8/17/07, Scott O'Bryan [EMAIL PROTECTED] wrote:
Right. But for 1.2 and higher JSF implementations, you would not need
to
Hey, it looks like I did the impl, just not the API. I'm fixing that now.
That said, does the liscence need to be in the POM files? I didn't
notice a liscence in the MyFaces 1.2 POM files... I have no problems
putting it in, certainly, but we may want to make the 1.2 branch of
MyFaces
but all this, can be fixed, when it's already committed.
We needed NOTICE and LICENSE files inside both JARs as well.
-M
On 8/17/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
yes pom as well.
and also files in:
-META-INF/services/
-META-INF/
@myfaces: a bug
On 8/17/07,
Not yet, but I think it should eventually. This bridge is going to be
the standard as far as the JCP is concerned and the R.I. will be taken
from the work done here at Apache. It's going to evolve with Portal
standards (like JSR-286) and should be able to influence JSF 2.0 to
allow JSF to be
Ok.. but with this bridge and the right version of myfaces you would
not need something like the tomahawk bridge any more...
thanks a bunch!
On Aug 17, 2007, at 10:54 AM, Matthias Wessendorf wrote:
there was no real tomahawk bridge.
that stuff is part of myfaces 1.1 (the core impl)
the
Hey Scott,
did a quick look.
POMs and API .java class have to contain the Apache 2.0 license as well.
Greetings,
Matthias
PS: build runs :-)
On 8/17/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
there was no real tomahawk bridge.
that stuff is part of myfaces 1.1 (the core impl)
Aarg.. I thought I forgot something. Let me fix that and upload the zip.
Matthias Wessendorf wrote:
Hey Scott,
did a quick look.
POMs and API .java class have to contain the Apache 2.0 license as well.
Greetings,
Matthias
PS: build runs :-)
On 8/17/07, Matthias Wessendorf [EMAIL
Hi,
yes pom as well.
and also files in:
-META-INF/services/
-META-INF/
@myfaces: a bug
On 8/17/07, Scott O'Bryan [EMAIL PROTECTED] wrote:
Hey, it looks like I did the impl, just not the API. I'm fixing that now.
That said, does the liscence need to be in the POM files? I didn't
Couldn't reproduce on OC4J 11g TP with RI on my side, neither with Firefox
nor MSIE. Didn't try with MyFaces either.
~ Simon
On 8/17/07, Adam Winer [EMAIL PROTECTED] wrote:
I can't reproduce a problem on that page using the latest 1.2.2,
and Glassfish with the JSF RI 1.2_04-b10-p01. I
Yeah, I agree. I'll try to get that as soon as I can, but it's good to
know it won't hold up the committing. :)
Scott
Matthias Wessendorf wrote:
but all this, can be fixed, when it's already committed.
We needed NOTICE and LICENSE files inside both JARs as well.
-M
On 8/17/07, Matthias
chooseDate component ignores l10n for first day of week
---
Key: TRINIDAD-634
URL: https://issues.apache.org/jira/browse/TRINIDAD-634
Project: MyFaces Trinidad
Issue Type: Bug
Very cool. Good to know ;-).
~~~
Kito D. Mann - Author, JavaServer Faces in Action
http://www.virtua.com - JSF/Java EE consulting, training, and mentoring
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info
* Sign up
panelBox skinning keys in purple skin demo are obsolete
---
Key: TRINIDAD-635
URL: https://issues.apache.org/jira/browse/TRINIDAD-635
Project: MyFaces Trinidad
Issue Type: Bug
[
https://issues.apache.org/jira/browse/TRINIDAD-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520648
]
Jeanne Waldman commented on TRINIDAD-635:
-
Also, make sure to doc in skin-selectors the 'included' styles.
Skinning an icon does not pick up base skin's non-overridden properties
---
Key: TRINIDAD-636
URL: https://issues.apache.org/jira/browse/TRINIDAD-636
Project: MyFaces Trinidad
[
https://issues.apache.org/jira/browse/TRINIDAD-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-630.
-
Resolution: Fixed
Fix Version/s: 1.0.3-core
Assignee: Adam Winer
Fixed. Also
[
https://issues.apache.org/jira/browse/TRINIDAD-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer resolved TRINIDAD-633.
-
Resolution: Fixed
Fix Version/s: 1.0.3-core
Assignee: Adam Winer
StyleNode
45 matches
Mail list logo
