I am using the Seam 2.2.0.GA. But it does not get loaded in eclipse. It cribs about verion incompatibility. Any clue on how to solve the same.

Thanks. B

As of right now (8/7/09) there is an issue with JBAS 5.1.0GA that prevents Seam from reliably deploying/hot-deploying

See:

Issues with Seam 2.2.0 and JBAS 5.1.0GA

Seam deployments and hot deployments in AS 5.1.0

and

FAQ: What happens when you deploy Seam app in JBoss5?

I am having problems with

<page conversation-required="true" no-conversation-view-id="home.xhtml">

The conversation is being propagated normaly, and this piece of code worked well in 2.1, but this tag is not correctily identifing the conversation and redirecting the page to the home in the wrong way.

Is this a Bug or something? Please help.

Also published this as a topic when tring to reply this tread... but I was no able to delete that... http://seamframework.org/Community/Conversationrequiredtrue#comment91260

What is missing is a compatibly matrix that can be updated to show what version on seam works with

- RichFaces

- Hibernate

- JBoss AS

That way we could let everyone know that maybe RichFaces 3.3.1 works with Seam 2.0...or that it doesn't.

Also so that people know Seam doesn't work on JBAS 5.1 currently.

Is this something we could setup in the wiki?

That´s a really good idea. The matrix could cover Eclipse and Netbeans (other IDEs..) compatibility too.

Any experts with the wiki that want to take a first crack at this?

I need to upgrade a couple of projects I built with seam-gen in Seam version 2.1.2. Is there a set of instructions on how to do that? What files need replacement/merging?

Thanks.

--Peter

Walter Barrow wrote on Oct 22, 2009 22:40:
Hello. We have a simple Seam application using Wicket which attempts to start a Quartz timer task (using @Asynchronous annotation) in the init() method of the main application (a subclass of SeamWebApplication). We first built this application using Seam 2.1.1.GA and we had no problem and the timer got activated properly. We recently upgraded to Seam 2.2.0.GA and this functionality stopped working. Instead, when we try to activate the timer task (inital call), we get a NPE thrown in the AsynchronousInterceptor when it attempts to access the EventContext, which is null (see log exerpt, below). When I put calls to Lifecycle.beginCall() and Lifecycle.endCall() around this code, the timer is activated with no apparent errors. My question is this: Is this something broken in 2.2.0.GA? If not, is my workaround an appropriate solution? I will be happy to provide my code if you want to look at it.

I changed the way that wicket/seam initialized itself for the 2.2.x branch. You don't get a full set of seam contexts at wicket init() time. The seam-recommended approach to starting things at app-startup time, independent of view framework choice, is:

@Observer("org.jboss.seam.postInitialization") public void setupTasks() { /*do things here*/ }

-Clint

Thanks! I'll give that a try.

Hello,

I have a simple Wicket application built to run with Seam that I use to demonstrate conversations to my co-workers. This application worked fine with Seam 2.1.1.GA, but no longer works with 2.2.0.GA. It seems that my @Begin and @End tags placed on callback methods are being ignored. I tried injecting the Conversation component and manually starting/stopping conversations, but that failed, too. Are there known problems with 2.2.0.GA, Wicket, and conversations? If so, are there any workarounds?

Thanks!

Walt Barrow

I feel like we're hijacking this thread...can you post anew, with a code sample of what you're doing, and also a description of how you are approaching instrumentation of the seam components (i.e. WEB-INF/wicket vs. @SeamWicketComponent, runtime vs. compile-time instrumentation.)

Thanks,

-Clint

Clint, I started a new thread Seam 2.2.0.GA, Wicket -cannot start longrunning conversation

Hello !!

I do not know if is a BUG in this release (and previews).

When you define in pages.xml the exception handler :

 <exception class="org.jboss.seam.security.NotLoggedInException">
    <redirect view-id="/pages/login.jspx">
       <message severity="warn">Please log in first</message>
     </redirect>
 </exception>

And in your template.xhtml use this to show all messages :

<h:messages id="messages" globalOnly="true" styleClass="message"
  errorClass="errormsg" infoClass="infomsg" warnClass="warnmsg"
  rendered="#{showGlobalMessages != 'false'}" />

And in your Pojo Class, you define a restrict access :

@Name("CommentService")
@Restrict("#{s:hasRole('USER')}")
public class CommentService {
  ...
}

The seam is adding two warn messages on page : Please log in first, one come from Identity and the other one come from NotLoggedInException treatment (pages.xml), see bellow the Identity class bellow.

Is it a bug ? Is there some trick for it ? I am not sure, but I saw something about you are removing all hard-coded set messages by Events.instance().raiseEvent(XXXX);

org.jboss.seam.security.Identity

public void checkPermission(Object target, String action)
   
 public void checkPermission(Object target, String action)
   {
      if (systemOp != null && Boolean.TRUE.equals(systemOp.get())) return;
      
      tryLogin();
      
      if ( !hasPermission(target, action) )
      {   
         if ( !isLoggedIn() )
         {
            if (Events.exists()) Events.instance().raiseEvent(EVENT_NOT_LOGGED_IN);
            throw new NotLoggedInException();            
         }
         else
         {
            if (Events.exists()) 
  1 ->        Events.instance().raiseEvent(EVENT_NOT_AUTHORIZED);
  2 ->        throw new AuthorizationException(String.format("Authorization check failed for permission[%s,%s]", target, action));
         }
      }
   }  
     

Thanks for help me !

Hi friends,

I marked the wrong lines :)

public void checkPermission(Object target, String action)
   
 public void checkPermission(Object target, String action)
   {
      if (systemOp != null && Boolean.TRUE.equals(systemOp.get())) return;
      
      tryLogin();
      
      if ( !hasPermission(target, action) )
      {   
         if ( !isLoggedIn() )
         {
            if (Events.exists())
1 ->          Events.instance().raiseEvent(EVENT_NOT_LOGGED_IN);
2 ->          throw new NotLoggedInException();            
         }
         else
         {
            if (Events.exists()) 
              Events.instance().raiseEvent(EVENT_NOT_AUTHORIZED);
              throw new AuthorizationException(String.format("Authorization check failed for permission[%s,%s]", target, action));
         }
      }
   }