ansaurus

Question

Jboss Seam: Enabling Debug page on WebLogic 10.3.2 (11g)

Answer 1

+1 A:

You get the following exception

No phase id bound to current thread (make sure you do not have two SeamPhaseListener instances installed)

But you said you have installed an ejb and web maven project. Maybe both includes a SeamPhaseListener when you deploy your application. It, maybe, explains why you get your exception (Two SeamPhaseListener instances installed).

My advice is (And if you want to avoid a lot of headache)

Always generate your project by using Seam-gem

See here why

A nice article, besides Seam in Action book, about JSF/Seam can be found here

Added to original answer

See what Seam in Action book talks about it

In Seam 2.0, the Seam phase listener is declared in a facesconfig.xml descriptor that is included in the core Seam JAR file, jboss-seam.jar. Thus, the phase listener is available as soon as you include this JAR file in your application.

So, you do not have to worry about SeamPhaseListener. Seam will.

UPDATE

First of all, you have a ear application. Before going on

1º Each EJB and war module should be declared in application.xml (The file that describes your ear)

So your ear application should looks like this one (Let's call your ear application pureCharger)

pureCharger.ear

    META-INF
        application.xml
    pureCharger-ejb.jar
        META-INF
            ejb-jar.xml
            persistence.xml
        lib
            // libraries ONLY USED by your EJB module goes here
    pureCharger-war.war
        WEB-INF
            web.xml
            components.xml
            faces-config.xml
            pages.xml
        lib
            // Here is what you want
            jboss-seam-debug.jar 
            jboss-seam-ui.jar
            jsf-facelets.jar
            // other libraries ONLY USED by your war module goes here
    jboss-seam.jar
    lib
        // JBoss Expression Language is used by both EJB and war module
        jboss-el.jar
        // libraries SHARED by all of your modules goes here

ejb-jar.xml is shown as follows (It enables @In-jection by your EJB components)

<?xml version="1.0" encoding="UTF-8"?>
<ejb-jar xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" version="3.0">
    <interceptors>
        <interceptor>
            <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>
        </interceptor>
    </interceptors>
    <assembly-descriptor>
        <interceptor-binding>
            <ejb-name>*</ejb-name>
            <interceptor-class>org.jboss.seam.ejb.SeamInterceptor</interceptor-class>
        </interceptor-binding>
    </assembly-descriptor>
</ejb-jar>

2º jboss-seam.jar is an EJB module

So it should also be declared in application.xml file. And more, as said above, you do not have to define SeamPhaseListener because of jboss-seam.jar includes SeamPhaseListener. So avoid to see this nice message

Two SeamPhaseListener instances installed

So your ear application.xml should looks like this one

<?xml version="1.0" encoding="UTF-8"?>
<application version="5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"&gt;
    <display-name>pureCharger</display-name>
    <module>
        <ejb>pureCharger-ejb.jar</ejb>
    </module>
    <module>
        <ejb>jboss-seam.jar</ejb>
    </module>
    <module>
        <web>
            <web-uri>pureCharger-war.war</web-uri>
            <context-root>pureCharger</context-root>
        </web>
    </module>
</application>

ok. Let's go

3º You want to enable debug page

The Seam debug page will be available if this jar is deployed in WEB-INF/lib, along with the Facelets, and if you set the debug property of the init component

So your components.xml should looks like this one

<?xml version="1.0" encoding="UTF-8"?>
<components xmlns="http://jboss.com/products/seam/components"
    xmlns:core="http://jboss.com/products/seam/core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="
    http://jboss.com/products/seam/core
    http://jboss.com/products/seam/core-2.2.xsd
    http://jboss.com/products/seam/components
    http://jboss.com/products/seam/components-2.2.xsd"&gt;
    <core:init jndi-pattern="pureCharger/#{ejbName}/local" debug="true"/>
    <core:manager concurrent-request-timeout="500" conversation-timeout="120000" conversation-id-parameter="cid" />
</components>

See as shown above i have defined global JNDI address (I suppose you are using JBoss and your ear application is called pureCharger) in order to Seam retrieve its EJB component

And finally, our web.xml file

<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"&gt;
    <context-param>
        <param-name>facelets.DEVELOPMENT</param-name>
        <param-value>true</param-value>
    </context-param>
    <context-param>
        <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
        <param-value>.xhtml</param-value>
    </context-param>
    <context-param>
        <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
        <param-value>server</param-value>
    </context-param>
    <!--It must be the first-->
    <filter>
        <filter-name>Seam Filter</filter-name>
        <filter-class>org.jboss.seam.servlet.SeamFilter</filter-class>
    </filter>
    <filter-mapping>
        <filter-name>Seam Filter</filter-name>
        <url-pattern>/*</url-pattern>
    </filter-mapping>
    <!--It must be the first-->
    <listener>
        <listener-class>org.jboss.seam.servlet.SeamListener</listener-class>
    </listener>
    <servlet>
        <servlet-name>Faces Servlet</servlet-name>
        <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
    </servlet>
    <servlet-mapping>
        <servlet-name>Faces Servlet</servlet-name>
        <url-pattern>*.xhtml</url-pattern>
    </servlet-mapping>
    <!--specified in minutes-->
    <session-config>
        <session-timeout>30</session-timeout>
    </session-config>
</web-app>

And our faces-config.xml

<?xml version="1.0" encoding="UTF-8"?>
<faces-config xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-facesconfig_1_2.xsd" version="1.2">
<application>
    <locale-config>
        <default-locale>en</default-locale>
        <supported-locale>en</supported-locale>
    </locale-config>
    <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>
    <resource-bundle>
        <base-name>XX.XXXX.XXX.prs.web.messages.messages</base-name>
        <var>msgs</var>
    </resource-bundle>
    <resource-bundle>
        <base-name>XX.XXXX.XXX.prs.web.messages.validation</base-name>
        <var>val</var>
    </resource-bundle>
</application>
</faces-config>

A couple of notes

You do not need to declare org.jboss.seam.el.SeamELResolver in faces-config.xml because it is bundled with jboss-seam.jar.

Now, what is missed ?

We need to call our debug page (Do not forget starting up JBoss and deploy your ear application)

http://127.0.0.1:8080/pureCharger/debug.xhtml

And again

If you really want to avoid a lot of headache, use seam-gem

UPDATE

Is your ear project AS SHOWN ABOVE ??? MAKE SURE your war lib folder DOES NOT CONTAIN any jboss-seam.jar file. You said

I opened the .ear and the following jboss jars are in:

jboss-seam-debug-2.2.0.GA.jar (wrong) It must be placed inside war file WEB-INF/lib folder
jboss-el-1.0_02.CR4.jar (wrong) It must be placed inside ear file lib folder
jboss-seam-2.2.0.GA.jar (right) But it must be declared in ear META-INF/application.xml file

Here you can see a nice Tutorial about EJB 2.0 and 3.0 provided by me

Helpful links about Seam Maven Integration

http://www.seamframework.org/Community/MavenWithSeam

http://www.seamframework.org/Documentation/SeamWithMavenOverview

http://www.seamframework.org/Community/SeamInActionChapter2345And6Mavenized

http://www.seamframework.org/Community/MavenSeamArchetype

regards,

Arthur Ronald F D Garcia 2010-03-17 03:48:52

I am sorry, but I don't understand how I may have "installed" two SeamPhaseListener. The way I see it, a SeamPhaseListener is installed when you make the appropriate entry in the web.xml file, which I have. Where is the second instance installed?

Markos Fragkakis 2010-03-17 09:06:44

If you are suggesting that the fact that I have two projects is relevant, I have opened the final .ear and only one jboss-seam-debug.jar ends up in it. That is in case the presence of a jboss-seam-debug.jar automagically registers a SeamPhaseListener.

Markos Fragkakis 2010-03-17 09:08:02

Please take another look, updated with current configuration and status.

Markos Fragkakis 2010-03-18 10:50:09

@Arthur ... Sorry, this didn't work either... I am still getting the same exception. I also tried variations of the solution by excluding maven dependencies, but no luck. For some reason the SeamPhaseListener is still "registered" twice.

Markos Fragkakis 2010-03-19 13:47:25

Anyway, thanks for getting into all this trouble. I will still not mark this answer as _the_ correct, but will upvote other comments you have made in other posts. Cheers!

Markos Fragkakis 2010-03-19 13:47:57

That would be ideal. However, I am trying to bring Seam to an existing project, with its own structure. Although Seam works (or at least that's what it looks like), I have not managed to show the debug page. Which would be _very_ helpful at this point..

Markos Fragkakis 2010-03-19 17:01:12

@Markos Fragkakis Updated. I hope it can be useful to you

Arthur Ronald F D Garcia 2010-03-20 13:22:42

Answer 2

A:

What do you mean debug page? Do you mean the default Seam debug page? Which is debug.seam? Typically http://localhost:8080/debug.seam ?

It is not enough to put in web.xml. You also need to put in components.xml

<core:init debug="true" jndi-pattern="myApp/#{ejbName}/local"/>

You also need to make sure that the jboss-seam-debug.jar is in classpath. Seam's interceptor should pick this up automatically.

If you are using Facelets, to get its debug page you will need to put this in web.xml

<context-param>
  <param-name>facelets.DEVELOPMENT</param-name>
  <param-value>true</param-value>
</context-param>

The tip from Arthur about always using seam-gen to generate your project is a very good idea.

I also see that Arthur is saying you need to make sure jboss-seam-debug.jar shouldnt be in your lib in your war. That is not necessarily correct. I have mine in

myapp.war/WEB-INF/lib/jboss-seam-debug.jar

Shervin 2010-03-22 08:39:15

@Shervin No, no. I said jboss-seam-debug.jar must be placed inside war file WEB-INF **lib** folder. As shown by yourself

Arthur Ronald F D Garcia 2010-03-22 18:55:43

@Arthur Ronald F D Garcia ah ok. Sorry, my bad then

Shervin 2010-03-23 08:35:35

Answer 3

+1 A:

The reason Seam the debug page did not appear is unbelievable (for me).

I packaged my application with Apache Maven. Traditionally, the filenames of jar files managed by maven also contain the version number. The jar for Seam is jboss-seam -2.2.0.GA.jar. Because Seam is an EJB module in the application, I declared its dependency as such. And indeed, the EAR contained it as an EJB module (located in the root of the EAR) and also declared it in the META-INF/application.xml.

I don't know if the specification defines naming restrictions for the EJB modules in an EAR, but the version part of the filename was what WebLogic did not like (if modified, the war works fine on JBoss).

I changed the setting in the maven-ear-plugin from this:

<ejbModule>
    <groupId>org.jboss.seam</groupId>
    <artifactId>jboss-seam</artifactId>
</ejbModule>

to this:

<ejbModule>
    <groupId>org.jboss.seam</groupId>
    <artifactId>jboss-seam</artifactId>
    <bundleFileName>jboss-seam.jar</bundleFileName>
</ejbModule>

And now I can see BOTH my application AND the Debug page.

Markos Fragkakis 2010-03-26 17:55:46

@Markos Fragkakis Congratulations (+1). Now, you can see why i said: if you want to avoid a lot of headache, use Seam-gem. Besides that, Seam bundled examples can give you a good insight about Seam. Do not forget mark your own answer as accepted two days from now.

Arthur Ronald F D Garcia 2010-03-26 18:39:27

ansaurus

tags:

views:

answers:

Jboss Seam: Enabling Debug page on WebLogic 10.3.2 (11g)

related questions