April 2008 - jboss-dev-forums - Jboss List Archives

[Design of JBossXB] - Re: jbossxb 1.0.0.SP2

by dimitris＠jboss.org

This is needed for Branch_4_2, so the old 'common' project is used there at version 1.2.1.GA https://svn.jboss.org/repos/repository.jboss.org/jboss/common/1.2.1.GA/ I only found the 'brew' version of it in the maven repo: https://svn.jboss.org/repos/repository.jboss.org/maven2/jboss/common/jbos... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140900#4140900 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140900

18 years

1
0
0 / 0

[Design of JBossXB] - Re: jbossxb 1.0.0.SP2

by alex.loubyansky＠jboss.com

I am fixing the thirdparty dependencies. I can't find common-core 1.0.0.GA in the repository. Which one should I use? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140899#4140899 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140899

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: NPE with new parsing in aop-mc-int tests

by alesj

"kabir.khan(a)jboss.com" wrote : Since AOPDeployment does not exist in mc trunk, how does the aop stuff even get parsed at the moment? | I've got this | package org.jboss.aop.microcontainer.beans.beanmetadatafactory; | | import java.util.List; | | import javax.xml.bind.annotation.XmlAnyElement; | import javax.xml.bind.annotation.XmlElement; | import javax.xml.bind.annotation.XmlElements; | import javax.xml.bind.annotation.XmlNsForm; | import javax.xml.bind.annotation.XmlRootElement; | import javax.xml.bind.annotation.XmlType; | | import org.jboss.beans.metadata.spi.BeanMetaDataFactory; | import org.jboss.kernel.plugins.deployment.AbstractKernelDeployment; | import org.jboss.managed.api.annotation.ManagementObject; | import org.jboss.managed.api.annotation.ManagementProperties; | import org.jboss.xb.annotations.JBossXmlSchema; | | /** | * | * @author <a href="kabir.khan(a)jboss.com">Kabir Khan</a> | * @version $Revision: 1.1 $ | */ | @ManagementObject(properties = ManagementProperties.EXPLICIT) // TODO - explicitly add props we want to manage | @JBossXmlSchema(namespace="urn:jboss:aop-beans:1.0", elementFormDefault=XmlNsForm.QUALIFIED) | @XmlRootElement(name="aop") | @XmlType(propOrder={"annotations", "classLoader", "beanFactories", "create", "start", "stop", "destroy", "aliases"}) | public class AOPDeployment extends AbstractKernelDeployment | { | private static final long serialVersionUID = 1L; | | | @XmlElements | ({ | @XmlElement(name="aspect", type=AspectBeanMetaDataFactory.class), | @XmlElement(name="interceptor", type=InterceptorBeanMetaDataFactory.class), | @XmlElement(name="bind", type=BindBeanMetaDataFactory.class), | @XmlElement(name="stack", type=StackBeanMetaDataFactory.class), | @XmlElement(name="typedef", type=TypeDefBeanMetaDataFactory.class), | @XmlElement(name="cflow-stack", type=CFlowStackBeanMetaDataFactory.class) | }) | @XmlAnyElement | public void setBeanFactories(List<BeanMetaDataFactory> beanFactories) | { | super.setBeanFactories(beanFactories); | } | } | Looks like old stuff (see diff package): | addJaxbSchema("urn:jboss:aop-beans:1.0", "org.jboss.aop.microcontainer.beans.metadata.AOPDeployment"); | Why is it still there? :-) If the metadata class is not there, you get this ignore in SingletonSchemaResolverFactory: | public boolean addJaxbSchema(String namespace, String reference) | { | try | { | resolver.addClassBinding(namespace, reference); | if (log.isTraceEnabled()) | log.trace("Mapped '" + namespace + "' to '" + reference + "'"); | return true; | } | catch (Exception ignored) | { | if (log.isTraceEnabled()) | log.trace("Ignored: ", ignored); | return false; | } | } | And then you get the null in beanfactories - a jbossxb problem Adrian mentioned. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140898#4140898 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140898

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: AOPConstructorJoinpoint::methodHasAnnotations is wrong

by alesj

"kabir.khan(a)jboss.com" wrote : You added the @HasInstanceAnnotaiton to the @JMX annotation which causes the JMXDecoratedTestCase to fail. I have reverted that change, but it causes your HasInstanceAnnotation test to fail. See this discussion: - http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140167#4140167 And these two JIRAs: - http://jira.jboss.com/jira/browse/JBMDR-21 - http://jira.jboss.com/jira/browse/JBMICROCONT-279 What's the usage of @JMX in that JMXDecoratedTC, apart for marking the bean to register it into MBeanServer? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140896#4140896 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140896

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: AOPConstructorJoinpoint::methodHasAnnotations is wrong

by kabir.khan＠jboss.com

You added the @HasInstanceAnnotaiton to the @JMX annotation which causes the JMXDecoratedTestCase to fail. I have reverted that change, but it causes your HasInstanceAnnotation test to fail. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140894#4140894 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140894

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: AOPConstructorJoinpoint::methodHasAnnotations is wrong

by alesj

While going over all sub INSTANCE levels, I also use JOINPOINT, where 'real' method annotations live. This means that I get hasSubInstanceMetaData == true for beans that have class annotated methods. So this: - http://www.jboss.org/index.html?module=bb&op=viewtopic&t=131170&start=10 again fails. I've added InstanceAnnotation(false) to all our IoC annotations. So that makes the tests pass. But it would still create proxy for any other non-InstanceAnnotation marked annotations that would live on methods (on class). Should I exclude JOINPOINT in that hierarchy? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140892#4140892 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140892

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: NPE with new parsing in aop-mc-int tests

by kabir.khan＠jboss.com

I haven't changed anything in that area, so most likely this is caused by the upgrade to JBoss XB? That upgrade would use the org.jboss.aop.microcontainer.beans.metadata.AOPDeployment class as the root of JAXB parsing instead of the aop bean schemainitializer. Since AOPDeployment does not exist in mc trunk, how does the aop stuff even get parsed at the moment? I can switch to use the JAXB stuff later today: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4140727#4140727 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140889#4140889 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140889

18 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Sending SOAP Message through HttpListener rather than JM

by tfennelly

"coejboss" wrote : Can it be a version issue of jboss-remoting.jar? I am using Specification-Version: 2.2.1.GA. I wouldn't expect a JBR version issue to result in a KernelRegistryEntryNotFoundException. I'd guess that this is more likely something to do with the version of JBossWS. To get back on track... we started on "how to deploy a HTTP endpoint" on the ESB and got to using the <jbr-listener>. Looks like we've moved on to a JBossWS issue now re running the webservice_producer quickstart. Yes/no? Which version of the ESB are you using? Are you running from SVN src or are you using a distro ? Have you patched you JBossAS with a newer version of JBossWS? Perhaps you're not even interested in using the SOAPProcessor and Webservice endpoints?? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140888#4140888 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140888

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Circular dependency error msg problem

by alesj

"ALRubinger" wrote : I'm seeing: | | 23:04:15,155 WARN [HDScanner] Failed to process changes | | org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): | | .... | | | | From hard copy deployment, but JMX Deployments are silent and do not report errors. | This doesn't tell me anything. Silent in what way? e.g. what is the input, what is the expected result, what actually happens, etc... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140863#4140863 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140863

18 years

1
0
0 / 0

[Design of JBoss Build System] - Re: Dependency conflicts lost during AS mavenization

by dimitris＠jboss.org

I guess you can only move the latest stuff you are currently working on, for which no tagged release of another project depends upon. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4140862#4140862 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4140862

18 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 April 2008