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-----

Re: Seam 2.3 branch is frozen, don't commit there

Marek Novotny — 2012-05-21T22:46:42

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

Tag Seam 2.3.0.Beta2 was created at
https://svn.jboss.org/repos/seam/tags/JBoss_Seam_2_3_0_Beta2

The branch is again open for commits.

Distribution and Maven artifacts will be announced later.

On 05/21/2012 04:51 PM, Marek Novotny wrote:

- -- 
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+6xdIACgkQU4HO8G8hNxUc9ACgv756iq5YarXueHGGTSM/hPdS
OJkAoLGMXgP79Ap6YW5AWh5GjJFiIwGu
=agCh
-----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-----

Re: [jbosstools-dev] JBAS 7.1 asking me to create a file called .war.dodeploy for app created in JBT

Lincoln Baxter, III — 2012-05-21T04:01:10

This is the normal method of triggering a deployment in AS7. If you use
JBoss Tools or the JBoss AS7 Maven Plugin (you can use Forge to install and
use this easily), this would have happened automatically, but if you are
doing a deployment by hand then you'll need to create the necessart files.

On Wed, May 16, 2012 at 1:19 PM, Max Rydahl Andersen <
max.andersen-H+wXaHxf7aLQT0dZR+AlfA< at >public.gmane.org> wrote:

Re: [jbosstools-dev] JBAS 7.1 asking me to create a filecalled .war.dodeploy for app created in JBT

Max Rydahl Andersen — 2012-05-16T17:19:21

Yes, if you are using our AS 7.x server adapter it will create this file automatically.

How did you deploy it ?

/max

On May 16, 2012, at 19:01 , Alexey Kazakov wrote:

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

Alexey Kazakov — 2012-05-16T17:01:46

I guess such a file should be created by JBoss AS Tools.
Rob, Max?


On 05/16/2012 07:06 AM, Daniel Hinojosa wrote:

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.as.logging] JBAS011502: Removing bootstrap
log handlers
07:53:05,285 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool --
26) JBAS016200: Activating ConfigAdmin Subsystem
07:53:05,371 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38)
JBAS011800: Activating Naming Subsystem
07:53:05,383 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39)
JBAS011940: Activating OSGi Subsystem
07:53:05,330 INFO  [org.jboss.as.clustering.infinispan] (ServerService
Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
07:53:05,440 INFO  [org.jboss.as.security] (ServerService Thread Pool --
44) JBAS013101: Activating Security Subsystem
07:53:05,584 INFO  [org.jboss.as.webservices] (ServerService Thread Pool --
48) JBAS015537: Activating WebServices Extension
07:53:05,777 INFO  [org.jboss.as.security] (MSC service thread 1-5)
JBAS013100: Current PicketBox version=4.0.7.Final
07:53:05,853 INFO  [org.jboss.as.naming] (MSC service thread 1-8)
JBAS011802: Starting Naming Service
07:53:05,906 INFO  [org.jboss.as.connector] (MSC service thread 1-8)
JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)


07:53:06,075 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-8)
JBAS015400: Bound mail session [java:jboss/mail/Default]
07:53:06,171 INFO  [org.jboss.as.connector.subsystems.datasources]
(ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant
driver class org.h2.Driver (version 1.3)
07:53:06,925 INFO  [org.jboss.ws.common.management.AbstractServerConfig]
(MSC service thread 1-7) JBoss Web Services - Stack CXF Server 4.0.2.GA
07:53:07,190 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service
thread 1-3) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
07:53:08,661 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC
service thread 1-7) JBAS010400: Bound data source
[java:jboss/datasources/ExampleDS]
07:53:09,017 INFO  [org.jboss.as.server.deployment.scanner] (MSC service
thread 1-5) JBAS015012: Started FileSystemDeploymentService for directory
/home/danno/java/jboss-as-7.1.1.Final/standalone/deployments
07:53:09,026 INFO  [org.jboss.as.remoting] (MSC service thread 1-6)
JBAS017100: Listening on /127.0.0.1:9999
07:53:09,026 INFO  [org.jboss.as.remoting] (MSC service thread 1-8)
JBAS017100: Listening on localhost/127.0.0.1:4447
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
07:53:09,322 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951:
Admin console listening on http://127.0.0.1:9990
07:53:09,324 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874:
JBoss AS 7.1.1.Final "Brontes" started in 10309ms - Started 133 of 208
services (74 services are passive or on-demand)
07:53:09,363 INFO  [org.jboss.as.server.deployment] (MSC service thread
1-2) JBAS015876: Starting deployment of "test-seam-ds.xml"
07:53:09,363 INFO  [org.jboss.as.server.deployment] (MSC service thread
1-1) JBAS015876: Starting deployment of "hsqldb-2.2.4.jar"

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-----

Re: janino.jar

Marek Novotny — 2012-05-09T06:30:21

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

it was replaced in drools 5.1.1 dependencies by ecj.jar

On 05/08/2012 08:49 PM, Daniel Hinojosa wrote:


- -- 
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+qDv0ACgkQU4HO8G8hNxXsuACeNa/rRTDBjLnDOAzlL1JWZhPU
ixYAoLy1CritvHWnppzCrAiLuD/yrNad
=nNHx
-----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

Re: [jbosstools-dev] What is expected of JBoss Seam 2.3 for JBoss Tools

Marek Novotny — 2012-05-02T19:15:41

Dan,

  Alexey commented your points/questions fairly well, so I hope you have 
clear understanding now ;-)

Just short summary:
1. Distribution assembly is Seam 2 support for ant users and seam-gen. 
(Maven users don't care much about distribution files)

2. Seam-gen is command line tool and JBoss Tools wizards mimic only 
invocations of these seam-gen command and collects inputs from user to 
create Seam projects/components/actions/forms etc.

3. JBoss Tools relies on seam-gen file templates, therefore what we will 
update and works in pure seam-gen, it should be used in JBoss Tools 
without issues and just works.


On 2.5.2012 20:49, Alexey Kazakov wrote:

Re: [jbosstools-dev] What is expected of JBoss Seam 2.3for JBoss Tools

Daniel Hinojosa — 2012-05-02T19:08:08

Great to know.. Thanks, Alexey

On Wed, May 2, 2012 at 12:49 PM, Alexey Kazakov <akazakov-BiWsVsXcoF7QT0dZR+AlfA< at >public.gmane.org> wrote:

Re: [jbosstools-dev] What is expected of JBoss Seam 2.3 for JBoss Tools

Alexey Kazakov — 2012-05-02T18:49:29

See my comments below.

On 05/02/2012 11:24 AM, Daniel Hinojosa wrote:
I would say JBoss Tools Seam Wizards (New Project, Action, Form, etc.) 
are not going to use Maven. But JBT has some maven features (seam 
support enabled automatically if you import a maven project with seam 
dependencies, mavenized seam project examples, etc.)
JBT does not use SEAM_HOME at all. We use our internal settings for 
eclipse projects to map it to the seam distribution.
Again, JBT can help here too, but if we are talking about Seam Wizards 
then this is correct.
Not supported by Seam Wizards. Since they are seam-gen based. All the 
problems we have right now are related to our Seam Wizards. Our seam 
maven integration works fine afaik. Just to be clear.
JBT does not use seam.sh, seam.bat or any scripts directly. We used them 
only during development to mimic its logic. But we still need the lib 
folder, the list of jars and templates (xhtmls, xmls, etc) and hope the 
scripts won't change much so we won't have to rewrite our wizards 
completely.
Again, JBT doesn't use seam scripts. See the previous comment.

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 Verification)
*  JBT will expect that the end distribution of Seam will have a lib folder
with required jars, a list of jars, and a seam.sh and seam.bat to run
seam-gen
*  Seam 2.3 has a distribution module that creates the final distribution
and uses the assembly plugin to achieve what JBT needs, this is the focus
currently:

https://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/distribution/
*  JBT will still require seam.bat or seam.sh scripts so it can create
entities and actions and that is already part of the current distribution


https://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/distribution/src/main/assembly/



If this is not correct, please correct since if there is something wrong,
it's because of a lack of understanding on my part.

Hope this is beneficial.

Danno

Seam gen issues affecting JBoss Tools and its Seam 2integrations

Marek Novotny — 2012-04-28T09:22:12

Hi Max and Alexey,

 here is the JIRA filter for issues which affect JBoss Tools and its Seam2 integration - https://issues.jboss.org/secure/IssueNavigator.jspa?mode=hide&requestId=12317111

I will group all issues like these with label seam-gen and component Tools.

Cheers,

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 contains the same classes) as a dependence you'll have the exception.

regards,


Antoine SABOT-DURAND

Re: Java EE6 BOM for seam 2.3

Marek Novotny — 2012-04-13T08:09:45

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

Daniel,

 it should work, even I am in the middle of re-factoring of seam parent.
Current Seam parent is here
https://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/pom.xml
and it imports org.jboss.bom:jboss-javaee-6.0-with-hibernate:1.0.0.M6.
Final solution will be like all dependencies, which are used in any
Seam2 Applications (e.g. our examples), will be moved to
https://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/bom/pom.xml
and this Seam2 BOM will be imported in Seam parent.

So users can import Seam 2 BOM file with dependency management and use
them in their applications without checking/updating all seam module
versions.

This is simple standard how to say Maven user what dependencies are
verified and used in Seam2 build.

As an example of usage is the following snippet from any Seam 2
application:

<dependencyManagement>
<dependencies>
<dependency>
  <groupId>org.jboss.seam</groupId>
  <artifactId>bom</artifactId>
  <version>2.3.0.Beta2-SNAPSHOT</version>
  <type>pom</type>
  <scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>

<dependencies>
<dependency>
  <groupId>org.jboss.seam</groupId>
  <artifactId>jboss-seam</artifactId>
  <type>ejb</type>
</dependency>

<dependency>
  <groupId>org.jboss.seam</groupId>
  <artifactId>jboss-seam-ui</artifactId>
  <type>ejb</type>
</dependency>

...
</dependencies>

On 04/13/2012 02:19 AM, Daniel Hinojosa wrote:


- -- 
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+H30kACgkQU4HO8G8hNxUjQACgo/S7ftO0kn33JdE6y9kolm5D
EJEAoNvw6ulXMVQxnFoqnuiw4foj/+Xc
=hNGw
-----END PGP SIGNATURE-----

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>

Re: Date and content for Seam 3.1.1

Lincoln Baxter, III — 2012-04-07T15:33:24

I'd really like to see a new release for the Security Enhancements that I
put in (and also put in to DeltaSpike)

On Thu, Apr 5, 2012 at 7:32 PM, John D. Ament <john.d.ament-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>wrote:

Re: Date and content for Seam 3.1.1

John D. Ament — 2012-04-05T23:32:57

I have a few small things for Seam JMS to support a 3.1.1 release, focusing
on better support in AS 7.x and WLS 12c

On Tue, Apr 3, 2012 at 11:14 AM, Jason Porter <lightguard.jp-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>wrote:

Re: Date and content for Seam 3.1.1

Jason Porter — 2012-04-03T15:14:56

Here are the tickets I'm thinking for a bundled 3.1.1 release, please
comment:

https://issues.jboss.org/browse/SEAMSECURITY-142 (maybe not doable?)
https://issues.jboss.org/browse/SEAM-133
https://issues.jboss.org/browse/SOLDER-116 (Unless this is a weld bug)
https://issues.jboss.org/browse/SEAMPERSIST-74 (Do we want to tackle all
these INFO logging during startup by creating other jars?)
https://issues.jboss.org/browse/SOLDER-325 (This may not actually be a
problem)
https://issues.jboss.org/browse/SOLDER-324
https://issues.jboss.org/browse/SEAMFACES-44
https://issues.jboss.org/browse/SEAMSECURITY-71
https://issues.jboss.org/browse/SOLDER-99 (This doesn't actually seem to be
our problem)
https://issues.jboss.org/browse/SOLDER-311
https://issues.jboss.org/browse/SEAMFACES-232
https://issues.jboss.org/browse/SEAMFACES-168

Also we need to cleanup documentation for projects that really need it. Off
the top of my head I'm thinking Security, Persistence especially.

If it seems like people are too busy, or I don't get many responses I'll
probably drop this whole idea as I don't have time to do all of them myself.

On Mon, Apr 2, 2012 at 09:17, Jason Porter <lightguard.jp-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote: