July 2009 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: Parallel deployments

by kabir.khan＠jboss.com

I think there will be a corner-case issue when AS boots up. At the end, it checks to see what has not been fully deployed. If there are asynchronous deployments still being processed when the main AS thread finishes the boot, they will probably be picked up as not deployed. The AbstractController internally marks which contexts are currently being processed asynchronously, so we should probably expose a check in the spi | boolean processingAsynchronousContexts() | and at the end of the bootstrap do something like: | //Main bootstrap code... | | if (controller instanceof AsynchController){ | while (controller.processingAsynchronousContexts()){ | Thread.sleep(100); | } | } | | //Report uninstalled contexts | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241690#4241690 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241690

16 years, 6 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Parallel deployments

by kabir.khan＠jboss.com

Currently there is no way to set the executor via the spi, you need to cast to AbstractController. I could add the setExecutor() method to the Controller interface, but maybe it belongs better in an AsynchController interface (similarly to what was done for GraphController)? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241675#4241675 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241675

16 years, 6 months

1
0
0 / 0

[Design of JBossXB] - Re: JBossXB does not assign schema defined attribute default

by alex.loubyansky＠jboss.com

The attribute shouldn't be bound into the blueprint namespace of course. The issue is actually with jboss-reflect. Apparently, propertyInfo.getUnderlyingAnnotation(annotationType) doesn't work for 'is'-methods (i.e. it returns null even if the method is annotated). If you move @XmlAttribute to setDefaultLazyInit(...) it'll work. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241670#4241670 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241670

16 years, 6 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Deployer meta data don't specify XML element order

by kabir.khan＠jboss.com

You also need to upgrade MC to the latest version. You're using 2.0.4.GA. MC 2.0.5.GA onwards contain the fixes to work with JBoss XB 2.0.1.GA View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241669#4241669 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241669

16 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: GetOutcomes returns additional transition

by shekharv

But having said that, here comes the fun part: I believe this qualifies as unexpected behavior. consider this process-definition: | <?xml version="1.0" encoding="UTF-8"?> | | <process key="CompletedOutcome" name="CompletedOutcome" xmlns="http://jbpm.org/4.0/jpdl"> | | <start g="20,20,48,48"> | <transition to="review"/> | </start> | | <task name="review" g="96,16,127,52"> | <assignment-handler | class="RandomTaskHandler"/> | <transition to="redpill"/> | <transition name="completed" to="bluepill"/> | </task> | | <end name="redpill" g="255,16,88,52"/> | <end name="bluepill" g="255,16,88,75"/> | </process> | | taskService.completeTask(777, null); | Guess where the workflow will end when the task is ended. Irrespective of what OUTCOME you pass to the completeTask, null or 'completed' it will always end up in 'bluepill'. Is there any way to get to the redpill 'end' state? NO! Now is this right or wrong? The more I look at this, the lesser and lesser sense it makes to me. But if course, the JIRA is rejected :(. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241657#4241657 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241657

16 years, 6 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Consistent handling of HTTP response header across HTTP

by Kevin.Conner＠jboss.com

"rmolin" wrote : Any idea when this will make it into the SOA platform ? - We have a corrective action that probably needs to be removed once this is in place. David's work is going into the project for the 4.6 release. The current plan is to make another project release, 4.7, towards the end of September and use that as the basis for the SOA 5 platform. Kev View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241652#4241652 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241652

16 years, 6 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Deployer meta data don't specify XML element order

by thomas.diesler＠jboss.com

After an upgrade to jbossxb-2.0.1.GA I see | Caused by: java.lang.IllegalStateException: Cannot deploy beans from: bundle://10.0:1/META-INF/base-deployers-beans.xml | at org.jboss.osgi.microcontainer.internal.EmbeddedKernelBootstrap.deploy(EmbeddedKernelBootstrap.java:79) | at org.jboss.osgi.microcontainer.internal.MicrocontainerServiceImpl$1.addingService(MicrocontainerServiceImpl.java:141) | at org.osgi.util.tracker.ServiceTracker$Tracked.trackAdding(ServiceTracker.java:1030) | at org.osgi.util.tracker.ServiceTracker$Tracked.trackInitialServices(ServiceTracker.java:891) | at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:296) | at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:235) | at org.jboss.osgi.microcontainer.internal.MicrocontainerServiceImpl.start(MicrocontainerServiceImpl.java:160) | at org.jboss.osgi.microcontainer.internal.MicrocontainerServiceActivator.start(MicrocontainerServiceActivator.java:47) | at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:589) | at org.apache.felix.framework.Felix.startBundle(Felix.java:1461) | ... 26 more | Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: bundle://10.0:1/META-INF/base-deployers-beans.xml@8,49 | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:177) | at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:147) | at org.jboss.osgi.microcontainer.internal.EmbeddedXMLDeployer.deploy(EmbeddedXMLDeployer.java:140) | at org.jboss.osgi.microcontainer.internal.EmbeddedKernelBootstrap.deploy(EmbeddedKernelBootstrap.java:74) | ... 35 more | Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Property order is not specified for type org.jboss.beans.metadata.plugins.AbstractDependencyValueMetaData bound to a sequence. Property order can be specified using @XmlType.propOrder or @XmlAccessorOrder. List of properties: underlyingValue classShortName | AFAICT, this is due to a missing xml element order spec in the meta data. Is this a known (perhaps already fixed) issue? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241651#4241651 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241651

16 years, 6 months

1
0
0 / 0

[Design of JBossXB] - Re: JBossXB does not assign schema defined attribute default

by thomas.diesler＠jboss.com

I updated to jbossxb-2.0.1.GA It seems that the 'default-lazy-init' attribute does not get bound | [tdiesler@tdvaio blueprint]$ cat testsuite/target/test.log | grep default | 2009-07-03 09:58:10,649 TRACE [org.jboss.xb.builder.JBossXBBuilder:885] Checking property defaultLazyInit for org.jboss.osgi.blueprint.parser.xb.TBlueprint type=java.lang.Boolean | 2009-07-03 09:58:10,651 TRACE [org.jboss.xb.builder.JBossXBBuilder:885] Checking property defaultDestroyMethod for org.jboss.osgi.blueprint.parser.xb.TBlueprint type=java.lang.String | 2009-07-03 09:58:10,660 TRACE [org.jboss.xb.builder.JBossXBBuilder:938] Bound attribute default-destroy-method type=org.jboss.osgi.blueprint.parser.xb.TBlueprint property=defaultDestroyMethod propertyType=ReflectClassInfoImpl(a)a9255c{name=java.lang.String}, normalizeSpace=false | 2009-07-03 09:58:10,661 TRACE [org.jboss.xb.builder.JBossXBBuilder:885] Checking property defaultAvailability for org.jboss.osgi.blueprint.parser.xb.TBlueprint type=org.jboss.osgi.blueprint.parser.xb.TAvailability | 2009-07-03 09:58:10,673 TRACE [org.jboss.xb.builder.JBossXBBuilder:938] Bound attribute default-availability type=org.jboss.osgi.blueprint.parser.xb.TBlueprint property=defaultAvailability propertyType=EnumInfoImpl(a)16d2702{name=org.jboss.osgi.blueprint.parser.xb.TAvailability}, normalizeSpace=false | 2009-07-03 09:58:10,674 TRACE [org.jboss.xb.builder.JBossXBBuilder:885] Checking property defaultInitMethod for org.jboss.osgi.blueprint.parser.xb.TBlueprint type=java.lang.String | 2009-07-03 09:58:10,676 TRACE [org.jboss.xb.builder.JBossXBBuilder:938] Bound attribute default-init-method type=org.jboss.osgi.blueprint.parser.xb.TBlueprint property=defaultInitMethod propertyType=ReflectClassInfoImpl(a)a9255c{name=java.lang.String}, normalizeSpace=false | 2009-07-03 09:58:10,677 TRACE [org.jboss.xb.builder.JBossXBBuilder:885] Checking property defaultTimeout for org.jboss.osgi.blueprint.parser.xb.TBlueprint type=java.math.BigInteger | 2009-07-03 09:58:10,679 TRACE [org.jboss.xb.builder.JBossXBBuilder:938] Bound attribute default-timeout type=org.jboss.osgi.blueprint.parser.xb.TBlueprint property=defaultTimeout propertyType=ReflectClassInfoImpl(a)659db7{name=java.math.BigInteger}, normalizeSpace=false | 2009-07-03 09:58:10,756 TRACE [org.jboss.xb.binding.sunday.unmarshalling.AttributesHandler:73] Attribute is not bound: element owner {http://www.osgi.org/xmlns/blueprint/v1.0.0}blueprint, attribute default-lazy-init | 2009-07-03 09:58:10,769 TRACE [org.jboss.xb.builder.runtime.PropertyHandler:94] QName default-timeout handle java.math.BigInteger@edf730 to org.jboss.osgi.blueprint.parser.xb.TBlueprint@16749745 property=defaultTimeout | 2009-07-03 09:58:10,770 TRACE [org.jboss.xb.builder.runtime.PropertyHandler:94] QName default-availability handle org.jboss.osgi.blueprint.parser.xb.TAvailability@17b0998 to org.jboss.osgi.blueprint.parser.xb.TBlueprint@16749745 property=defaultAvailability | 2009-07-03 09:58:10,874 TRACE [org.jboss.xb.binding.sunday.unmarshalling.AttributesHandler:73] Attribute is not bound: element owner {http://www.osgi.org/xmlns/blueprint/v1.0.0}blueprint, attribute default-lazy-init | 2009-07-03 09:58:10,874 TRACE [org.jboss.xb.builder.runtime.PropertyHandler:94] QName default-timeout handle java.math.BigInteger@faa550 to org.jboss.osgi.blueprint.parser.xb.TBlueprint@24864323 property=defaultTimeout | 2009-07-03 09:58:10,875 TRACE [org.jboss.xb.builder.runtime.PropertyHandler:94] QName default-availability handle org.jboss.osgi.blueprint.parser.xb.TAvailability@17b0998 to org.jboss.osgi.blueprint.parser.xb.TBlueprint@24864323 property=defaultAvailability | | @XmlAttribute | public Boolean isDefaultLazyInit() | { | return defaultLazyInit; | } | I also tried | @XmlAttribute(name = "default-lazy-init") | @XmlAttribute(name = "default-lazy-init", namespace = BlueprintContext.XMLNS_BLUEPRINT) | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241649#4241649 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241649

16 years, 6 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: How to use class

by tom.baeyens＠jboss.com

Lifecycle is not part of the public api. It's an experiment to allow for customized task state workflows. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241646#4241646 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241646

16 years, 6 months

1
0
0 / 0

[Design of JBoss ESB] - Error in webservice_producer (Sample application in jbossesb

by ermohanraja

Hi all, I'm new in JBossESB applications. I want to implement jboss webservice in our application. While i convert webservice_producer application (Sample application in jbossesb-server-4.5.GA) to eclipse, getting "SOAPProcessor cannot be resolved". Please anyone help me in this issue. Also please give your ideas to implement JBoss esb web services in J2EE applications. I'm looking forward for your comments. Thanks in advance. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241645#4241645 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241645

16 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 July 2009