[Installation, Configuration & Deployment] - jboss-head build failure
by hindog
Hi, I checked out jboss-head twice today (once around 2pm, once around 5pm), both build attempts failed with the following output... anyone else having this same failure?
Aaron
compile-rmi:
[rmic] RMI Compiling 1 class to /tmp/jboss/jboss-head/management/output/classes
compile-etc:
[mkdir] Created dir: /tmp/jboss/jboss-head/management/output/etc
[copy] Copying 2 files to /tmp/jboss/jboss-head/management/output/etc
compile:
[mkdir] Created dir: /tmp/jboss/jboss-head/management/output/lib
[jar] Building jar: /tmp/jboss/jboss-head/management/output/lib/jboss-jsr77.jar
[jar] Building jar: /tmp/jboss/jboss-head/management/output/lib/jboss-jsr77-client.jar
[jar] Building jar: /tmp/jboss/jboss-head/management/output/lib/jboss-management.jar
[jar] Building jar: /tmp/jboss/jboss-head/management/output/lib/ejb-management.jar
[touch] Creating /tmp/jboss/jboss-head/management/output/build-marker
most:
==
== Finished with 'most' in module 'management'.
======================================================================
_module-management-most:
_module-management-most:
[copy] Copying 2 files to /tmp/jboss/jboss-head/build/output/jboss-5.0.0.Beta/server/all/lib
[copy] Copying 1 file to /tmp/jboss/jboss-head/build/output/jboss-5.0.0.Beta/docs/examples/jmx
[copy] Copying 1 file to /tmp/jboss/jboss-head/build/output/jboss-5.0.0.Beta/client
======================================================================
== Executing 'most' in module 'aspects'...
==
_buildmagic:init:
Trying to override old definition of task libraryset
Trying to override old definition of task execmodules
Trying to override old definition of task resolveproperties
Trying to override old definition of task resolver
Trying to override old definition of task require
Trying to override old definition of task _dump
Trying to override old definition of task _puke
Trying to override old definition of task moduleinit
Trying to override old definition of task moduleconfig
Trying to override old definition of task modulelibrary
Trying to override old definition of task projectinfo
Trying to override old definition of task library
Trying to override old definition of task Ant
Trying to override old definition of task moduleinfo
Trying to override old definition of task projecthelp
Trying to override old definition of task propertyfilter
Trying to override old definition of task call
Trying to override old definition of task property
configure:
Overriding previous definition of reference to xdoclet.task.classpath
init:
_buildmagic:build-bypass-checker:
_buildmagic:build-bypass-notice:
_buildmagic:build-bypass-check:
output:
_buildmagic:init:
init:
_default:compile-etc:
[mkdir] Created dir: /tmp/jboss/jboss-head/aspects/output/etc
[copy] Copying 3 files to /tmp/jboss/jboss-head/aspects/output/etc
_default:compile-resources:
[mkdir] Created dir: /tmp/jboss/jboss-head/aspects/output/resources
[copy] Copying 30 files to /tmp/jboss/jboss-head/aspects/output/resources
[copy] Copied 25 empty directories to 8 empty directories under /tmp/jboss/jboss-head/aspects/output/resources
compile-classes:
[mkdir] Created dir: /tmp/jboss/jboss-head/aspects/output/classes
[javac] Compiling 187 source files to /tmp/jboss/jboss-head/aspects/output/classes
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aop/deployment/JBossClassPool.java:70: toClass(javassist.CtClass,java.lang.ClassLoader) in org.jboss.aop.deployment.JBossClassPool cannot override toClass(javassist.CtClass,java.lang.ClassLoader) in javassist.ClassPool; overridden method is final
public Class toClass(CtClass cc, ClassLoader loader)
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aop/deployment/JBossClassPool32.java:71: toClass(javassist.CtClass,java.lang.ClassLoader) in org.jboss.aop.deployment.JBossClassPool32 cannot override toClass(javassist.CtClass,java.lang.ClassLoader) in javassist.ClassPool; overridden method is final
public Class toClass(CtClass cc, ClassLoader loader)
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aspects/logging/CallLoggingInterceptor.java:47: warning: [deprecation] isDebugEnabled() in org.jboss.logging.Logger has been deprecated
boolean callLogging = log.isDebugEnabled();
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aspects/tx/TxInterceptor.java:177: warning: [deprecation] org.jboss.tm.TxManager in org.jboss.tm has been deprecated
org.jboss.tm.TxManager txManager = (org.jboss.tm.TxManager)tm;
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aspects/tx/TxInterceptor.java:177: warning: [deprecation] org.jboss.tm.TxManager in org.jboss.tm has been deprecated
org.jboss.tm.TxManager txManager = (org.jboss.tm.TxManager)tm;
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aspects/tx/TxInterceptor.java:180: warning: [deprecation] org.jboss.tm.TxManager in org.jboss.tm has been deprecated
if (tm instanceof org.jboss.tm.TxManager)
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aspects/tx/TxInterceptor.java:182: warning: [deprecation] org.jboss.tm.TxManager in org.jboss.tm has been deprecated
txManager = (org.jboss.tm.TxManager)tm;
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aspects/tx/TxInterceptor.java:244: warning: [deprecation] org.jboss.tm.TxManager in org.jboss.tm has been deprecated
org.jboss.tm.TxManager txManager = (org.jboss.tm.TxManager)tm;
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aspects/tx/TxInterceptor.java:244: warning: [deprecation] org.jboss.tm.TxManager in org.jboss.tm has been deprecated
org.jboss.tm.TxManager txManager = (org.jboss.tm.TxManager)tm;
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aspects/tx/TxInterceptor.java:247: warning: [deprecation] org.jboss.tm.TxManager in org.jboss.tm has been deprecated
if (tm instanceof org.jboss.tm.TxManager)
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aspects/tx/TxInterceptor.java:249: warning: [deprecation] org.jboss.tm.TxManager in org.jboss.tm has been deprecated
txManager = (org.jboss.tm.TxManager)tm;
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aspects/versioned/DistributedSynchronizationManager.java:72: warning: [deprecation] callMethodOnCluster(java.lang.String,java.lang.String,java.lang.Object[],boolean) in org.jboss.ha.framework.interfaces.HAPartition has been deprecated
ArrayList rsp = partition.callMethodOnCluster(domainName, "getCurrentState", args, true);
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aspects/versioned/DistributedSynchronizationManager.java:133: warning: [deprecation] callMethodOnCluster(java.lang.String,java.lang.String,java.lang.Object[],boolean) in org.jboss.ha.framework.interfaces.HAPartition has been deprecated
checkResponses(partition.callMethodOnCluster(domainName, "addNewObjects", args, true));
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aspects/versioned/DistributedSynchronizationManager.java:148: warning: [deprecation] callMethodOnCluster(java.lang.String,java.lang.String,java.lang.Object[],boolean) in org.jboss.ha.framework.interfaces.HAPartition has been deprecated
checkResponses(partition.callMethodOnCluster(domainName, "updateObjects", args, true));
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aspects/versioned/DistributedSynchronizationManager.java:163: warning: [deprecation] callMethodOnCluster(java.lang.String,java.lang.String,java.lang.Object[],boolean) in org.jboss.ha.framework.interfaces.HAPartition has been deprecated
checkResponses(partition.callMethodOnCluster(domainName, "acquireLocks", args, true));
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aspects/versioned/DistributedSynchronizationManager.java:170: warning: [deprecation] callMethodOnCluster(java.lang.String,java.lang.String,java.lang.Object[],boolean) in org.jboss.ha.framework.interfaces.HAPartition has been deprecated
partition.callMethodOnCluster(domainName, "releaseHeldLocks", args, true);
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aspects/versioned/DistributedTxCache.java:145: warning: [deprecation] callMethodOnCluster(java.lang.String,java.lang.String,java.lang.Object[],boolean) in org.jboss.ha.framework.interfaces.HAPartition has been deprecated
List rsp = partition.callMethodOnCluster(cacheName, "getCurrentState", args, true);
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aspects/versioned/DistributedTxCache.java:173: warning: [deprecation] callMethodOnCluster(java.lang.String,java.lang.String,java.lang.Object[],boolean) in org.jboss.ha.framework.interfaces.HAPartition has been deprecated
partition.callMethodOnCluster(cacheName, "_insert", args, false);
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aspects/versioned/DistributedTxCache.java:192: warning: [deprecation] callMethodOnCluster(java.lang.String,java.lang.String,java.lang.Object[],boolean) in org.jboss.ha.framework.interfaces.HAPartition has been deprecated
partition.callMethodOnCluster(cacheName, "_remove", args, false);
^
/tmp/jboss/jboss-head/aspects/src/main/org/jboss/aspects/versioned/DistributedTxCache.java:211: warning: [deprecation] callMethodOnCluster(java.lang.String,java.lang.String,java.lang.Object[],boolean) in org.jboss.ha.framework.interfaces.HAPartition has been deprecated
partition.callMethodOnCluster(cacheName, "_flush", args, false);
^
2 errors
18 warnings
BUILD FAILED
/tmp/jboss/jboss-head/aspects/build.xml:192: Compile failed; see the compiler error output for details.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963699#3963699
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963699
19 years, 9 months
[JBoss Seam] - LoginAction - Understanding Second Part?
by connerjohn
I'm trying to understand the booking LoginAction
| //$Id: LoggedInInterceptor.java,v 1.12 2006/07/26 23:19:55 gavin Exp $
| package org.jboss.seam.example.booking;
|
| import java.lang.reflect.Method;
|
| import javax.interceptor.AroundInvoke;
| import javax.interceptor.InvocationContext;
| import javax.faces.event.PhaseId;
|
| import org.jboss.seam.annotations.Interceptor;
| import org.jboss.seam.contexts.Contexts;
| import org.jboss.seam.contexts.Lifecycle;
| import org.jboss.seam.interceptors.BijectionInterceptor;
| import org.jboss.seam.interceptors.BusinessProcessInterceptor;
| import org.jboss.seam.interceptors.ConversationInterceptor;
| import org.jboss.seam.interceptors.RemoveInterceptor;
| import org.jboss.seam.interceptors.ValidationInterceptor;
|
| @Interceptor(around={BijectionInterceptor.class, ValidationInterceptor.class,
| ConversationInterceptor.class, BusinessProcessInterceptor.class},
| within=RemoveInterceptor.class)
| public class LoggedInInterceptor
| {
|
| @AroundInvoke
| public Object checkLoggedIn(InvocationContext invocation) throws Exception
| {
| boolean isLoggedIn = Contexts.getSessionContext().get("loggedIn")!=null;
| if ( Lifecycle.getPhaseId()==PhaseId.INVOKE_APPLICATION )
| {
| if (isLoggedIn)
| {
| return invocation.proceed();
| }
| else
| {
| return "login";
| }
| }
| else
| {
| if ( isLoggedIn )
| {
| return invocation.proceed();
| }
| else
| {
| Method method = invocation.getMethod();
| if ( method.getReturnType().equals(void.class) )
| {
| return null;
| }
| else
| {
| return method.invoke( invocation.getTarget(), invocation.getParameters() );
| }
| }
| }
| }
|
| }
|
Wondering two things from this code:
1. what do we get for checking the Lifecycle.PhaseId
2. what is the purpose of calling method.invoke(....) instead of returing a string outcome (aka, "login") like is done if we are in the INVOKE_APPLICATION phase.
Thanks,
--jc
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963696#3963696
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963696
19 years, 9 months
[EJB 3.0] - Re: Using Differents jars
by jmarcos_se
Hi,
Thanks for the reply....
Let me try to explain what I want to say....
First, I created a interface.war for the web Interface and a ejb.jar with the entities and session beans within. Then, I packed those two in a .ear file, ok ?
This worked smoothly.
But now I want to separate the sessions and the entities in two different .jar files. For instance, a entity.jar and a session.jar. So my .ear file would look like this
<display-name>ProjetoJM</display-name>
Entity.jar
Session.jar
<web-uri>InterfaceJSF.war</web-uri>
<context-root>Teste</context-root>
Doing this, I'm getting exceptions just like tho one I told before.....
Sorry about my english, but I'm a Brazillian guy and I'm still learning the language....
Thanks....
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963695#3963695
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963695
19 years, 9 months
[JBoss jBPM] - Re: jBPM BPEL change DB - HowTo?
by fwshk
Hi Claus,
Thanks for trying my previous post. May be my previous post is not well organized. However, I make a updated version for MySQL. In facts, I haven't been used MSSQL.
My Configure:
- jbpm-bpel-1.1-beta1
- jboss-4.0.4.GA
- mysql-5.0.21
- mysql-connector-java-5.0.0-beta
1. Edit JBPM_HOME\build.properties
jboss.home=D:/Try/jboss-4.0.4.GA
| jbpm.bpel.version=1.1-beta1
| jbpm.version=3.1.1
2. Edit JBPM_HOME\src\resources\jbpm-bpel.sar\hibernate.properties
hibernate.dialect=org.hibernate.dialect.MySQLInnoDBDialect
| hibernate.connection.datasource=java:/jbpmBpelDS
| hibernate.show_sql=true
| hibernate.query.substitutions=true 1, false 0
| hibernate.hbm2ddl.auto=update
Notice:
- Datasource name is case sentience
- doankhoavy talk about use "create" rather than "update"
3. Edit JBPM_HOME\src\resources\jbpm-bpel.sar\jbpm-bpel-ds.xml
<?xml version="1.0" encoding="UTF-8"?>
| <datasources>
| <local-tx-datasource>
| <jndi-name>jbpmBpelDS</jndi-name>
| <connection-url>jdbc:mysql://localhost/jbpmBpel</connection-url>
| <driver-class>com.mysql.jdbc.Driver</driver-class>
| <user-name>root</user-name>
| <password></password>
| <min-pool-size>5</min-pool-size>
| <max-pool-size>20</max-pool-size>
| <idle-timeout-minutes>0</idle-timeout-minutes>
| <track-statements />
| <metadata>
| <type-mapping>MySQL</type-mapping>
| </metadata>
| </local-tx-datasource>
| </datasources>
4. Execute command
CD JBPM_HOME
| ANT build.service.404
5. Copy JBPM_HOME\build\jbpm-bpel.sar to JBOSS\service\default\deploy
Notice:
- Place into your server instead of default server
6. Copy MySQL Driver into JBOSS\service\default\lib
Notice:
- Place into your server instead of default server
7. Before start JBoss:
- Please confirm that your MySQL is running
- The database is existing in your MySQL
- The user is able to access the database
8. Start your JBoss
Wish it is helpful for you and I am welcome for point out my mistake.
Roy
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3963693#3963693
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3963693
19 years, 9 months