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

[Design of JCA on JBoss] - Re: JBAS-1437 RARMetaDataRepository

by weston.price＠jboss.com

anonymous wrote : | The JAXB deployer helper shouldn't live in jboss-deployers.jar | because otherwise the JAXB jar will need to be in the bootstrap classpath | alongside jboss-deployers.jar | Fine by me. We can put it anywhere that allows me to get me work done. I don't care where it lives. Note, I actually put it alonside the jboss-deployers.jar as a test, with the same results. I assume you knew it wasn't going to work when you checked it in, so I will similarly assume you have an idea of where to put to it to actually make it functional. anonymous wrote : | Classloading 101 | import com.acme.SomeClass | means Class.forName() not thread context classloader | What is your point or are you just trying to appear intelligent and pedantic at the same time? anonymous wrote : | This class should live in a seperate JAXB integration project | that can be "hot deployed". | Again, fine by me. I didn't see anything in this post about where you actually think it should be. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029804#4029804 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029804

19 years

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Re: Updating the server task to detect OutOfMemoryErrors

by mvecera＠redhat.com

I have created new ant task server:memcheck (MemCheckServerTask. java), see file attached to JBAS-4211. It must be put to Branch_4_2 and diff files must be applied. Then you can run ./testsuite/build.sh jboss-memcheck-tests. The only problem is that you must have build/output/jboss-xxx/client/jbossall-client.jar in CLASSPATH environment variable for the task to work. I was not able to solve the classpath problem. Could anybody just have a look on it to help me a bit please? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029789#4029789 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029789

19 years

1
0
0 / 0

[Design of Management Features on JBoss] - Re: Internalization of the management layer

by mark.little＠jboss.com

Updating to use annotations should be fairly straightforward. Nice idea. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029787#4029787 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029787

19 years

1
0
0 / 0

[Design of Kosmos] - Re: Error: HessianServiceExporter only supports POST request

by mega

Hi, Thanks for your help. I can see the SVN monitoring data in my portal page. :) but it takes "a long time" to show the data. I met another problems. I can read the "text" data, but the picture data is not displayed. :( Here are errors in the log. I only attach those "errors" here. What shall I do next? would you please give me some suggestions? Thank you very much. ==================================== 2007-03-20 21:21:10,979 ERROR [STDERR] log4j:ERROR A "org.jboss.logging.util.Onl View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029779#4029779 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029779

19 years

1
0
0 / 0

[Design of JBoss Portal] - Portlet code that acess the CMS JSR-170

by AdiLev

Any short Portlet code that acess the CMS JSR-170 availble as example? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029765#4029765 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029765

19 years

1
0
0 / 0

[Design of JBoss Web Services] - BPEL file to Java file

by demcoul

Hello, I have a project to develope a BPEL Web service. I want to develop with java. I need to represent in Java, BPEL constructors such , , , , . Some one can help me to make this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029757#4029757 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029757

19 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Breaking up the MC project and Mavenizing it

by kabir.khan＠jboss.com

"adrian(a)jboss.org" wrote : | anonymous wrote : | | **** org.jboss.repository (this one can be dropped; a single interface exists) | | | | This needs to be left in place unless Kabir verifies that there was no real | AOP release that referenced this class. | IIRC this class is still referenced by AOP's Advisor for backwards | compatibility reasons. | If we are talking about the MetaDataContext, no real aop releases referenced this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029743#4029743 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029743

19 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Breaking up the MC project and Mavenizing it

by adrian＠jboss.org

"alesj" wrote : | *** P1 - org.jboss.classloading | **** SPI only | This was only there for a test that no longer exists. It should be replaced by whatever underlies the OSGi implementation in terms of defining a bundle/module (I called it domain) classloader anonymous wrote : | **** org.jboss.repository (this one can be dropped; a single interface exists) | This needs to be left in place unless Kabir verifies that there was no real AOP release that referenced this class. IIRC this class is still referenced by AOP's Advisor for backwards compatibility reasons. anonymous wrote : | ** org.jboss.test.kernel.junit | *** TODO - where to put this? | This is part of the yet to be defined MC api (see below for api vs spi). In practice, I don't really want an api for the MC since a key idea behind IOC is to not reference a container api. But you obviously need some form of api for tests, e.g. the getBean() supplied by this testcase implementation. anonymous wrote : | * managed (org.jboss.managed) | ** API (why not SPI?) | An API is meant to be used at runtime by an application/user. It should be 100% stable across releases. A SPI is for integration issues, which is meant for "super users". anonymous wrote : Don't know what you need to do about Eclipse projects. Maven can generate eclipse project files from the pom. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029729#4029729 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029729

19 years

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBAS-1437 RARMetaDataRepository

by adrian＠jboss.org

No, the problem is like I said initially when I wrote this class. The JAXB deployer helper shouldn't live in jboss-deployers.jar because otherwise the JAXB jar will need to be in the bootstrap classpath alongside jboss-deployers.jar (not a problem for Java6 where it is in the JDK). Classloading 101 import com.acme.SomeClass means Class.forName() not thread context classloader This class should live in a seperate JAXB integration project that can be "hot deployed". View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029718#4029718 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029718

19 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Breaking up the MC project and Mavenizing it

by alesj

A quick overview of our current MC codebase: Microcontainer's artifacts (via Maven): * aop-int ** no SPI ** impl (+ resources/schema) *** org.jboss.aop.microcontainer.aspect (separate artifact) ** tests * container ** 4 diff projects ** tests *** P1 - org.jboss.classloading **** SPI only *** P2 - org.jboss.metadata **** org.jboss.repository (this one can be dropped; a single interface exists) **** SPI **** impl: annotation, generic, plugins *** P3 **** org.jboss.annotation ***** no SPI **** org.jboss.beans.info ***** SPI ***** plugins **** org.jboss.classadaptor ***** SPI ***** plugins **** org.jboss.config ***** SPI ***** plugins **** org.jboss.joinpoint ***** SPI ***** plugins **** org.jboss.reflect ***** SPI ***** plugins *** P4 **** org.jboss.javabean ***** no SPI *** (P5) - org.jboss.net, org.jboss.virtual (already moved to VFS project) // * dependency (org.jboss.dependency) ** SPI ** plugins ** tests * deployers (org.jboss.deployers) ** SPI ** plugins ** tests * kernel ** org.jboss.beans.metadata *** SPI *** plugins ** org.jboss.kernel *** SPI + Kernel, KernelFactory, KernelPermission *** plugins ** org.jboss.test.kernel.junit *** TODO - where to put this? ** tests * managed (org.jboss.managed) ** API (why not SPI?) ** plugins ** tests * metatype ** API (why not SPI?) *** we could separate API into SPI and plugins? ** no plugins / impl ** tests * spring-int ** no SPI ** impl (+ resources/schema) ** tests Don't know what you need to do about Eclipse projects. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4029712#4029712 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4029712

19 years

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 March 2007