Hi yary,
what you mean attach the source code? i got the sampe problem with you.. can
you explain it to me... how you fixed it?
thank's
BR
Ali Bastomi
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4227374#4227374
Reply to the post :
Hi Good Day people,
I'm been trying to solve this problem on the past few days but got no luck on
the finding the solution.
I tried to ask mr. google to find some reference but I cannot find the the
right one or something related to my problem, thats why I post now the problem
on the forum.
http://www.jboss.org/index.html?module=bbop=viewtopicp=4193509#4193509
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4227378#4227378
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4227378
I am actually set the key as well, it is there in the code
keyNode.put(ExpirationAlgorithmConfig.EXPIRATION_KEY, expTime);
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4227391#4227391
Reply to the post :
You can checkout it's from svn repository,
https://anonsvn.jboss.org/repos/jbosstools/trunk/hibernatetools/
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4227399#4227399
Reply to the post :
http://www.google.nl/search?q=hibernate+coherence+oracleie=utf-8oe=utf-8aq=trls=org.mozilla:nl:officialclient=firefox-a
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4227398#4227398
Reply to the post :
by reading what I stated before. Your variable contains the string you passed
to it, including the #{.} and by parsing it with the jBPM EL resolver it
will be filled.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4227401#4227401
Reply to the post :
OK, I saw that...
But I dont known how to use ServerPeer to deploy topic.
If someone has an example.
Thanks
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4227407#4227407
Reply to the post :
You can have a look at the JBM examples source, especially this file:
examples/common/src/org/jboss/example/jms/common/Util.java
the deployQueue() method.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4227408#4227408
Reply to the post :
Thank you again Peter,
always fast and accurate.
Antonello
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4227415#4227415
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4227415
___
I try that example yesterday, and always I got
| Unable to find operation createQueue(java.lang.String,java.lang.String)
|
This is my example:
| package com.jboss.test;
|
| import java.util.Properties;
|
| import javax.management.MBeanServerConnection;
| import
Hi,
Thanks a lot for d reply ...It really worked !!!
and i was successfully able to embed d portlet into d portal...
regards
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4227416#4227416
Reply to the post :
Sorry, the operation name should be 'deployQueue', not 'createQueue'.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4227420#4227420
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4227420
I'd need to double check what was available in AS 4.2.2, I think the -t 2.1
option was later disabled because the implementation of JAX-WS 2.1 was not
complete yet.
For sure you can use the 2.1 target starting from JBossWS Native 3.1.0.GA as
the JAX-WS 2.1 has been completed there.
Otherwise
Works
Thanks
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4227424#4227424
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4227424
___
jboss-user mailing list
Hi,
I think the JSF library feature is only for defining the JSF standard
implementation, but not for libraries built upon JSF.
So, you need two steps:
1) create a JSF library in eclipse with the option server supplies
implementation (JBoss contains Mojarra) and choose your JBoss server
jaikiran wrote : What is the reason for keeping these properties outside the
.ear? Is it because you will have to unzip the archive to make any changes to
the properties? If yes, then have a look at the exploded deployment option
http://www.jboss.org/community/docs/DOC-9719. That way you can
Hi,
give jbosssx-as-client.jar a try, this one contains your class in 5.0.1.
Best regards
Wolfgang
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4227433#4227433
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4227433
Handled in your other post
http://www.jboss.org/index.html?module=bbop=viewtopict=154538
Best regards
Wolfgang
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4227436#4227436
Reply to the post :
You can place those property files in %JBOSS_HOME%/server/ serverName/conf
folder which by default is in the classpath. You can then access those files in
the code, something along these lines:
InputStream is =
this.getClass().getClassLoader().getResourceAsStream(myprops.properties);
|
It seems mail node is blocking, I just tried. I would like to handle when the
sending of a mail fails. I saw that this node can handle exceptions, so I added
one :
mail-node name=notifier_valideur to=#{demande.valideur.email}
template=task-assign
| subject#{mailSubject}/subject
Replys are in your other post:
http://www.jboss.org/index.html?module=bbop=viewtopict=154538
Please don't cross-post
Best regards
Wolfgang
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4227442#4227442
Reply to the post :
Hi,
the problem is that i don't have the permission to make changes on the DB
because it's a LIVE/Production DB. So problems with releases/changes and so on.
I tried to access now my attributs via @NamedQuery like this:
SELECT r.roadPK.origin.iata,r.roadPK.destination.iata, r.availabilityMethod
We finally were able to reproduce this issue. This issue arises because of
Classpath entries in MANIFEST.MF of the ejb jar files. Looking at the
MANIFEST.MF files your application has set the Classpath attribute to point to
other ejb jar deployments. This leads to incorrect handling of the bean
24 matches
Mail list logo
