Thanks for the link. I was aware of this wiki page.
But there is something unclear to me:
If you have a handle to a remote connectionFactory, how can you get a handle to
a queue running in a remote server. Is this automatically done in the correct
JNDI namespace (the remote server one) or are
I am using an EJB3 MessageDrivenBean using the activation-config property
destination and destinationType
Can the destination be reconfigured as a resource reference in jboss.xml
deployment descriptor? This is more an EJB3 question, but perhaps you know. Or
should i use a different strategy to
Hi,
No i wanted to implement a JBoss messaging client talking to a JBM clustered
server without installing a Jboss Messaging implementation on the server (just
throwing jboss-messaging.jar in the lib dir).
But I solved this part using remote JNDI lookup on the cluster. What is not
mentioned in
I am using JBoss 4.2.2GA and JBoss Message 1.4.SP3
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4129196#4129196
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4129196
___
Hi Everybody
I have been playing with JBoss Messaging for a few days and want to achieve
something which i cannot get to work:
The idea is the following:
Have a JBoss Appserver procuce message to a clustered JBoss Mesaging
implementation via JCA RA adapter connected to teh remote cluster. I
Ah i have the same issue!
In my case the processdefinition files are not stored in the root or the par
but in classes/{processname}
I am using the latest 3.2 GA JPDL suite
Regards Karl de Boer
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4048687#4048687
I have not played yet with the JbpmNavigationHandler, but i am familiar with
Trinidad = (ADF Faces). You should use the default-render-kit-id tag in
faces-config.xml and not the view-handler element.
See the trinidad frequently asked questions about use trinidad in cobination
with facelets, if
The error was due to renaming the simple process. If you donto start with a
default simple process the par is generated correctly
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4048705#4048705
Reply to the post :
We are intending to use BPM on top of a (partly existing) SOA Architecture.
The BPEL standard has no provisioning for Workflow. A lot of BPEL products
extend the standard to incorporate this.
I think jBPM is a far better solution for this. But for service orchestration
BPEL is a good option
And i forgot to mention that we indeed have many tasks for users. The
webservice orchestration part is in our case less important. So if web service
orchestration is more important than managing heman tasks it would be a good
idea to do the oppoisite (intgrate jBMP human tasks in a BPEL
Oh wonderfull!
The basic scenario is this: I want an application to write locally into a non
persistent JMS queue (In fact a log4J queue appender). Logging in this way is
fast and not depending on network availablitly. However i want to access the
log messages on a central server. Therefore i
According to the 1.2 GA User Guide a messaging bridge is included.
However i cannot find any documentation how to set this up.
Is it included or will this be a feature of 1.2.1?
I have tried to make a bridge myself (in 1.2 CR1) using an MDB in JBoss 405 and
two JCA Connectionfactories (one local
Thanks for sharing your thoughts. But i am using webservices based upon
servlets, because we use a WSDL first approach (specify the contract first with
xml schema support). The generated code with WSCompile / WSTools generates
servlet based endpoints. SO i am not using annotiations nor ejbs.
I finally managed to get the username token profile stuff working.
It ends up in the endpoint. But for Servlet Based Endpoints (perhaps also for
ejb based endpoints) it seems that noting happens with the username and
password. I had expected the JAAS Module associated with the webapp to be
I did some research in the JBoss WS 103 Sources.
It appears that the username token profile is partly supported.
The user and password are added to the soap header when the password are added
to the call or proxy object
However password type attribute and password encoding is not support.
Hi Jason,
what about passwords, the nonce and timestamp elements which are also part of
the Username token profile 1.0 spec?
And last: what username is added to the soap header. Where does it come from?
We need to support the username token profile standard and the clients are not
alwasy
I am suprised that this is related to clustering.
What i would like to see (and expected) is the following:
Always write and read from a local queue and the distributed channel forwards
the message transparently to the queye on the target node (or cluster). So the
messages can be read locally
17 matches
Mail list logo