July 2007 - jboss-user - Jboss List Archives

[JBoss Seam] - Re: Breaking Pages.xml into multiple files

by norman.richards＠jboss.com

| <navigation:pages> | <navigation:resources> | <value>/WEB-INF/conversations.pages.xml</value> | <value>/WEB-INF/common.pages.xml</value> | <value>/WEB-INF/inventory.pages.xml</value> | <value>/WEB-INF/contacts.pages.xml</value> | <value>/WEB-INF/admin.pages.xml</value> | </navigation:resources> | </navigation:pages> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068324#4068324 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068324

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: How to prevent double submit

by fhh

Or you can use this javascript hack: | <script> | function disableButtons(formular) | { | | for (var iter = 0; iter < formular.elements.length; iter++) { | | if (formular.elements[iter].type == "submit" | || formular.elements[iter].type == "button" | || formular.elements[iter].type == "reset") | { | | formular.elements[iter].disabled = true; | | } | } | } | <script> | <h:form onsubmit="disableButtonsAfterSubmit(this);">...</h:form> | Regards Felix View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068323#4068323 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068323

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: login & logout options

by gavin.king＠jboss.com

There are some events that occur on login/out that you can write an @Observer method for. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068321#4068321 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068321

18 years, 9 months

1
0
0 / 0

[Messaging, JMS & JBossMQ] - Re: Messages always persistent in Topic

by fljmayer

Yes, a list of common problems (looks like many are described in TuningJBossMQ) would help. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068320#4068320 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068320

18 years, 9 months

1
0
0 / 0

[JBoss AOP] - PER_INSTANCE and constructor executions, method calls, etc.

by paulfreeman

I seem to be having an issue with the PER_INSTANCE scope. I have a simple aspect that captures the execution of a method and the execution of a constructor on the same object: package com.kronos.jboss.aop; import org.jboss.aop.Aspect; import org.jboss.aop.Bind; import org.jboss.aop.PointcutDef; import org.jboss.aop.advice.Scope; import org.jboss.aop.joinpoint.Invocation; import org.jboss.aop.pointcut.Pointcut; @Aspect(scope=Scope.PER_INSTANCE) public class AAspect { public AAspect(){ System.out.println("** CREATED " + this.getClass().getSimpleName()); } @PointcutDef ("execution($instanceof{com.kronos.jboss.aop.A}->new(..))") public static Pointcut newA; @PointcutDef ("execution(* $instanceof{com.kronos.jboss.aop.A}->foo(..))") public static Pointcut aroundFooMethod; @Bind (pointcut="com.kronos.jboss.aop.AAspect.newA") public Object aroundNewA(Invocation invocation) throws Throwable{ System.out.println("before new A " + this.getClass().getSimpleName()); Object result = invocation.invokeNext(); System.out.println("after new A " + this.getClass().getSimpleName()); return result; } @Bind (pointcut="com.kronos.jboss.aop.AAspect.aroundFooMethod") public Object aroundFoo(Invocation invocation) throws Throwable{ System.out.println("before foo " + this.getClass().getSimpleName()); Object result = invocation.invokeNext(); System.out.println("after foo " + this.getClass().getSimpleName()); return result; } } package com.kronos.jboss.aop; public class A { public A(){ System.out.println("In new A..."); } public void foo(){ System.out.println("In foo..."); } } When I execute a simple test: package com.kronos.jboss.aop; public class Main { /** * @param args */ public static void main(String[] args) { A a = new A(); a.foo(); } } I expect to have the AAspect instance created every time an instance of A is created, however the advice on the A constructor is never executed. See output: In new A... ** CREATED AAspect before foo AAspect In foo... after foo AAspect If I change the scope to PER_CLASS, I get the expected output, but not the desired number of instances of my aspect. Here is the output: ** CREATED AAspect before new A AAspect In new A... after new A AAspect before foo AAspect In foo... after foo AAspect Also, if I the scope is PER_INSTANCE and I change the foo method pointcut definition from exection to call, an instance of my AAspect is never created. Here is the modified pointcut: @PointcutDef ("call(* $instanceof{com.kronos.jboss.aop.A}->foo(..))") public static Pointcut aroundFooMethod; Here is the output: In new A... In foo... If I try call in the pointcut and change the scope back to PER_CLASS, I get the correct output: ** CREATED AAspect before new A AAspect In new A... after new A AAspect ** CREATED AAspect before foo AAspect In foo... after foo AAspect I assume this is a bug, but I wanted to check here first to make sure I understand the PER_INSTANCE scope designation. I was unable to find this listed as a BUG in JIRA. Any help would be appreciated. I have tried this both in the annotation syntax shown above, and with an aop.xml file configuration - same results. Thanks, Paul View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068319#4068319 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068319

18 years, 9 months

1
0
0 / 0

[JBoss Messaging] - ClassLoader issue with MDB and Hibernate

by genman

The issue I see is that Hibernate can't load classes when it does a transaction commit, after a JMS message is processed in an MDB. See this thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068315 When does Thread.setCurrentClassLoader() get called for messages being processed in an MDB? It seems this is somehow reset, perhaps post processing. JBoss AS /connector does not set the classloader. Looking at the Hibernate sources, Hibernate does not make this call. So I assume it's part of JBoss Messaging (the JmsSession), and it must get reset before transaction commit. Anyway, it's a definite bug, I just need to know where the bug is. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068318#4068318 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068318

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Custom Logging in Seam

by ucfjeff

Thank you Matt and Gavin. We have found that the log4j MDC will meet our requirements in the manner of the example provided by Gavin above. Matt you are here in Orlando? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068316#4068316 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068316

18 years, 9 months

1
0
0 / 0

[Beginners Corner] - Re: Classloading issue either with JMS inflow, TM, or Hibern

by genman

I have more of a definitive question than a problem. When does Thread.setCurrentClassLoader() get called for messages being processed in an MDB? It seems this is somehow reset. JBoss AS /connector does not do this. Looking at the Hibernate sources, Hibernate does not make this call. So I assume it's part of JBoss Messaging (the JmsSession), and it must get reset before transaction commit. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068315#4068315 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068315

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Seam on tomcat connection problem using EJB

by Stateless Bean

F**** somethink wrong is going on when I insecrt source of jboss-beans. :( third try | <?xml version="1.0" encoding="UTF-8"?> | | <deployment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" | xsi:schemaLocation="urn:jboss:bean-deployer bean-deployer_1_0.xsd" | xmlns="urn:jboss:bean-deployer"> | | <bean name="CenturionDatasourceBootstrap" class="org.jboss.resource.adapter.jdbc.local.LocalTxDataSource"> | <property name="driverClass">org.postgresql.Driver</property> | <property name="connectionURL">jdbc:postgresql://localhost:5432/Centurion</property> | <property name="userName">postgres</property> | <property name="jndiName">java:/CenturionDatasource</property> | <property name="minSize">0</property> | <property name="maxSize">10</property> | <property name="blockingTimeout">1000</property> | <property name="idleTimeout">100000</property> | <property name="transactionManager"><inject bean="TransactionManager"/></property> | <property name="cachedConnectionManager"><inject bean="CachedConnectionManager"/></property> | <property name="initialContextProperties"><inject bean="InitialContextProperties"/></property> | </bean> | | <bean name="CenturionDatasource" class="java.lang.Object"> | <constructor factoryMethod="getDatasource"> | <factory bean="CenturionDatasourceBootstrap"/> | </constructor> | </bean> | | </deployment> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068314#4068314 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068314

18 years, 9 months

1
0
0 / 0

[JBoss Seam] - Re: Seam on tomcat connection problem using EJB

by Stateless Bean

18 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user July 2007