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

[Design of Management Features on JBoss] - Re: Using xinclude in config files

by adrian＠jboss.org

XInclude is already handled by JBossXB (if the parser supports it, which Xerces does). With the JBoss "resource:" url handler it is fairly trivial to include things from the classpath, e.g. | <?xml version="1.0" encoding="UTF-8"?> | | | <xi:include href="resource:org/jboss/some/path/included.xml" | xmlns:xi="http://www.w3.org/2001/XInclude"/> | | If all the new deployers use the helper classes then it would be trivial to enable XInclude for their JAXP parsers as well. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025065#4025065 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025065

19 years, 1 month

1
0
0 / 0

[Design of OSGi Integration] - Re: OSGiControllerContext design

by adrian＠jboss.org

"alesj" wrote : | In order to register OSGi service, one must have current bundle's BundleContext. | This changes the concept that we are currently used to - (mostly) one mbean server, main bootstrap kernel - multiple contexts with multiple (m)beans pluged via 'central' state machine. | Here we have multiple beans / services coresponding to certain bundle context. Where to keep this bundle context information in order to be accessable by MC beans marked as an OSGi exposed / lookup services? | The BundleContext should come from the deployment, it is an object that lives outside the core microcontainer like the KernelDeployment aggregation. It should be held on the OSGiControllerContext and passed to the OSGi api facade in which the OSGi service lives. If you want to integrate other contexts that are not native OSGi (like POJOs mbeans), this will need an "on the fly" implementation of the bundle context or whatever OSGi expects. I can't remember the exact details, since it is a while since I looked at the OSGi api. I do remember there are some notifications required in there somewhere. For an example of a simple facade., see the ServiceControllerContext which pretends to provide a legacy ServiceController, which is now just a wrapper to the MC. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025047#4025047 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025047

19 years, 1 month

1
0
0 / 0

[Design of OSGi Integration] - Re: OSGiControllerContext design

by adrian＠jboss.org

"alesj" wrote : | What was the idea behing KernelRegistryPlugin? | To sometimes simplify Controller integration with some other pojo producing layer? | It is to make available via injection objects that are not themselves controlled by the Microcontainer. It has a much weaker dependency notion. i.e. the dependent object either exists or it doesn't, it has no other state. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025043#4025043 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025043

19 years, 1 month

1
0
0 / 0

[Design of JBoss Portal] - Re: OpenSSO integration

by vdinino

Hi first of all I confim we are using JB 2.4. So far, we handled with LoginModule, UserModule, RolesModule. We are still working on them and we are glad to put them online as soon as we have a good release. thank you for your advices. We've already posted the question in User Forum. vincs View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025042#4025042 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025042

19 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Still have insufficient separation of metadata

by adrian＠jboss.org

Also, there is no reason why the dependency name cannot be null. Ales added support for this to the MC metadata such that a null name means to match the interface of the property with a singleton implementator. (This is similar to the Nanocontainer approach to IOC). | <property name="TransactionManager"><inject/></property> | | or the equivalent annotation | | @Inject | public void setTransactionManager(TransactionManager tm) {} | But the same processing has not been added to the JMX injection handling. If it were, the error reporting would be better, e.g. cannot resolve the interface of the jmx attribute to a singleton. (Although that is not what was intended in this case :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025034#4025034 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025034

19 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Still have insufficient separation of metadata

by adrian＠jboss.org

"scott.stark(a)jboss.org" wrote : For example, the ServiceMetaData contains ServiceInjectionValueMetaData which has a transient dependency that can be non-serializable (apparently, I cannot remember now why I marked it as transient): | The dependency object is just a "name". Making it transient, breaks the ServiceInjectionValueMetaData. When I created the MC api, I left open the possiblity that names could be something other than String, e.g. I anticapted that we might want to use ObjectName directly when integrating with JMX. As it turns out, that would be difficult to implement, since different contexts won't be able to compare each other's names. So in the actual code, ObjectName's are turned into their string canonical form. I still like the idea of being able to use a structured name/id when this is understood by all users. Like any serializable contract, if a user uses a name that is not serializable then they won't be able to serialize the metadata. But that doesn't mean I'm convinced that we should enforce a name to be serializable since the user may not want to serialize the metadata. So basically, I don't see why the dependency field should be transient? It isn't in AbstractDependencyValueMetaData in the MC metadata (it reuses the value field from the super class). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025033#4025033 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025033

19 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - JPDL custom element attributes

by paolodt

It would be very useful to introduce in JPDL engine an API to handle custom attributes on process definition elements. It could be done in a very easy way adding support for custom xml namespace in JDPL. In this way it will possible to add custom attributes to annotate process elements (node, transition, task, etc). For example <process-definition xmlns="urn:jbpm.org:jpdl-3.1" xmlns:custom="http://stuff.com/custom" > <node node="node1" custom:attr1="x" custom:attr2="y" > : : </process-definition> This would be useful to express extra semantics in domain specific language. What do you think about? Regards, Paolo Di Tommaso View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025030#4025030 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025030

19 years, 1 month

1
0
0 / 0

[Design of JBoss Portal] - Adding a jar file to build file

by jihadaj

How can i add external jar file to jboss portal src 2.4 ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025023#4025023 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025023

19 years, 1 month

1
0
0 / 0

[Design of Security on JBoss] - Re: AS 4.2.0 binding to localhost

by scott.stark＠jboss.org

a) possibly. The testsuite setup would also need to run to lay down the default with security configured in accord with the testsuite. b) would have to be all jmx invokers and this would also break the testsuite. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024982#4024982 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024982

19 years, 1 month

1
0
0 / 0

[Design of Security on JBoss] - exception when run jboss-4.0.4 with the jboss federation sso

by charles751

help me! i installed jboss federation sso in jboss-4.0.4.GA as the jboss-sso-1.0CR1 readme.txt file step by step. when i performed: run -c default -b node1.jboss.com the jboss-4.0.4.GA console threw the following exception: 2007-03-05 13:32:38,906 DEBUG [org.jboss.deployment.SARDeployer] create operation failed for package file:/D:/jboss-4.0.4.GA/server/default/deploy/jboss-sso.sar/ org.jboss.deployment.DeploymentException: Error parsing the XML file: ; - nested throwable: (org.jboss.mx.util.JBossNotCompliantMBeanException: Error parsing the XML file: ) at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196) at org.jboss.system.ServiceController.install(ServiceController.java:226) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024980#4024980 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4024980

19 years, 1 month

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