gmane.comp.java.cdi.seam.devel

Seam 2.3.0.Beta2 is available

Marek Novotny — 2012-05-23T15:09:38

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Some progress with Seam 2 ;-)

Full announcement is at

https://community.jboss.org/blogs/marek-novotny/2012/05/23/seam-230beta2-is-out

Enjoy it!

- -- 
Marek Novotny
- --
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+8/bIACgkQU4HO8G8hNxUQxwCg6geSsQzD9dwo83C+qssmI6Ai
3XkAnR0ZazGyZkjOL158GU83bc3hmX8I
=r3kE
-----END PGP SIGNATURE-----

Seam 2.3 branch is frozen, don't commit there

Marek Novotny — 2012-05-21T14:51:46

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

As all issues in JIRA for Seam 2.3.0.Beta2 is resolved.  Please don't
make any commits to the
https://svn.jboss.org/repos/seam/branches/community/Seam_2_3 without
checking with me and getting approval from
      this mail list first.

When the tag is created branch will be unfrozen and announced here.

Cheers,

- -- 
Marek Novotny
- --
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+6VoIACgkQU4HO8G8hNxX+KgCeOigo3hDZMnFZh4EdE9uLzV/6
O+YAoOufCU6zExpXQspPxsJmgBYNGUxU
=vsZ5
-----END PGP SIGNATURE-----

JBAS 7.1 asking me to create a file called .war.dodeploy for app created in JBT

Daniel Hinojosa — 2012-05-16T14:06:19

Hey Alexey,

When deploying and testing from JBT to JBAS7.1.1 I get the message:

07:53:09,039 INFO  [org.jboss.as.server.deployment.scanner]
(DeploymentScanner-threads - 1) JBAS015003: Found test-seam.war in
deployment directory. To trigger deployment create a file called
test-seam.war.dodeploy

What is responsible for this file? seam-gen or JBT?

Thanks, Alexey.

CC:ed relevant groups for public disclosure, bringing "open" to "open
source" ;)



07:53:00,223 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA
07:53:01,164 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA
07:53:01,442 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final
"Brontes" starting
07:53:04,993 INFO  [org.xnio] XNIO Version 3.0.3.GA
07:53:05,007 INFO  [org.jboss.as.server] JBAS015888: Creating http
management service using socket-binding (management-http)
07:53:05,045 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
07:53:05,087 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
07:53:05,240 INFO  [org.jboss

Seam 2.3.0.Beta2 is coming this week

Marek Novotny — 2012-05-16T07:55:23

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Seam devs,

this week is important for Seam 2.3 development. We are very close to
finish all issues identified for 2.3.0.Beta2 - right now 6 issues remaining.

After 2.3.0.Beta2 there will be some time to get feedback and
investigate stability of 2.3.0.Beta2 on coming AS 7.1.2. Then will come
our first CR for this branch - hopefully finished by releasing
2.3.0.Final long way so far ;-).

Cheers,


- -- 
Marek Novotny
- --
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+zXWsACgkQU4HO8G8hNxW0HwCgyrsyuEc2OVc3xE4B7FoD4HMo
1W8AoJawirdh5jt692WFwGOhkD9AGQQR
=OZ/3
-----END PGP SIGNATURE-----

janino.jar

Daniel Hinojosa — 2012-05-08T18:49:54

Marek, Marek, Pete,

Not finding much use for this, and not involved in any project, yet it is
on the list.  I am going to gut it from the list unless there are objections

What is expected of JBoss Seam 2.3 for JBoss Tools

Daniel Hinojosa — 2012-05-02T18:24:10

I got done with a Skype conversation with Alexey Kazakov on how JBoss Tools
will interact with the new Seam 2.3.  The points are below. Some further
questions are asked below.  Many of you already know most of what is going
on, this email is for clarification, information and to make this process
as public as possible.


*  Latest JBT is used with Eclipse 3.7.2 Indigo
*  Seam 2.3 uses maven, therefore all dependencies are done through maven
*  JBT WILL NOT be using Maven
*  JBT only needs the initial seam distribution (zip file with lib) to have
everything it needs to create a seam web project.
*  Once JBT has the initial distribution and libraries it can then use that
to create a seam web project.
*  If the end user wishes to use JBT, they have to download the
distribution, map it to SEAM_HOME.
*  If the end user doesn't wish to use JBT, they can just add dependencies
to their maven pom files, and do what they want.
*  If the end user wants to use JBT AND Maven, that will not be supported
currently (Need Ve

issue trying to put OAuth in Seam Security External

Antoine Sabot-Durand — 2012-04-20T06:58:37

Hi all,

I worked on OAuth integration in Seam Security.

Markek provided some code in Seam Social but I found it more relevant to put it in Security. So I moved and refactored the Authenticator in Seam Security External. Everything seems ok but I can't start the Web example application having this exception.

org.jboss.weld.exceptions.DeploymentException: WELD-001408 Unsatisfied dependencies for type [SamlSignatureUtilForPostBinding] with qualifiers [< at >Default] at injection point [[field] < at >Inject private org.jboss.seam.security.external.saml.SamlMessageSender.signatureUtilForPostBinding]

I tested my security classes directly in the web app : it works. So I can't put them in external since I need to configure unrelated beans to avoid Weld error at boot time. 

I pushed the code for others to test.  Start with example/oauth web app. The version works. If you delete org.jboss.seam.security.external.oauth and org.jboss.seam.security.external.oauth.api package from the web app and add security-external (which co

Java EE6 BOM for seam 2.3

Daniel Hinojosa — 2012-04-13T00:19:34

Is that still installed? I seem to remember that it was at one time because
most tests would pass on some of the examples that I am working on, now it
has no referral to any dependency management in the parent poms.

        <dependency>
            <groupId>org.hibernate.javax.persistence</groupId>
        <artifactId>hibernate-jpa-2.0-api</artifactId>
        </dependency>
        <dependency>
            <groupId>org.jboss.spec.javax.el</groupId>
            <artifactId>jboss-el-api_2.2_spec</artifactId>
        </dependency>

Releasing Seam 2.3.0.Beta1

Marek Novotny — 2012-03-28T16:10:05

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Seam devs,

 I created a tag for Seam 2.3.0.Beta1 at
http://anonsvn.jboss.org/repos/seam/tags/JBoss_Seam_2_3_0_Beta1

Maven artifacts are deployed at JBoss staging repository for
verification at https://repository.jboss.org/nexus/content/groups/staging/.

I will continue with next steps like uploading Seam 2.3.0.beta1
distribution and documentation.

More later.

Branch https://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/
is now switched to next development version 2.3.0.Beta2-SNAPSHOT.


- -- 
Marek Novotny
- --
WFK and Seam Product Lead

Red Hat Czech s.r.o.
Purkynova 99
612 45 Brno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9zN90ACgkQU4HO8G8hNxXWHgCeJuyqe61Cx9LxwWCuqhNZXGTZ
taUAniHL1DqnFvrxNaT8a5lveIMe5JcD
=1jXI
-----END PGP SIGNATURE-----

Date and content for Seam 3.1.1

Jason Porter — 2012-03-26T20:36:20

I know I've said in the past we need to get on a date for this :) Here I am
doing that now. I would like to propose April 30th for 3.1.1. This would be
a minor release addressing bugs, documentation and examples.

I know I blogged [1] about some additional examples so I think we have
those covered. We may not distribute them, but simple have them in a README
or something like that. Of course I'm open to other ideas here.

For bugs and documentation I'm looking for some help from all of you to
categorize issues and documentation spots we really need to focus on
correcting and improving. Does everyone feel like Friday would be enough
time for people get that list in, or should we extend it to next Wednesday?
I don't want to go too long and not have enough time to get things done.


[1]
https://community.jboss.org/blogs/lightguardjp/2012/02/24/seam-3-examples

Forge 1.0.1.Final Released

Lincoln Baxter, III — 2012-03-23T16:52:27

http://jboss.org/forge

Now with support for scaffolding reverse-engineered database Models. Over
22 features/bugs/issues completed. Thanks to Pete Muir, Burr, and Koen Aers
for being the uber-usability-testers. Special thanks to Thomas Fruebeck and
Richard Kennard for fixing the scaffolding custom < at >Id fields issue, and for
everyone else who made this release a success.

Start writing plugins for your projects! ;)

https://docs.jboss.org/author/display/FORGE/Reference+the+Forge+APIs
Bug

   - [FORGE-486 <https://issues.jboss.org/browse/FORGE-486>] - Scaffolding
   an entity with an enum fails
   - [FORGE-490 <https://issues.jboss.org/browse/FORGE-490>] - Cannot
   access configuration outside of an active Project context
   - [FORGE-491 <https://issues.jboss.org/browse/FORGE-491>] - REST plugin
   creates compilation errors when "id" setter is not called "setId()"
   - [FORGE-492 <https://issues.jboss.org/browse/FORGE-492>] - REST facet
   does not recognize Application class with ApplicationPath annotation

Seam 2.3 and Conversation init/restore in RESTORE_VIEW(JSF2)

Marek Novotny — 2012-03-22T15:18:39

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Seam devs,

 I am fighting with the design mismatch between Seam 2 Conversation
init/restore and JSF2 new logic in Restore view.

The original issue https://issues.jboss.org/browse/JBSEAM-4898 was
created as "Page scope components are not available in Postback
request". But as we have migrated Dvdstore example to JSF2/JPA 2, I see
that issue also as Conversation scope components are not available
(specifically outjected components) in case of long running and nested
conversations.

I have attached patch which is more than a fix a wicked hack, it
alongside changes jsf dependency from Optional to Required.

I would appreciate any help/advice.

 Cheers,

- -- 
Marek Novotny
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9rQs8ACgkQU4HO8G8hNxVwQgCePY0s9TOIsN+IEFPOL8FEwzLD
M4gAoNXncPqs0/s+HgH1pUxE/DCyeqPT
=ge3g
-----END PGP SIGNATURE-----

Has anyone tried to use Seam 2.x and Hibernate 4.1.x (org.hibernate.session has a few new methods)...

Scott Marlow — 2012-03-19T15:25:25

Hibernate 4.1.x org.hibernate.Session 
(https://github.com/hibernate/hibernate-orm/commit/3071fa892fd6c08b37983a5869c0b7ca14e4180d#L0L825) 
has a few new methods.  Will this have any impact on Seam 2.x 
applications that have upgraded to Hibernate 4.0.x already?

Scott

Permission Request for 'Seam Framework - REST Mod...'

Deborah Markovski — 2012-03-06T17:40:19

Hello,

I've known you website for ages, strictly speaking from year 2010. I found  
interesting your publication Seam Framework - REST Module Home which I  
googled on http://seamframework.org/Seam3/RESTModule ! I'd love to use it  
in a project I'm involved with called "WHW Science", so I'm seeking your  
permission. "WH Science" is a freemium-model non-English language  
orientated startup with collection of scientific articles, personal notes  
etc. in several languages that is collaboratively edited by volunteers from  
around the world since 1999. Young and old, students and professors - even  
your neighbor could be a volunteer member.
If you agree, we will credit you for your work in the resulting  
translation's references by stating that it was based on your work and is  
used with your permission, and by mentioning the name of my project "WH  
Science" back to:
http://seamframework.org/Seam3/RESTModule

Thank you for your time and patience.
I look forward to your response next week.

---
Best wish

JMS deadlock issue in JBoss AS7 7.1 Final

Ove Ranheim — 2012-02-28T14:45:14

Hi,

I have identified a deadlock situation with JBoss 7.1.0 Final and HornetQ.

Please check out: https://issues.jboss.org/browse/AS7-3919

Could this be related to Seam JMS?

Ove

Meeting 2012-02-22

Jason Porter — 2012-02-22T20:52:56

The only thing I have to talk about is a date for 3.1.1. If people would
like to attend a meeting for that today great I'll be in IRC. If you'd
simply like to respond to this email we can do it that way as well.

We've talked about 3.1.1 simply being examples, better documentation and
some minor bug fixes.

Please review

Jason Porter — 2012-02-14T00:08:54

https://github.com/seam/migration/blob/develop/open18_java_ee_6/migration_steps.rst

I have all of the sections I had originally flesh out with some text. I
would appreciate anyone who has done any Seam 2 => EE 6 migration to take a
look, fork, issue pull requests, etc. Thank you everyone for the help.

Meeting minutes 2011-02-01

Lincoln Baxter, III — 2012-02-02T03:42:54

10:14:09 AM jbott: Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2012/forge.2012-02-01-15.03.html
10:14:09 AM jbott: Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2012/forge.2012-02-01-15.03.txt
10:14:09 AM jbott: Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/forge/2012/forge.2012-02-01-15.03.log.html

No meeting this week

Jason Porter — 2012-01-31T22:41:25

I'll be up late / early depending on how you look at it with the forum
migration. I also don't have anything to really talk about.

JBoss Seam 2.3 Archetype for maven

Daniel Hinojosa — 2012-01-30T20:26:54

Since 2.3 is mavenized should there a be a mvn archetype :
jboss-seam-2.3-ear and jboss-seam-2.3-war?  There are
currently jboss-javaee6-webapp-archetype but I think those are WELD/CDI
based applications.

Moving Oauth authenticator to Seam Security

Antoine Sabot-Durand — 2012-01-27T09:05:51

Hi All,


Marek did a great job by creating an Oauth authenticator for Seam Security in Seam Social. Now I think it would be better to move it to Security external modules (beside OpenId). From a user point of view I think it would be more consistent to have all authentication module in the same place.

If there are no objection I'll move the code (Shane gave me right on Security looooong ago) or provide a pull request.

regards,

Antoine SABOT-DURAND