[Design of JBoss Web Services] - Re: Simplify deploy/undeploy cycles for different stacks
by thomas.diesler@jboss.com
AFAIKS client jars would be the problem with this approach
| <!-- CLIENT JARS -->
| <copy todir="${jboss501.home}/client" overwrite="true">
| <fileset dir="@{stacklibs}">
| <include name="jboss-jaxrpc.jar"/>
| <include name="jboss-jaxws.jar"/>
| <include name="jboss-jaxws-ext.jar"/>
| <include name="jboss-saaj.jar"/>
| <include name="jbossws-client.jar"/>
| </fileset>
| <fileset dir="@{thirdpartylibs}">
| <include name="policy.jar"/>
| <include name="jaxb-api.jar"/>
| <include name="jaxb-impl.jar"/>
| <include name="jaxb-xjc.jar"/>
| <include name="jaxws-tools.jar"/>
| <include name="jaxws-rt.jar"/>
| <include name="stax-ex.jar"/>
| <include name="streambuffer.jar"/>
| <include name="wsdl4j.jar"/>
| </fileset>
| </copy>
| <copy todir="${jboss501.home}/lib" overwrite="true">
| <fileset dir="@{thirdpartylibs}">
| <include name="jaxb-api.jar"/>
| <include name="jaxb-impl.jar"/>
| </fileset>
| </copy>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130655#4130655
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130655
18 years, 1 month
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2 Management Interfaces
by timfox
I won't pretend I have fully got my head around this yet. :)
To summarise my understanding so far:
JBM 2.0 will have a simple POJO based management API.
What we would like to do is:
1) Expose that API as a web interface (I'm guessing this is what Charles demo'd at JBW)
2) Also expose that API as a non web interface (is this Swing?) which can be controlled from a remote client.
The management stuff needs to know what attributes and operations we want to expose - I'm assuming that's the purpose of the plugin.
Given a plugin, I'm assuming the management layer is smart enough to be able to provide a web or non web (remote) interface. (This is just a view on the same underlying API).
We want to avoid non standard JDK annotations in our POJOs to define management interfaces, since JBM is also designed to be included in Joe Bloggs third party project and we don't want to force them to pull in an unnecessary build time dependency on other (MC) jboss libraries.
If all this is to run in the MC, I am also interested in what runtime dependencies are needed for this all to function.
So far I have gleaned:
1) JBossWeb
2) Seam
3) Remoting 2
4) Profile service (?)
Anything else?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130641#4130641
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130641
18 years, 1 month
[Design of POJO Server] - Are these properties/operations for DS and JMS correct/neede
by bytor99999
The following properties show up under ComponentTypes Datasource/LocalTX,NoTX, XAtx, are they all needed, are some not valid as tags within say a <local-tx-datasource> tag in a -ds.xml file.
rar-name
connection-definition
jmx-invoker-name
prefill
background-validation
background-validation-minutes
validate-on-match
use-strict-min
statistics-formatter
isSameRM-override-value
track-connection-by-tx
config-property
depends
metadata
type-mapping
localTransactions
(XA Only property)
xa-resource-timeout
Under JMS I see the following two statistic properties, they are complex types, Maps with keys that we would consider a statistic. However, some of the keys are for other statistic properties already defined for Destinations.
Statistic properties in question
messageCounter the properties within it.
messageStatistics the properties within it.
Are the operations correct for Topics and Queues
Where are some of the operations like listDurableSubscriptions or listNonDurableSubscriptions, do both Destination type now have the same identical set of operations?
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130610#4130610
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130610
18 years, 1 month