[Microcontainer] - Re: migrating from ServiceMBeanSupport
by jhalliday
> You are missing the point and some code/xml
Yes, thanks Ales, the missing link seems to be the functionality in TestServiceControllerLifecycleCallback. I had assumed that declaring the annotation was sufficient, but it seems that nothing in the current AS trunk actually does anything with that annotation, or at least not at a sufficiently early stage in the lifecycle to be useful.
The code in TestServiceControllerLifecycleCallback is generic, not specific to the TransactionManager service. IMO it should be present in the AS, but I don't see it. Do I need to include it in the TS side of the integration module? To my mind the functionality should really be provided via bootstrap-beans, so in the xml for the TransactionManager I can simply reference the ServiceLifecycle bean rather than having to declare it first. Or perhaps one of the existing beans already has this functionality?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116405#4116405
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116405
18 years, 6 months
[Installation, Configuration & DEPLOYMENT] - In Linux environment , jboss-4.2.2.GA don't startup
by javang
Hi all
I am install jboss-4.2.2.GA in Linux environment ,the os env is os.version: 2.6.9-11.ELsmp and the java runtime env is java.runtime.version: 1.5.0_06-b05,but when i type ./run.sh script to start jboss Server, the server is not successful runing,I get some exception trace:
2008-01-01 16:23:37,537 ERROR [org.jboss.deployment.MainDeployer] Could not initialise deployment: file:/usr/jbossB/server/all/deploy/ejb3.deployer/
org.jboss.deployment.DeploymentException: Failed to find META-INF/jboss-service.xml for archive ejb3.deployer
2008-01-01 16:23:37,543 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Failed to deploy: org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL@350ff423{ url=file:/usr/jbossB/server/all/deploy/ejb3.deployer/, deployedLastModified=0 }
org.jboss.deployment.DeploymentException: Failed to find META-INF/jboss-service.xml for archive ejb3.deployer
2008-01-01 16:23:37,550 ERROR [org.jboss.deployment.MainDeployer] Could not initialise deployment: file:/usr/jbossB/server/all/deploy/jboss-aop-jdk50.deployer/
org.jboss.deployment.DeploymentException: Failed to find META-INF/jboss-service.xml for archive jboss-aop-jdk50.deployer
2008-01-01 16:23:37,576 ERROR [org.jboss.deployment.MainDeployer] Could not initialise deployment: file:/usr/jbossB/server/all/deploy/jboss-bean.deployer/
org.jboss.deployment.DeploymentException: Failed to find META-INF/jboss-service.xml for archive jboss-bean.deployer
2008-01-01 16:23:37,648 ERROR [org.jboss.deployment.MainDeployer] Could not initialise deployment: file:/usr/jbossB/server/all/deploy/jboss-web.deployer/
org.jboss.deployment.DeploymentException: Failed to find META-INF/jboss-service.xml for archive jboss-web.deployer
2008-01-01 16:23:37,882 ERROR [org.jboss.deployment.MainDeployer] Could not initialise deployment: file:/usr/jbossB/server/all/deploy/httpha-invoker.sar/
org.jboss.deployment.DeploymentException: Failed to find META-INF/jboss-service.xml for archive httpha-invoker.sar
2008-01-01 16:23:37,891 ERROR [org.jboss.deployment.MainDeployer] Could not initialise deployment: file:/usr/jbossB/server/all/deploy/jboss-web-cluster.sar/
org.jboss.deployment.DeploymentException: Failed to find META-INF/jboss-service.xml for archive jboss-web-cluster.sar
2008-01-01 16:23:37,915 ERROR [org.jboss.deployment.MainDeployer] Could not initialise deployment: file:/usr/jbossB/server/all/deploy/snmp-adaptor.sar/
org.jboss.deployment.DeploymentException: Failed to find META-INF/jboss-service.xml for archive snmp-adaptor.sar
Everyone can help me ,thanks a lot
Javang!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116394#4116394
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116394
18 years, 6 months
[EJB 3.0] - Re: Confused EJB3 Beginner - Ignored EJB3 Annotations
by skidvd
Aha! It turns out that my Annotations are not being ignored - I just did not understand that I can (apparently) not mix both field and method level Annotations.
My class has several read-only attributes (i.e. there is no associated set methods). In general, I would prefer to put my Annotations on the method level for code clarity sake. However, when doing this for the read-only attributes, I got an error complaining that a setter could not be found. This error message went away when I moved those Annotations to the field. Apparently though, this had the undersired effect of making all attributes 'field' access and effectively ignored all of my other method-based Annotations for columne name, length, etc.
So, my questions now are:
1. Is there an EJB3 standard way of mixing both field and method access types? I would like to have my default for method, but be able to override in exception cases such as the read-only attribute discussed above.
2. Is there a better way to handle read-only attributes that do NOT have an associated setter?
TIA!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116393#4116393
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116393
18 years, 6 months
[Javassist user questions] - javax.naming.CommunicationException JBOSS 4.0.2
by hemalmca
Hi
I am new in the JBOSS community. I am facing one problem in JMSMQ. I am working JMSMQ. In my application there are nearly 16 standalone client which connected to JBOSS server through test/Topic. And every five minute each client send a JMS message to the server and server respond back as a jms message. But in long run neary 2 to 3 days i found the following exception from the client side.
javax.naming.CommunicationException: Receive timed out [Root exception is java.n
et.SocketTimeoutException: Receive timed out]
at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:11
19)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1196)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:516)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:509)
at javax.naming.InitialContext.lookup(Unknown Source)
at com.realsoft.JMSSender.sendMessage(JMSSender.java:40)
at com.realsoft.Test1.main(Test1.java:7)
Caused by: java.net.SocketTimeoutException: Receive timed out
at java.net.PlainDatagramSocketImpl.receive(Native Method)
at java.net.DatagramSocket.receive(Unknown Source)
at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:10
89)
... 6 more
Can anybody help me in resolving this issue.
Thanks in advance
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116390#4116390
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116390
18 years, 6 months
[JBoss Seam] - Re: How to control end of conversations/state of stateful be
by pete.muir＠jboss.org
"trouby" wrote : I still don't get it, what about links that -should- start a new conversation? is it possible to combine begin/end annotations together for the same method? like ending the current conversation and starting a new one?
Yes, but you have to end the current conversation before a redirect, and start a new conversation after a redirect (you can do this from pages.xml or from annotations). I've not seen a great use case for this though.
anonymous wrote : btw, I have a seam link which invoke an method that is annotated with @Begin, invoking the same link just after the first invocation throws "begin method invoked from a long-running conversation, try using @Begin(join=true)", so what should I do in such situation?? I don't want -another- conversation to start in this case,
If you want to join the current conversation, use join=true, otherwise, design your app so the use can't be on that page when a long running conversation is in progress.
anonymous wrote : I guess I'm doing something wrong, as in seam booking example the 'setHotel' is annotated with @Begin and can be invoked many times without this exception,
Yes, because you can't be on the page which calls this method and inside a long running conversation.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116366#4116366
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116366
18 years, 6 months
[JBoss Seam] - Re: pageflow and parameters transmition
by gazadonf
Hi, and happy new year to all of you.
No i don't.
I suppressed all of myPageNamepage.xml in the WebContent and in my pages.xml i only have reference to my pagefolws.
Here is my pages.xml
| <?xml version="1.0" encoding="UTF-8"?>
| <pages xmlns="http://jboss.com/products/seam/pages"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://jboss.com/products/seam/pages http://jboss.com/products/seam/pages-2.0.xsd"
| login-view-id="/login.xhtml"
| no-conversation-view-id="/index.xhtml">
|
| <page view-id="/login.xhtml">
| <navigation from-action="#{identity.login}">
| <rule if="#{identity.loggedIn}">
| <redirect view-id="/Activity.xhtml"/>
| </rule>
| </navigation>
| </page>
| <page view-id="/Activity.xhtml" login-required="true">
| <begin-conversation join="true" pageflow="monPageflow"/>
| </page>
|
| <page view-id="*">
| <navigation from-action="#{identity.logout}">
| <end-conversation/>
| <redirect view-id="/login.xhtml"></redirect>
| </navigation>
| </page>
|
|
| <exception class="org.jboss.seam.framework.EntityNotFoundException">
| <redirect view-id="/error.xhtml">
| <message>Not found</message>
| </redirect>
| </exception>
|
| <exception class="javax.persistence.EntityNotFoundException">
| <redirect view-id="/error.xhtml">
| <message>Not found</message>
| </redirect>
| </exception>
|
| <exception class="javax.persistence.OptimisticLockException">
| <end-conversation/>
| <redirect view-id="/error.xhtml">
| <message>Another user changed the same data, please try again</message>
| </redirect>
| </exception>
|
| <exception class="org.jboss.seam.security.AuthorizationException">
| <redirect view-id="/error.xhtml">
| <message>You don't have permission to do this</message>
| </redirect>
| </exception>
|
| <exception class="org.jboss.seam.security.NotLoggedInException">
| <redirect view-id="/login.xhtml">
| <message>Please log in first</message>
| </redirect>
| </exception>
|
| <exception class="javax.faces.application.ViewExpiredException">
| <redirect view-id="/error.xhtml">
| <message>Your session has timed out, please try again</message>
| </redirect>
| </exception>
|
| <exception class="javax.faces.application.IllegalNavigationException">
| <redirect view-id="/error.xhtml">
| <message>Your session has timed out, please try again</message>
| </redirect>
| </exception>
|
| <exception>
| <redirect view-id="/error.xhtml">
| <message>Unexpected error, please try again</message>
| </redirect>
| </exception>
|
|
|
| </pages>
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116359#4116359
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116359
18 years, 6 months
[EJB 3.0] - Uploading multiple files from Client to server
by kaviarasu
Hi
i want to upload all files from a folder in Client to Server
Im using jsf as a front ent
When if i test it in client side with Server in same machine and checks for the folder and upload all files it working
But when the server is in remote palce how to upload all files from client folder to the server
I pasted my sample coding . I browse one file from the folder and using that i find the path to the folder and upload all fles from the folder
File f=new File(vname1);
File f1=new File(f.getParent());
int i=0;
if(f1.isDirectory())
{
for(File a:f1.listFiles())
{
FileInputStream fr = new FileInputStream(a); FileOutputStream fw = new FileOutputStream(new File(location1,a.getName()));
while((i=fr.read())!=-1)
{
fw.write(i);
}
fw.close();
fr.close();
}
the above code works when the server is in same machine
when the server is in remote place it not working
Thanks in advance
happy new year
Regards
Kaviarasu
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116355#4116355
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116355
18 years, 6 months
[Beginners Corner] - Migrating to JBoss 4.2.2.GA
by puzz
Hi,
Before migrating we had a lot of
WARN [TxConnectionManager] Prepare called on a local tx. Use of local transactions on
a jta transaction with more than one branch may result in inconsistent data in some cases of failure
in our jboss log files.
Since we migrated it seems this warning instead generates an error.
I've also seen in other discussions that this warning now (in JBoss 4.2) generates errors.
I'm not really sure why we're getting the WARN/error in the first place.
An example of when the WARN/error is thrown:
A stateless EJB 3 session bean, where I use two other stateless beans to retrieve data from db. I try to retrieve the data from both stateless beans in the same method. And, voila, I get an error in JBoss 4.2 when retrieving data from the second stateless bean. I remember that the above mentioned WARN was generated when the method was done when we used an earlier version of JBoss.
Anyone has an idea what I should do to correct this?
/Best regards, Håkan Jacobsson - System developer in Sweden
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116354#4116354
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116354
18 years, 6 months
[JBoss Seam] - Richfaces with Maven and Tomcat 6
by rmcalderero
Hello,
Is there any working 'mavenized' seam application with richfaces as one of its dependencies?
I've tried different dependencies in the pom based on some non official blogs, but none worked. Maybe some can provide one.
Our app was based on the jboss-seam-jpa example and is deployed under tomcat6. The app runs ok when the jars are included manually.
pom.xml
| <?xml version="1.0" encoding="UTF-8"?>
| <project xmlns="http://maven.apache.org/POM/4.0.0"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
|
| <modelVersion>4.0.0</modelVersion>
| <groupId>org.fundacionctic.seam</groupId>
| <artifactId>monitor</artifactId>
| <packaging>war</packaging>
| <name>monitor</name>
| <version>0.1</version>
| <url>http://fundacionctic.org</url>
|
| <!--
| <pluginRepositories>
| <pluginRepository>
| <id>apache.snapshots</id>
| <url>
| http://people.apache.org/repo/m2-snapshot-repository/
| </url>
| </pluginRepository>
| </pluginRepositories>
| -->
|
| <build>
| <finalName>monitor</finalName>
| <plugins>
| <plugin>
| <artifactId>maven-war-plugin</artifactId>
| <configuration>
| <warSourceDirectory>WebContent</warSourceDirectory>
| </configuration>
| </plugin>
|
| <plugin>
| <groupId>org.apache.maven.plugins</groupId>
| <artifactId>maven-compiler-plugin</artifactId>
| <configuration>
| <source>1.5</source>
| <target>1.5</target>
| <encoding>utf8</encoding>
| </configuration>
| </plugin>
|
| </plugins>
| </build>
|
|
| <repositories>
| <repository>
| <id>jboss.org</id>
| <name>jboss.org</name>
| <url>http://repository.jboss.com/maven2</url>
| </repository>
| </repositories>
|
|
| <dependencies>
|
| <dependency>
| <groupId>junit</groupId>
| <artifactId>junit</artifactId>
| <version>3.8.1</version>
| <scope>test</scope>
| </dependency>
|
| <!-- TestNG -->
| <dependency>
| <groupId>org.testng</groupId>
| <artifactId>testng</artifactId>
| <version>5.0</version>
| <classifier>jdk15</classifier>
| <scope>test</scope>
| </dependency>
|
| <dependency>
| <groupId>javax.servlet</groupId>
| <artifactId>servlet-api</artifactId>
| <version>2.5</version>
| <scope>test</scope>
| </dependency>
|
| <dependency>
| <groupId>javax.el</groupId>
| <artifactId>el-api</artifactId>
| <version>1.0</version>
| <scope>test</scope>
| </dependency>
|
| <!-- Seam -->
| <dependency>
| <groupId>org.jboss.seam</groupId>
| <artifactId>jboss-seam</artifactId>
| <version>2.0.0.GA</version>
| <exclusions>
| <exclusion>
| <artifactId>el-api</artifactId>
| <groupId>javax.el</groupId>
| </exclusion>
| </exclusions>
| </dependency>
|
| <dependency>
| <groupId>org.jboss.seam</groupId>
| <artifactId>jboss-seam-ui</artifactId>
| <version>2.0.0.GA</version>
| <exclusions>
| <exclusion>
| <artifactId>el-api</artifactId>
| <groupId>javax.el</groupId>
| </exclusion>
| </exclusions>
| </dependency>
|
| <dependency>
| <groupId>org.jboss.seam</groupId>
| <artifactId>jboss-seam-debug</artifactId>
| <version>2.0.0.GA</version>
| <exclusions>
| <exclusion>
| <artifactId>servlet-api</artifactId>
| <groupId>javax.servlet</groupId>
| </exclusion>
| <exclusion>
| <artifactId>el-api</artifactId>
| <groupId>javax.el</groupId>
| </exclusion>
| </exclusions>
| </dependency>
|
| <dependency>
| <groupId>org.jboss.seam</groupId>
| <artifactId>jboss-el</artifactId>
| <version>2.0.0.GA</version>
| <exclusions>
| <exclusion>
| <artifactId>el-api</artifactId>
| <groupId>javax.el</groupId>
| </exclusion>
| </exclusions>
| </dependency>
|
| <dependency>
| <groupId>org.jboss.seam</groupId>
| <artifactId>jboss-seam-mail</artifactId>
| <version>2.0.0.GA</version>
| </dependency>
|
| <!-- hibernate -->
| <dependency>
| <groupId>org.hibernate</groupId>
| <artifactId>hibernate-validator</artifactId>
| <version>3.0.0.ga</version>
| </dependency>
|
| <dependency>
| <groupId>org.hibernate</groupId>
| <artifactId>hibernate-annotations</artifactId>
| <version>3.3.0.ga</version>
| </dependency>
|
| <dependency>
| <groupId>org.hibernate</groupId>
| <artifactId>hibernate-entitymanager</artifactId>
| <version>3.3.1.ga</version>
| </dependency>
|
| <!-- spring ldap y ldap booster pack -->
| <dependency>
| <groupId>org.springframework.ldap</groupId>
| <artifactId>spring-ldap</artifactId>
| <version>1.2</version>
| </dependency>
|
| <dependency>
| <groupId>com.sun</groupId>
| <artifactId>ldapbp</artifactId>
| <version>1.0</version>
| </dependency>
|
| <!-- log4j -->
| <dependency>
| <groupId>log4j</groupId>
| <artifactId>log4j</artifactId>
| <version>1.2.14</version>
| </dependency>
|
| <!-- mysql -->
| <dependency>
| <groupId>mysql</groupId>
| <artifactId>mysql-connector-java</artifactId>
| <version>5.0.4</version>
| </dependency>
|
| <!-- mail -->
| <dependency>
| <groupId>javax.mail</groupId>
| <artifactId>mail</artifactId>
| <version>1.4</version>
| </dependency>
|
| <!-- faces -->
|
| <dependency>
| <groupId>com.sun.facelets</groupId>
| <artifactId>jsf-facelets</artifactId>
| <version>1.1.14</version>
| </dependency>
|
| <dependency>
| <groupId>javax.servlet</groupId>
| <artifactId>jstl</artifactId>
| <version>1.1.2</version>
| </dependency>
|
| <!-- MyFaces
| <dependency>
| <groupId>org.apache.myfaces.core</groupId>
| <artifactId>myfaces-api</artifactId>
| <version>1.2.0</version>
| </dependency>
|
| <dependency>
| <groupId>org.apache.myfaces.core</groupId>
| <artifactId>myfaces-impl</artifactId>
| <version>1.2.0</version>
| </dependency>
| -->
|
| <!-- RichFaces -->
| <dependency>
| <groupId>org.richfaces</groupId>
| <artifactId>richfaces</artifactId>
| <version>3.0.0</version>
| </dependency>
|
| <!--
| <dependency>
| <groupId>org.richfaces</groupId>
| <artifactId>framework</artifactId>
| <version>3.1.0</version>
| </dependency>
| -->
| <!--
| <dependency>
| <groupId>org.richfaces.framework</groupId>
| <artifactId>richfaces-api</artifactId>
| <version>3.1.3.GA</version>
| </dependency>
| <dependency>
| <groupId>org.richfaces.framework</groupId>
| <artifactId>richfaces-impl</artifactId>
| <version>3.1.3.GA</version>
| <exclusions>
| <exclusion>
| <groupId>javax.faces</groupId>
| <artifactId>jsf-api</artifactId>
| </exclusion>
| <exclusion>
| <groupId>javax.faces</groupId>
| <artifactId>jsf-impl</artifactId>
| </exclusion>
| </exclusions>
| </dependency>
| <dependency>
| <groupId>org.richfaces.ui</groupId>
| <artifactId>richfaces-ui</artifactId>
| <version>3.1.3.GA</version>
| <exclusions>
| <exclusion>
| <groupId>javax.faces</groupId>
| <artifactId>jsf-api</artifactId>
| </exclusion>
| <exclusion>
| <groupId>javax.faces</groupId>
| <artifactId>jsf-impl</artifactId>
| </exclusion>
| </exclusions>
| </dependency>
| -->
|
| <!-- Tomahawk -->
| <dependency>
| <groupId>org.apache.myfaces.tomahawk</groupId>
| <artifactId>tomahawk-sandbox</artifactId>
| <version>1.1.6</version>
| </dependency>
|
| <!-- tomahawk-facelets -->
| <dependency>
| <groupId>com.google.code.tomahawk</groupId>
| <artifactId>tomahawk-facelets</artifactId>
| <version>1.1.6</version>
| </dependency>
|
|
| <!-- JSF RI
| <dependency>
| <groupId>javax.faces</groupId>
| <artifactId>jsf-api</artifactId>
| <version>1.2_04-p02</version>
| </dependency>
|
|
| <dependency>
| <groupId>javax.faces</groupId>
| <artifactId>jsf-impl</artifactId>
| <version>1.2_04-p02</version>
| </dependency>
| -->
|
| <!-- RichFaces
| <dependency>
| <groupId>org.richfaces.framework</groupId>
| <artifactId>richfaces-impl</artifactId>
| <version>3.1.2.GA</version>
| </dependency>
|
| <dependency>
| <groupId>org.richfaces.framework</groupId>
| <artifactId>richfaces-api</artifactId>
| <version>3.1.2.GA</version>
| </dependency>
|
| <dependency>
| <groupId>org.richfaces.ui</groupId>
| <artifactId>richfaces-ui</artifactId>
| <version>3.1.2.GA</version>
| </dependency>
| -->
|
| </dependencies>
| </project>
|
exception in tomcat
| 02-ene-2008 11:58:41 org.apache.catalina.core.StandardContext listenerStart
| GRAVE: Error configurando escuchador de aplicación de clase com.sun.faces.config.ConfigureListener
| java.lang.NoClassDefFoundError: javax/faces/FacesException
| at java.lang.Class.getDeclaredConstructors0(Native Method)
| at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
| at java.lang.Class.getConstructor0(Unknown Source)
| at java.lang.Class.newInstance0(Unknown Source)
| at java.lang.Class.newInstance(Unknown Source)
| at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3774)
| at org.apache.catalina.core.StandardContext.start(StandardContext.java:4337)
| at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
| at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
| at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
| at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920)
| at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883)
| at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492)
| at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
| at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
| at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
| at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
| at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
| at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
| at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
| at org.apache.catalina.core.StandardService.start(StandardService.java:516)
| at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
| at org.apache.catalina.startup.Catalina.start(Catalina.java:566)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
| at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
| 02-ene-2008 11:58:41 org.apache.catalina.core.StandardContext listenerStart
| GRAVE: Error configurando escuchador de aplicación de clase com.sun.faces.application.WebappLifecycleListener
| java.lang.NoClassDefFoundError: javax/faces/FacesException
| at com.sun.faces.application.WebappLifecycleListener.<clinit>(WebappLifecycleListener.java:67)
| at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
| at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
| at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
| at java.lang.reflect.Constructor.newInstance(Unknown Source)
| at java.lang.Class.newInstance0(Unknown Source)
| at java.lang.Class.newInstance(Unknown Source)
| at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3774)
| at org.apache.catalina.core.StandardContext.start(StandardContext.java:4337)
| at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
| at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
| at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
| at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:920)
| at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883)
| at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:492)
| at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138)
| at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
| at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
| at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
| at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
| at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
| at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
| at org.apache.catalina.core.StandardService.start(StandardService.java:516)
| at org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
| at org.apache.catalina.startup.Catalina.start(Catalina.java:566)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
| at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
| 02-ene-2008 11:58:41 org.apache.catalina.core.StandardContext listenerStart
| GRAVE: Se ha saltado la instalación de escuchadores de aplicación debido a error(es) previo(s)
| 02-ene-2008 11:59:08 org.apache.catalina.core.StandardContext listenerStart
| GRAVE: Excepción enviando evento inicializado de contexto a instancia de escuchador de clase com.sun.faces.config.ConfigureListener
| javax.faces.FacesException: java.lang.ClassNotFoundException: [Ljava.lang.String;
| at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:354)
| at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3830)
| at org.apache.catalina.core.StandardContext.start(StandardContext.java:4337)
| at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
| at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
| at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525)
| at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825)
| at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714)
| at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490)
| at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1206)
| at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:293)
| at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
| at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1337)
| at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601)
| at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610)
| at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590)
| at java.lang.Thread.run(Unknown Source)
| Caused by: java.lang.ClassNotFoundException: [Ljava.lang.String;
| at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1358)
| at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1204)
| at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:635)
| at com.sun.faces.config.ConfigureListener.configure(ConfigureListener.java:422)
| at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:348)
| ... 16 more
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116353#4116353
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116353
18 years, 6 months
[JBoss Portal] - Should we use Portlets+EJB3 for componentized enterprise app
by avogt_sundn
We consider a design of uniform building blocks for an enterprise application portal, were the building blocks are EAR files that deliver UI as well as busines logic in one deployment. I'm interested in your opinion on this. Let me explain that:
- we want to build up on the best practices and open standards
- building blocks (one EAR) group business use cases
- the portal presents the available use cases to the user as it chooses from the deployed use cases (that calls for some kind of registry, hopefully EJB jndi is sufficient)
- we create portal pages for each instance of a use case (that gives the user something like tabbed browsing: one tab for each use case),
- on that page there are several portlets from different EARs (!) that are grouped and controlled under guidance of one orchestrating building block (an EJB), while the portlet implementation remains within the boundaries of its EAR
- a use case has a page flow
- we have a portlet that has navigation menu for the page flow
- we have on the use case portal page a working region where at one time there will only be one portlet displayed
- the page flow is beyond JSF page flow: it can render various portlets on the working area. When the portlet (the jsf app within, to be exactly) finishes its user interaction, the page flow takes over and renders the next portlet in flow to the working area
Why the efforts? We want to have those building blocks to be highly reusable, especially the UI must be reusable "as is"; the cohesion within the building block is high since it s coupled with its UI as well as with its database tier.
What i need is some kind of injection of portlets within other portlets (or at least their controllers), so that one controller calls another when he likes to give him preset values and when he wants to extract return values from the portlets.
In the Seam group I read warnings not to declare dependencies on EJBs from foreign ear files because of class loader issues, and I read that it was not possible to biject EJBs from foreign ears.
So I was thinking about leveraging the Seam concepts to the Portal?
I could imagine that portal page to be the visualization of something like a new SEAM context.
Any opinions to that?
Armin
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116345#4116345
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116345
18 years, 6 months
[JBoss Seam] - Back
by Marx3
I have a form to submit picture. This form can be called from many different other forms, because I can attach pictures to many different objects. Hovewer I would like to have "Back" button acting like BackButton in browser. So I should always back to the form which has called my form. How should it be done in Seam?
Let's face simple example: FormObjectA and FormObjectB calls FormPicture.
How to define "Back" button so it back to caller?
I've tried:
1)many buttons with "rendered" attribute one for each caller (works but tedious) connected with many "rule if-outcome" in XML
2)render button with binding method returning proper action (has problems when binding takes place in stateful bean)
3)"navigation from-action="back" and rule-if connected with some parameter set in bean - working, but there are problems with passing parameter
4) What I think about but don't know how to make properly is to program javascript:go(-1) and have faith in proper behaviour of backButton covered by Seam.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4116340#4116340
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4116340
18 years, 6 months