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

[jBPM Development] - Re: Multiple instances with synchronization

by fabiomsouto

I'm guessing it's not probably possible, right? Or is there something missing? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262912#4262912 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262912

16 years, 1 month

1
0
0 / 0

[jBPM Development] - updated eclipse project names

by tom.baeyens＠jboss.com

i prefixed the eclipse project names with jbpm- so that they're nicely grouped together. i don't think this will cause problems for anyone but that assumption is wrong, let me know. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262900#4262900 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262900

16 years, 1 month

1
0
0 / 0

[JBoss XML Binding Development] - Re: JBossEntityResolver cannot resolve...

by alex.loubyansky＠jboss.com

I don't see it as an issue with JBossEntityResolver. As you can see it is trying to use publicId/systemId as URL, find in the classpath and you can help by mapping the location explicitly. This is the contract that it implements. If you have a use-case which shows a bug in the impl of the contract then it's an issue otherwise it's a misuse. If you want to rely on resolution based on the classpath then you have to specify the correct relative path. Like you had posted previously. <xsd:import namespace="http://www.opengis.net/gml/3.2" schemaLocation="OGC/net/opengis/gml/3.2.1/gml.xsd"/> Alternatively, perhaps you can provide your own EntityResolver impl, but I am not sure about that. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262898#4262898 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262898

16 years, 1 month

1
0
0 / 0

[JBoss Web Services Development] - Re: jms transport support in jbossws-cxf

by richard.opalka＠jboss.com

"richard.opalka(a)jboss.com" wrote : | is accessible via httpit's a bug if it isn't. I mean you're able to invoke endpoint operations via HTTP(S) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262885#4262885 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262885

16 years, 1 month

1
0
0 / 0

[JBoss Web Services Development] - Re: jms transport support in jbossws-cxf

by richard.opalka＠jboss.com

"jim.ma" wrote : So this correct jms address deployer should be ordered after TomcatDeployer(the war actually started). | | What do you think about this ? | We shouldn't rely on Tomcat deployer :( The fact you'll place your new deployer after tomcat deployer doesn't mean war is deployed and ready to service after tomcat deployer finishes its job. For example if there's a war with many dependencies on other archives, this war won't be started until dependencies are satisfied. IOW your prediction ordered after TomcatDeployer(the war actually started) is wrong. BTW we had many troubles in the past with such expectations and it took us months to fix that. Now all the JBossWS deployers are executed before tomcat deployer by purpose. "jim.ma" wrote : | BTW, I also tried the native jms transport sample . I see there is only jms endpoint registered . The http endpoint is not been list in the services list page . Is it intended ? | I don't know the details of that native sample, but if endpoint in JMS sample is accessible via http, it should be registered with endpoints registry and it's a bug if it isn't. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262884#4262884 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262884

16 years, 1 month

1
0
0 / 0

[JBoss Microcontainer Development POJO Server] - Re: integration with the Papaki annotation indexer/repositor

by emuckenhuber

"dimitris(a)jboss.org" wrote : Rather than keep going with the dog-fight, why not putting down the exact requirements/usecase for this module (papaki), or is this already discussed elsewhere? | I haven't found a discussion on the goals of papaki - so i'll just add a few thoughts. Not all related to papaki, but just describing some of the problems i see with the annotation scanning. Maybe that helps that we can define clearer requirements what papaki should provide and what has to be done elsewhere. * unified API, independent of the scanning strategy (precompiled or runtime) - as when writing deployers integration code it should not matter where this information comes from. The precompiled index has to be optional, since the spec requires runtime scanning. So either a precompiled index exists or we have to generate it during deployment time. So that we really have a reusable index, which should be used by all deployers and we only do scanning once (or use the index). * jboss-metadata - for example jboss-metadata is just asking the AE to get a list of classes which have a given top-level annotation (e.g. @Stateful). Then loading the class and do a separate annotation processing with java reflect. This is also because AE does not have enough information about inheritance, which is needed for all the EE annotation processing. Beside jboss-metadata there are not many users of AnnotationEnvironment, but we really should avoid having things like getClassloader().loadClass(metaData.getClassName()).getAnnotation(X) if possible. * jboss-mdr integration - this index should be reused in the MDR as well, as mentioned earlier in this thread. * inclusion/exclusion of deployments, .jars, classes - we need a way to exclude stuff from annotation scanning, as we are mostly just doing too much scanning. Basically we already have jboss-scanning.xml - which makes sense for our own deployments. Still we need a programmatic way of excluding stuff like: - if the deployment is not an EE5/EE6 deployment we can just skip any annotation scanning, - if isMetaDataComplete() - afaik the new servlet spec requires to exclude .jars (web-fragments), where we should be able to skip scanning as well. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262866#4262866 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262866

16 years, 1 month

1
0
0 / 0

[JBoss Web Services Development] - Re: jms transport support in jbossws-cxf

by jim.ma

CXF jms endpoint can be started without MDB , so the jms address info is only in wsdl or jbossws-cxf.xml. We can write another DeploymentAspect to extract this information . But it seems redundant work to parse the wsdl port address and jbossws-cxf.xml destination configuration. So the another way could be : Place an deployer after TomcatDeployer. In cxf, all the started endpoints will be registered in bus. We can get address info from it . But we only can get it after cxf endpoints started. So this correct jms address deployer should be ordered after TomcatDeployer(the war actually started). What do you think about this ? BTW, I also tried the native jms transport sample . I see there is only jms endpoint registered . The http endpoint is not been list in the services list page . Is it intended ? Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262862#4262862 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262862

16 years, 1 month

1
0
0 / 0

[JBoss OSGi Development] - Re: Extender Patter vs. LifecycleInterceptors

by thomas.diesler＠jboss.com

anonymous wrote : | I just wanna re-use the Deployer/LI logic I once wrote. | Ok, that is a good enough use case https://jira.jboss.org/jira/browse/JBOSGI-195 https://jira.jboss.org/jira/browse/JBOSGI-196 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262852#4262852 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262852

16 years, 1 month

1
0
0 / 0

[Embedded JBoss Development] - Re: Embedded and Bootstrap Development

by ALRubinger

Yep, send me an email and I'll attach 'em to you. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262821#4262821 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262821

16 years, 1 month

1
0
0 / 0

[Embedded JBoss Development] - Re: Embedded and Bootstrap Development

by manuel.chinea

Hi ALR, I'll checkout the code and see it tonight. Is there any Eclipse templates, code formatter preferences you use in the project?. Thnxs. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262818#4262818 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262818

16 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums October 2009