December 2007 - jboss-dev-forums - Jboss List Archives

[Design of POJO Server] - Re: vfs issue?

by charles.crouch＠jboss.com

"pete.muir(a)jboss.org" wrote : Seam is a dead duck on AS 5 until this can be fixed. So what happened/is going to happen with respect to this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111786#4111786 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111786

18 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Nested property ref

by alesj

Commited. The tests to watch are NestedPropertyTestCase. And the one that does most of the nested work is BeanInfoUtilTestCase. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111784#4111784 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111784

18 years, 4 months

1
0
0 / 0

[Design of JBoss Profiler] - Re: JBoss Profiler Quick Start

by clebert.suconic＠jboss.com

If you also want to install the Memory leak tool (JVMTI) you will also need to copy jbossAgent.dll/so into your path (and add -agentlib:jbossAgent to your JVM) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111772#4111772 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111772

18 years, 4 months

1
0
0 / 0

[Design of JBoss Profiler] - Re: JBoss Profiler Quick Start

by jigu888

Hi, I am new to JBoss Profiler. Please help me to setup it within JBoss Application Server. I am using jboss-4.0.5.GA. The output of 'java -version' command is : ---------------- java version "1.5.0" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-b64) Java HotSpot(TM) Client VM (build 1.5.0-b64, mixed mode, sharing) ---------------- The operating system is Windows Server 2003. I am using jboss-profiler-1.0.CR4(2). I have setup it as follows: 1. Copied jbossInspector.dll to C:\Windows\System32 2. Copied jboss-profiler.war, jboss-profiler-jvmti.sar and jboss-profiler-noAOP.sar to %JBOSS_HOME%\server\default\deploy directory 3. Edited run.bat file and appended following to JAVA_OPTS: -XrunjbossInspector:%JBOSS_HOME%/server/default/tmp/profiler,memory=true,tracer=true 4. Created profiler directory under tmp folder for above step. When I started the jboss service by double clicking the run.bat file, I got following exception: ---------------- 2007-12-11 03:25:39,619 DEBUG [org.jboss.deployment.SARDeployer] Deploying SAR, create step: url file:/D:/JBoss/jboss-4.0.5.GA/server/default/deploy/jboss-profiler-jvmti.sar 2007-12-11 03:25:39,619 DEBUG [org.jboss.deployment.SARDeployer] Registering service UCL=jmx.loading:UCL=8f2ca6 2007-12-11 03:25:39,619 DEBUG [org.jboss.system.ServiceCreator] About to create xmbean object: jboss.profiler:mbean=JVMTIClass with code: org.jboss.profiler.jvmti.JVMTIInterface with descriptor: META-INF/jvmti-xmbean.xml 2007-12-11 03:25:39,650 ERROR [org.jboss.profiler.jvmti.JVMTIInterface] The DLL couldn't be loaded, you won't be able to use any JVMTIInterface feature java.lang.UnsatisfiedLinkError: no jbossAgent in java.library.path at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1682) at java.lang.Runtime.loadLibrary0(Runtime.java:822) at java.lang.System.loadLibrary(System.java:992) at org.jboss.profiler.jvmti.JVMTIInterface.(JVMTIInterface.java:65) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) ..... ..... at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:490) at java.lang.Thread.run(Thread.java:595) 2007-12-11 03:25:39,806 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss.profiler:mbean=JVMTIClass 2007-12-11 03:25:39,806 DEBUG [org.jboss.system.ServiceController] Creating service jboss.profiler:mbean=JVMTIClass ---------------- Am I missing something? Please help me. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111769#4111769 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111769

18 years, 4 months

1
0
0 / 0

[Design of JMX on JBoss (JBoss/JMX)] - Re: Updating the logging framework(JBAS-2412)

by david.lloyd＠jboss.com

So this discussion pretty much fizzled. Since I've been bitten by this issue yet again, I thought I'd opine a bit. First point. The decision to use JDK logging or log4j on the backend should have ZERO impact on the user. A user should be able to use EITHER of these frameworks from their software, and the log messages should be categorized and filtered in the expected way. No, relying on the System.out/err capture facility is NOT adequate. Second point. Due to the above point, switching to JDK logging should NOT mean that log4j support would cease to exist (and vice versa) - just that log4j log messages get mapped to JDK loggers. So application developers who use log4j should not have to stop using log4j. Third point. JBAS 4.2.x still does not support JDK logging in ANY way out of the box. Booooo. Fourth point. Framework developers (specifically, those at jboss.org) would be well advised to stick to using ONLY JDK logging. The reason for this is simple: using 3 or 4 frameworks that each require different logging frameworks means that the end user now also has a number of logging frameworks to track down and deliver with their product. Case in point: Remoting 3 as of now requires both slf4j AND log4j, and it doesn't even use either one of these (it uses JDK logging)! If framework developers use ONLY JDK logging, the end user will have a much easier time integrating the framework. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111766#4111766 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111766

18 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: setting managed property of type List

by alesj

"alex.loubyansky(a)jboss.com" wrote : | Have you updated the snapshot? | No. For the AS5_trunk I guess we need a new release. I'm still working on some stuff, so I hope we can wait till I get it in. But I'll be done till we tag all stuff for AS5_beta3. "alex.loubyansky(a)jboss.com" wrote : | Is it in metatype? Yes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111758#4111758 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111758

18 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: setting managed property of type List

by alex.loubyansky＠jboss.com

Thanks, Ales. Have you updated the snapshot? Is it in metatype? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111756#4111756 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111756

18 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Nested property ref

by alesj

OK, thanks for the short explanation. :-) So, my new impl is legit? ;-) Do I still need to wrap it up with MetaDataStack push and ContextClassloader change? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111736#4111736 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111736

18 years, 4 months

1
0
0 / 0

[Design of JBoss ESB] - JAXBIntros vs JiBX/Castor ? Also tooling support for code/co

by sameer.rao＠compuware.com

JAXBIntro seems to be providing functionality similar to JiBX/Castor? What would be the core difference. Also are there plans on providing tooling support i.e. XJC type complier to generate a POJO class structure and corresponding config file? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111735#4111735 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111735

18 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Nested property ref

by adrian＠jboss.org

Joinpoints are legacy. I explained the history behind them somewhere before, find that for a longer discussion. The original aim (abstracting different invocation models) has been dealt with using other approaches. Most of what they do is just delegated to Class/MethodInfo, etc. They now have only two real uses: 1) AOP integrates by overriding the constructor joinpoint 2) It makes the constructor/method (e.g. for factories) handling a bit cleaner since the code just has to resolve and dispatch a joinpoint. Both could be implemented in different ways which would finally remove the need for the Joinpoint abstraction. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111729#4111729 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111729

18 years, 4 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-dev-forums December 2007