Datasources: Driver binaries
by Heiko Braun
Since drives are added as modules, I assume this can not be managed from the console, right?
Which means that we will provide means to add datasource configuration baed on existing drivers configurations
that have to be preconfigured.
Ike
13 years
HornetQ subsystems in AS 7
by Brian Stansberry
Copied below is a discussion we had today on #jboss-as7 in IRC that I'm
copying here to get input from the HQ folks.
AS 7 currently has 2 HQ-related subsystems, "messaging" which provides
core HQ, and "jms" which brings in JMS spec compliance. The gist of the
discussion is 1) whether this separation is overly unintuitive and 2) if
it's necessary, is the name "messaging" for the core HQ subsystem too
likely to lead users to assume it's where JMS topic/queue creation is done.
The conversation is below. It carried on after the following; please see
http://echelog.matzon.dk/logs/browse/jboss-as7/1302040800 if you are
interested.
pilhuhn: Also I am astonished that Q s are present , but not Topics
[1:52pm] bstansberry: pilhuhn: there are topics in the jms subsystem
[1:53pm] bstansberry: the "messaging" subsystem is very oriented toward
core HornetQ
[1:54pm] bstansberry: Nihility: ^^^ reminds me of our discussion w/ paul
re: the JGroups subsystem, where we decided it was silly to give a
"generic" name to a subsystem that was not exposing a standard API
[1:55pm] bstansberry: same applies to subsystem=messaging
[1:55pm] pilhuhn: so Qs are in both? messaging and jms? feels strange
[1:55pm] Nihility: bstansberry: makes sense
[1:55pm] Nihility: bstansberry: sort of
[1:55pm] Nihility: bstansberry: another example is subsystem=web
[1:56pm] Nihility: bstansberry: which is jboss web
[1:56pm] bstansberry: well, that at least is exposing the Servlet spec
[1:56pm] dmlloyd: shared global bindings are a nasty little problem
[1:56pm] Nihility: i think our goal should just be to have subsystem names
[1:56pm] Nihility: that are intuitive easy to understand
[1:57pm] Nihility: jgroups vs group-communication is basically the same
to me
[1:57pm] dmlloyd: jgroups is unambiguous and concise imo
[1:57pm] bstansberry: yes, that's decided
[1:57pm] Nihility: yes
[1:57pm] dmlloyd: hornetq should be hornetq
[1:57pm] Nihility: the reason for messaging and jms is different
[1:57pm] pilhuhn: I think it needs to be clear that for an enduse, that
he wants to have a jms/queue and not a messaging/queue when doing jms
[1:58pm] dmlloyd: jms should be jms
[1:58pm] Nihility: they realy do have two subsystems
[1:58pm] dmlloyd: if there is such a generic notion
[1:58pm] bstansberry: right, so calling hornetq "messaging" is not intuitive
[1:58pm] Nihility: they have this notion of a lightweight topic
[1:58pm] bstansberry: people will gravitate toward it
[1:59pm] pilhuhn: Yeah leightweight.. it will float in the clouds
[1:59pm] Nihility: and thats what they think is a real messaging api
[1:59pm] pilhuhn: .oO( DId I win as BS-Bingo? )
[1:59pm] Nihility: jms is just something extra they do for the spec
[1:59pm] Nihility: with extra requirements etc
[1:59pm] Nihility: so its like a higher level layer
[1:59pm] Nihility: so they have core messaging
[1:59pm] Nihility: and they have jms
[1:59pm] Nihility: and togheter thats hornetq
[1:59pm] bstansberry: good point
[2:00pm] bstansberry: ok, no JIRA, at least not from me
[2:01pm] bstansberry: instead, a dev list thread and the HQ people can
deal with it
[2:01pm] pilhuhn: The admin that wants to use a MessageDrivenBean does
not really care about that separation
[2:02pm] Nihility: the separation is more because you can run hq without
starting the jms services
[2:02pm] Nihility: and they have separate configuration
[2:02pm] pilhuhn: yep
[2:02pm] Nihility: although you could collapse the two
[2:02pm] Nihility: emuckenhuber and i debated that for awhile
[2:02pm] Nihility: we had a hard time deciding
[2:03pm] pilhuhn: What I want to express (and that targets rather us
with JON and the console) is that for this said admin it needs to be
totally clear that he wants to go to subsys/jms/queue
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
13 years
RFC: write-attribute*s* / update-resource operation
by Heiko W.Rupp
Hi,
sometimes it is required to change multiple attributes of a node at once.
Currently this needs to be done via composite operation that contains
multiple write-attribute calls.
If would be nice if there would be an operation that allows to
update multiple attributes (sub elements?) of a resource at once.
pilhuhn
--
Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
Handelsregister: Amtsgericht München HRB 153243
Geschaeftsführer: Brendan Lane, Charlie Peters, Michael Cunningham, Charles Cachera
13 years
Nested steps for comp-op - intentional?
by Heiko W.Rupp
Hi,
the domain.ds test sends the following json to the DC:
{
"operation" : "composite",
"address" : [],
"steps" : [{
"operation" : "composite",
"steps" : [
Is it intentional that the outer steps consists of one step "op: comp" which then contains
the real steps?
Thanks
pilhuhn
13 years
Tagging user guide contents
by Heiko Braun
We've created a custom tag for Wiki articles that should go into the userguide at some point:
#jboss_7_userguide
If you happen to encounter contents that should be included in the userguide,
please make sure to tag it accordingly. For the time being all relevant articles can be found here:
all articles tagged #jboss_7_userguide
Thanks for your help.
Ike
13 years
Deploy to a domain
by ssilvert＠redhat.com
How do you deploy something to a domain? Can it be done currently?
I'm asking because I want to add this functionality to the console.
So if anyone also has info about the following please let me know:
Using the management API, how can I...
... query for the current deployments and status?
... deploy something?
... undeploy something?
Thanks,
Stan
13 years
Re: [jboss-as7-dev] Domain deployment fails
by Marchioni Francesco
Thanks for making this clear Brian,
Regards
Francesco
>Deployment to the domain is more complex, as once the content is added
>to the domain, there's a step to map it to server a server-group.
>The high level "deploy" command in the CLI is currently oriented toward
>standalone mode, and internally the CLI is handling it by asking the
>domain controller to do something that's not appropriate. We need to
fix
>that.
>Later today I'm going to write a wiki page re: deployment that will
>describe how to do domain deployments with lower level operations.
On 4/6/11 9:13 AM, Marchioni Francesco wrote:
> Hi all JBoss developers,
>
> I'm trying to deploy a .war artifact on a JBoss AS 7 domain using the
> cli interface.
>
> [localhost:9999 deploy] deploy Test.war
>
> And on the console:
>
> [Host Controller] 16:07:19,375 ERROR [org.jboss.as.controller]
> (pool-1-thread-23) operation ("deploy") failed - address:
> ([("deployment" => "Test.war")]): java.lang.IllegalStateException: No
> handler for deploy at address [("deployment"
>
> => "Test.war")]
>
> [Host Controller] at
>
org.jboss.as.controller.BasicModelController.execute(BasicModelControlle
r.java:254)
>
> [Host Controller] at
>
org.jboss.as.controller.BasicModelController.execute(BasicModelControlle
r.java:216)
>
> [Host Controller] at
>
org.jboss.as.controller.BasicModelController.execute(BasicModelControlle
r.java:77)
>
> [Host Controller] at
>
org.jboss.as.controller.SynchronousOperationSupport.execute(SynchronousO
perationSupport.java:88)
>
> [Host Controller] at
>
org.jboss.as.domain.controller.DomainModelImpl.executeForDomain(DomainMo
delImpl.java:329)
>
> [Host Controller] at
>
org.jboss.as.domain.controller.DomainControllerImpl$LocalDomainModelAdap
ter.execute(DomainControllerImpl.java:912)
>
> [Host Controller] at
org.jboss.as.domain.controller.DomainControllerImpl.e
>
> Has anyone managed to deploy an application domain-wide ?
>
> Thanks a lot
>
> Francesco
>
--------------------------------------------------------------------------------------------------------
Le informazioni trasmesse possono contenere documenti confidenziali e/o materiale riservato; sono
quindi da intendersi esclusivamente ad uso della persona e/o societa a cui sono indirizzate.
Qualsiasi modifica, inoltro, diffusione o altro utilizzo, relativo alle informazioni trasmesse, da parte
di persone e/o societa diversi dai destinatari indicati, e proibito ai sensi della legge 196/2003.
Qualora questa mail fosse stata ricevuta per errore, si prega di contattare il mittente e cancellarne
il contenuto.
--
Privileged/Confidential Information may be contained in this message. If you are not the addressee
indicated in this message (or responsible for delivery of the message to such person), you may not
copy or deliver this message to anyone. In such case, you should destroy this message and kindly
notify the sender by reply email. Please advise immediately if you or your employer does not consent
to Internet email for messages of this kind. Opinions, conclusions and other information in this
message that do not relate to the official business of my firm shall be understood as neither given
nor endorsed by it.
--------------------------------------------------------------------------------------------------------
13 years
Domain deployment fails
by Marchioni Francesco
Hi all JBoss developers,
I'm trying to deploy a .war artifact on a JBoss AS 7 domain using the
cli interface.
[localhost:9999 deploy] deploy Test.war
And on the console:
[Host Controller] 16:07:19,375 ERROR [org.jboss.as.controller]
(pool-1-thread-23) operation ("deploy") failed - address:
([("deployment" => "Test.war")]): java.lang.IllegalStateException: No
handler for deploy at address [("deployment"
=> "Test.war")]
[Host Controller] at
org.jboss.as.controller.BasicModelController.execute(BasicModelControlle
r.java:254)
[Host Controller] at
org.jboss.as.controller.BasicModelController.execute(BasicModelControlle
r.java:216)
[Host Controller] at
org.jboss.as.controller.BasicModelController.execute(BasicModelControlle
r.java:77)
[Host Controller] at
org.jboss.as.controller.SynchronousOperationSupport.execute(SynchronousO
perationSupport.java:88)
[Host Controller] at
org.jboss.as.domain.controller.DomainModelImpl.executeForDomain(DomainMo
delImpl.java:329)
[Host Controller] at
org.jboss.as.domain.controller.DomainControllerImpl$LocalDomainModelAdap
ter.execute(DomainControllerImpl.java:912)
[Host Controller] at
org.jboss.as.domain.controller.DomainControllerImpl.e
Has anyone managed to deploy an application domain-wide ?
Thanks a lot
Francesco
--------------------------------------------------------------------------------------------------------
Le informazioni trasmesse possono contenere documenti confidenziali e/o materiale riservato; sono
quindi da intendersi esclusivamente ad uso della persona e/o societa a cui sono indirizzate.
Qualsiasi modifica, inoltro, diffusione o altro utilizzo, relativo alle informazioni trasmesse, da parte
di persone e/o societa diversi dai destinatari indicati, e proibito ai sensi della legge 196/2003.
Qualora questa mail fosse stata ricevuta per errore, si prega di contattare il mittente e cancellarne
il contenuto.
--
Privileged/Confidential Information may be contained in this message. If you are not the addressee
indicated in this message (or responsible for delivery of the message to such person), you may not
copy or deliver this message to anyone. In such case, you should destroy this message and kindly
notify the sender by reply email. Please advise immediately if you or your employer does not consent
to Internet email for messages of this kind. Opinions, conclusions and other information in this
message that do not relate to the official business of my firm shall be understood as neither given
nor endorsed by it.
--------------------------------------------------------------------------------------------------------
13 years, 1 month
