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

[Design of POJO Server] - Re: recursing directories on deployment

by adrian＠jboss.org

"bill.burke(a)jboss.com" wrote : | Now, when lib/ is processed, the JARStructure deployer determines it is neither a "archive" nor a top level directory, so it does not process lib's children. | How could it know that lib/ is a subdeployment whereas com/ or org/ that just contain classes are not? You need to provide extra information if you want a subdirectory deployed and that subdirectory doesn't have a recognisable suffix. I guess we could make an exception for the special case "lib' and then hope nobody has a class called lib.blah.Some.class :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012986#4012986 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012986

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Scoped beans deployment

by adrian＠jboss.org

I don't understand the question? The policy xml should be unmarshalled to an object that implements BeanMetaDataFactory. When the deployment invokes getBeans() that object will create some BeanMetaData for a POJO that knows how to install/uninstall data into the MetaData repository. | public class Policy implements BeanMetaDataFactory | { | public void setScope(ScopeMetaData); | | public void setMappings(Map<String, ValueMetaData>) | | public List<BeanMetaData> getBeanMetaData() | { | // IMPORTANT the Mappings needs to be converted to a MapMetaData | // such that the injections in ValueMetaData work correctly, i.e. dependencies | return buildMetaDataRepositoryInstallerBeanMetaData(); | } | } | | public class MetaDataRepositoryInstaller | { | public void setScope(ScopeMetaData); | | @Inject // If we can assume there be will only one instance? | public void setKernelMetaDataRepository(KernelMetaDataRepository) | | // The MC will resolve the ValueMetaData to objects! | public void setMappings(Map<String, Object>) | | public void start() | { | // Install | } | | public void stop() | { | // Uninstall | } | } | NOTE: I'm not overly impressed by the name "Policy" perhaps <metadata> would be a better name? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012985#4012985 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012985

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBoss Messaging table.

by timfox

Best thing is to look in org.jboss.messaging.core.plugin.JDBCPersistenceManager BTW the 1.0.1 schema is different to the 1.2 schema. See my previous post View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012967#4012967 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012967

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Schema tarted up

by timfox

The shiny new slick schema is now committed. It's all nice and generic now. JDBCPersistenceManager has no JMS dependencies JMS headers and properties stored in core headers. No more routable Fixes and tweaks to the message proxy model. Renamed tables to JBM_XXX etc There is one test failing org.jboss.test.messaging.core.plugin.postoffice.cluster.RedistributionWithDefaultMessagePullPolicyTest which I am dealing with now. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012966#4012966 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012966

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: wsimport API, SPI, command line tool, and ant task

by thomas.diesler＠jboss.com

Yes, this functionality should be included in 1.2.0 for many reasons. The actual naming of the tools seems to be the only remaining issue and should of course not hold back this important feature. Lets clarify and step back a little. When consuming a thirdparty web service using jbossws (i.e. a web service client) one would start with the abstract contract as input | wsdl -> [wsimport] | +- SEI | +- Service | +- JAXB artifacts | +- [wrappers] | +- [impl template] | [wrappers] - are generated on demand (i.e. with doc/lit wrapped, for exceptions) [impl template] - a template for the endpoint implementation could be generated When providing a webservice using jbossws one would start with the implementation bean or possibly with an SEI | Impl -> [wsgen] | [SEI] +- [wrappers] | +- [wsdl] | [wrappers] - are generated on demand (i.e. with doc/lit wrapped, for exceptions) [wsdl] - could be generated if asked to do so For branding reasons and clarity sake we cannot name the jbossws tools the same as the RI tools. After some whiteboard sessions, we came up with the following suggestions [wsgen]: javatowsdl, wsserver, wscontract, wsendpoint, wsexport [wsimport]: wsdltojava, wsclient Our favorite choice is underlined. I would like to reach a conclusion on this today, so we can actually bring the feature in and write about is here http://tddell.dyndns.org/mediawiki/index.php/JAX-WS_User_Guide#JBossWS_Tools View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012965#4012965 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012965

19 years, 2 months

1
0
0 / 0

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

by adrian＠jboss.org

"weston.price(a)jboss.com" wrote : anonymous wrote : | | If you are doing this in two phases (parse/runtime) it should be automatic? | | | | The parsing stage populates the repository, the runtime stage (the actual | | construction/configuration of the MBeans/Pojos) should have all the parsed rar information | | in the repository by then? | | | | No, that's the issue. | You missed the point. The logic should be something like: 1a) Parse the MCF xml 1b) Parse the rar xml 2a) Deploy the mcf (create mbean/pojo metadata) 2b) Deploy the rar (create mbean/pojo metadata) 3a) Create the mcf object (callback from the MC when dependencies are satisified) 3b) Create the rar object (-""-) (1) is the parsing stage of deployment (2) is the post parsing or "real deployer" stage of deployment Within each category it doesn't matter in which order things get done because stage (1) fills the repository and stage (2) references it. All you need is for stage (2) to look at the data from (1) so you can decide what name to put in the dependency. It is only in stage (3) - construction of the MBean/POJOs that you are actually going to have wired objects. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012957#4012957 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012957

19 years, 2 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Multithreaded services and their EPR(s)

by mark.little＠jboss.com

EPRs are service addresses and each instance is intended to be created once and typically not changed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012940#4012940 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012940

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Text nodes in SOAP messages

by thomas.diesler＠jboss.com

I assume comments are not white space. Is that right? anonymous wrote : | 2.5 Comments | | [Definition: Comments may appear anywhere in a document outside other markup; in addition, they may appear within the document type declaration at places allowed by the grammar. They are not part of the document's character data; an XML processor may, but need not, make it possible for an application to retrieve the text of comments. For compatibility, the string "--" (double-hyphen) must not occur within comments.] Parameter entity references are not recognized within comments. | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012935#4012935 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012935

19 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Beta2 compile issues

by tom.baeyens＠jboss.com

created a jira issue to make sure i don't forget to look at these problem reports: http://jira.jboss.com/jira/browse/JBPM-835 THANKS, Jeff! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012930#4012930 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012930

19 years, 2 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Multithreaded services and their EPR(s)

by sanjoa

Hi, Based on the posts in this thread I assume that EPR (and Registry) instances are thread safe and one may cache the instances for a period of time. A'm I correct? / Joakim Sandstroem View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012899#4012899 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012899

19 years, 2 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 February 2007