September 2008 - jboss-dev-forums

[Design of Messaging on JBoss (Messaging/JBoss)] - Status of documentation in Branch_1_4

by timfox

What's the status of the documentation in Branch_1_4? Has it been merged? If not, can you make sure it's updated properly and properly reflects the the state of the code, e.g. in stuff related to security and sucker password. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178025#4178025 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178025

17 years, 6 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Some maven updates

by kabir.khan＠jboss.com

"pgier" wrote : It looks like ant is compiling the tests twice, is this intentional? | No :-) Once the build is a bit more stable I can take a look at that View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178012#4178012 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178012

17 years, 6 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Too strict pattern matching in PackageClassFilter

by alesj

"alesj" wrote : Result: filter on package doesn't pick up package itself. | Or is this intentional? Since I see class name matching behave this way: | public void testJavaLang() throws Exception | { | ClassFilter filter = PackageClassFilter.createPackageClassFilter("java.lang"); | assertFilterMatchesClassName("java.lang.Object", filter); | assertFilterMatchesClassName("java.lang.X", filter); | assertFilterNoMatchClassName("java.lang", filter); | assertFilterNoMatchClassName("java.lang.", filter); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178011#4178011 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178011

17 years, 6 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Some maven updates

by kabir.khan＠jboss.com

"pgier" wrote : | To compile the JRockit stuff you have to pass JROCKIT_HOME to maven. | Does maven have the concept of a local.properties file? It would be nice not to manually pass in this system property every time View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178010#4178010 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178010

17 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: jbosws integration layers for JBoss application server 4

by alessio.soldano＠jboss.com

The documentation refers to the JBoss AS community versions. There's no JBoss AS 4.3, May be you're using the AS coming with the enterprise application platform 4.3, which should btw already include JBossWS afaik. Please contact the Support for further information in this case. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178003#4178003 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178003

17 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - jbosws integration layers for JBoss application server 4.3.G

by anatolyg

1) You wrote: "Currently, we have integration layers for the JBoss application server 4.2 and 5.0." We are using JBoss application server 4.3.GA Is it a way to get it working with Jboss 4.3.GA? 2) Second question, Can you clarify: After installation of Jboss 4.3. i have JBoss-4.3.GA_Stargate\server\default\deploy\jbossws.sar What is difference between this framework and JBoss Web Services framework that is not part of installation of Jboss? Isn't is conflicts? Can i disable jbossws.sar in some way? Regards Anatoly View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177995#4177995 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177995

17 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Annoyance when running unit tests in eclipse

by ataylor

ok, this should work for all test run scenarios now. log written to ./tests/logs View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177993#4177993 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177993

17 years, 6 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Some maven updates

by kabir.khan＠jboss.com

Doing a ./build.sh release from the build directory gives me compilation errors in the asintegration/ module. Running mvn install from the top-level folder gives me OutOfMemoryErrors | [INFO] ------------------------------------------------------------------------ | [INFO] Building JBoss AOP Framework | [INFO] task-segment: [install] | [INFO] ------------------------------------------------------------------------ | [INFO] [enforcer:enforce {execution: enforce-versions}] | [INFO] [resources:resources] | [INFO] Using default encoding to copy filtered resources. | [INFO] [compiler:compile] | [INFO] Nothing to compile - all classes are up to date | [INFO] [resources:testResources] | [INFO] Using default encoding to copy filtered resources. | [INFO] [compiler:testCompile] | [INFO] Compiling 839 source files to /Users/kabir/sourcecontrol/jboss-aop/aop/target/test-classes | [INFO] ------------------------------------------------------------------------ | [ERROR] BUILD FAILURE | [INFO] ------------------------------------------------------------------------ | [INFO] Compilation failure | Failure executing javac, but could not parse the error: | | | The system is out of resources. | Consult the following stack trace for details. | java.lang.OutOfMemoryError: Java heap space | at java.lang.Object.clone(Native Method) | at com.sun.tools.javac.code.Scope.dupUnshared(Scope.java:122) | at com.sun.tools.javac.comp.MemberEnter.methodEnv(MemberEnter.java:587) | at com.sun.tools.javac.comp.MemberEnter.visitMethodDef(MemberEnter.java:552) | at com.sun.tools.javac.tree.Tree$MethodDef.accept(Tree.java:478) | at com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:383) | at com.sun.tools.javac.comp.MemberEnter.memberEnter(MemberEnter.java:395) | at com.sun.tools.javac.comp.MemberEnter.finishClass(MemberEnter.java:405) | at com.sun.tools.javac.comp.MemberEnter.finish(MemberEnter.java:953) | at com.sun.tools.javac.comp.MemberEnter.complete(MemberEnter.java:920) | at com.sun.tools.javac.code.Symbol.complete(Symbol.java:355) | at com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:612) | at com.sun.tools.javac.comp.Enter.complete(Enter.java:467) | at com.sun.tools.javac.comp.Enter.main(Enter.java:445) | at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:404) | at com.sun.tools.javac.main.Main.compile(Main.java:592) | at com.sun.tools.javac.main.Main.compile(Main.java:544) | at com.sun.tools.javac.Main.compile(Main.java:85) | at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | at java.lang.reflect.Method.invoke(Method.java:585) | at org.codehaus.plexus.compiler.javac.JavacCompiler.compileInProcess(JavacCompiler.java:420) | at org.codehaus.plexus.compiler.javac.JavacCompiler.compile(JavacCompiler.java:141) | at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:493) | at org.apache.maven.plugin.TestCompilerMojo.execute(TestCompilerMojo.java:102) | at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) | at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) | at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) | at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) | at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) | at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) | It works if I go into the aop/ folder and run mvn install there. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177992#4177992 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177992

17 years, 6 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Some maven updates

by kabir.khan＠jboss.com

"pgier" wrote : While working on this, I came up with a few questions about how the AOP build is supposed to work. First, should the artifactId be "jboss-aop" or "jboss-aop-jdk50"? Currently, we have two different artifactIds representing the same artifact, so I would like to combine them into one. Since we don't have other artifacts with the jdk version in the id, I would prefer just "jboss-aop". | I agree there should be just one, jboss-aop sounds good. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177989#4177989 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177989

17 years, 6 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Some maven updates

by kabir.khan＠jboss.com

"pgier" wrote : | All three of these files are also included in the jboss-aop-jdk50.jar file. Do these files need to be in both places? Can I move these files out into the new pluggable-instrumentor module? | I think JRockitPluggableClassPreProcessor.class should be in pluggable-instrumentor.jar (used with AS), while JDK14Transformer.class and JDK14TransformerManager.class should be in jboss-aop-jdk50.jar. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177988#4177988 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177988

17 years, 6 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 September 2008