[JBoss Tools] New message: "Re: JBoss Tools 3.1 Final!"
by Denis Golovin
User development,
A new message was posted in the thread "JBoss Tools 3.1 Final!":
http://community.jboss.org/message/531831#531831
Author : Denis Golovin
Profile : http://community.jboss.org/people/dgolovin
Message:
--------------------------------------------------------------
We have to keep separate update sites for JBossTools 3.0 and 3.1 because Eclipse doesn't support updates between 3.X releases:
1. updates/stable - for JBT 3.0.X for Eclipse 3.4.X
2. updates/stable/galileo - for JBT 3.1.X for Eclipse 3.5.X
It happens because update site structure is incompatible between 3.X releases. That's why if you're upgrading from JBoosTools 3.0 to 3.1. you have to do fresh install Eclipse + JBossTools and why JBossTools 3.1.0.GA update site has different URL.
So if JBossTools 3.0.4 is going to happen it will be available troug the same update site (1), the same for 3.1.1 releases, they'll go to (2).
I guess that you where using nightly builds of JBossTools. Nightly builds are published in updates/nightly area with version names like:
1. updates/nightly/3.1.0.CR1
2. updates/nightly/3.1.0.CR2
3. update/nightly/trunk
updates sites like (1) and (2) appear after branch is created for upcoming release.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/531831#531831
16 years, 4 months
[JBoss Messaging] New message: "Re: Sending message to JBOSS queue from WebSphere"
by Hitesh Patel
User development,
A new message was posted in the thread "Sending message to JBOSS queue from WebSphere":
http://community.jboss.org/message/531830#531830
Author : Hitesh Patel
Profile : http://community.jboss.org/people/sunil_patel
Message:
--------------------------------------------------------------
Here are the steps I followed (WebSphere needs some fix, so it will not work, not with 6.1 at least):
1. Created a queue in JBOSS server. Tested the queue successfully from command prompt and from within RAD by running a java program with following jar files provided by JBOSS.
jboss-remoting.jar
jboss-messaging-client.jar
jbossall-client.jar
jboss-aop.jar
javassist.jar
trove.jar
log4j.jar
2. Created a JMS provider (JBOSS Messaging Provider) in local WebSphere with Admin Console. Added all jar files mentioned in step 1 in the classpath for the provider.
3. Created a Queue connection factory in local WebSphere with Admin Console.
4. Created a queue (with external jndi name same as provided in step 1) in local WebSphere with Admin Console.
5. Wrote a servlet to test this by sending a message in local WebSphere with Admin Console.
6. Ran the servlet. Connection is successful but get exception "javax.jms.IllegalStateException: Isn't an XASession" while trying to create sender.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/531830#531830
16 years, 4 months
[jBPM] New message: "Re: Question About Forks and Modeling Rework Requests in jbpm4"
by Robert Moskal
User development,
A new message was posted in the thread "Question About Forks and Modeling Rework Requests in jbpm4":
http://community.jboss.org/message/531824#531824
Author : Robert Moskal
Profile : http://community.jboss.org/people/rmoskal
Message:
--------------------------------------------------------------
Let's say there was a parallel activity to frosting the cake. If we requested a rework from frosting to baking we would have to take the fork and do both frosting and this other activity again. Another way I want to say this is that if one branch after a fork goes back, they all must.
I was thinking of this in terms simply ending the execution on the other fork. Thats' what I was trying to do in the test case I attached. I send a signal to *state2* to take the rework path to *state1* and then I tried to track the down and kill the execution for *state3*.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/531824#531824
16 years, 4 months
[JNDI and Naming] New message: "Re: Resources injection in JBoss 5"
by jaikiran pai
User development,
A new message was posted in the thread "Resources injection in JBoss 5":
http://community.jboss.org/message/531823#531823
Author : jaikiran pai
Profile : http://community.jboss.org/people/jaikiran
Message:
--------------------------------------------------------------
Luca, welcome to the forums
Nice thing you are trying out there!
> morettoni wrote:
>
>
> Another solution talks about creating a file with this:
> > <?xml version="1.0" encoding="UTF-8"?>
> > <jndi:binding name="theConfig">
> > <java:properties xmlns:java="urn:jboss:java-properties" xmlns:xs="http://www.w3.org/2001/XMLSchema-instance" xs:schemaLocation="urn:jboss:java-properties resource:java-properties_1_0.xsd">
> > <java:property>
> > <java:key>remote.address</java:key>
> > <java:value>192.168.0.7</java:value>
> > </java:property>
> > <java:property>
> > <java:key>dumpinfo</java:key>
> > <java:value>1</java:value>
> > </java:property>
> > </java:properties>
> > </jndi:binding>
> ... but exploring the jndi tree I can't find any "theConfig" resource name! There are any solutions to this? Thanks!
>
>
1) That file isn't complete. What you need is this:
<?xml version="1.0" encoding="UTF-8"?>
<mbean code="org.jboss.naming.JNDIBindingServiceMgr"
name="jboss.apps:name=myapp">
<attribute name="BindingsConfig" serialDataType="jbxb">
<jndi:bindings xmlns:xs="http://www.w3.org/2001/XMLSchema-instance"
xmlns:jndi="urn:jboss:jndi-binding-service:1.0"
xs:schemaLocation="urn:jboss:jndi-binding-service resource:jndi-binding-service_1_0.xsd">
<jndi:binding name="theConfig">
<java:properties xmlns:java="urn:jboss:java-properties" xmlns:xs="http://www.w3.org/2001/XMLSchema-instance" xs:schemaLocation="urn:jboss:java-properties resource:java-properties_1_0.xsd">
<java:property>
<java:key>remote.address</java:key>
<java:value>192.168.0.7</java:value>
</java:property>
<java:property>
<java:key>dumpinfo</java:key>
<java:value>1</java:value>
</java:property>
</java:properties>
</jndi:binding>
</jndi:bindings>
</attribute>
</mbean>
2) Name this file to end with -service.xml (ex: myapp-service.xml) and place it in JBOSS_HOME/server/< servername>/deploy folder and start the server. You should be able to find "theConfig" jndi binding available under the Global namespace in JNDIView through jmx-console.
3) Finally to inject this, you will have to use the mappedName of the @Resource annotation. Like this:
@Resource(mappedName = "theConfig")
private Properties configProperties;
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/531823#531823
16 years, 4 months
[Beginner's Corner] New message: "Re: file size limit for downloading from a JBoss server?"
by Jim Schumm
User development,
A new message was posted in the thread "file size limit for downloading from a JBoss server?":
http://community.jboss.org/message/531812#531812
Author : Jim Schumm
Profile : http://community.jboss.org/people/jimsch
Message:
--------------------------------------------------------------
Hi Mike,
Thanks for your question. The problem is now solved. Apologies - I should have updated the thread but got side-tracked.
It turned out I needed to add a setting to my server.xml file in
jboss\server\default\deploy\jboss-web.deployer
The setting I needed was useSendFile="false" in
my connector.
The connector now reads
<Connector port="8080" address="${jboss.bind.address}"
maxThreads="250" maxHttpHeaderSize="8192"
emptySessionPath="true"
protocol="org.apache.coyote.http11.Http11NioProtocol"
enableLookups="false" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true"
compressableMimeType="text/html,text/css,text/xml,text/plain,application
/json,text/javascript"
compressionMinSize="300" compression="on" useSendfile="false" />
Reading this thread
http://www.mail-archive.com/users@tomcat.apache.org/msg51465.htmlmailto:/...
it seems that I must have been hitting the limit of my kernel memory.
I think then that setting useSendfile="false" ensures that all files, regardless of size, can be downloaded but that
files that could have already been downloaded with the default useSendfile="true" may take that little bit longer.
Best wishes,
Jim
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/531812#531812
16 years, 4 months
[jBPM] New message: "Re: Question About Forks and Modeling Rework Requests in jbpm4"
by Robert Moskal
User development,
A new message was posted in the thread "Question About Forks and Modeling Rework Requests in jbpm4":
http://community.jboss.org/message/531811#531811
Author : Robert Moskal
Profile : http://community.jboss.org/people/rmoskal
Message:
--------------------------------------------------------------
Ron:
Thanks for responding, let me draw out a slightly simpler process (what I call a pipeline) and I think my needs and my client's use cases will become clear.
Take a look this work flow for making cakes:
http://community.jboss.org/servlet/JiveServlet/showImage/2331/Screenshot-...
At any step in the process someone may discover that something went wrong and the cake has to go back for "rework". At any point past baking, another department may find a flaw in the baking and may send it back. The decorators may find that the frosting is imperfect and may send it back there. Once a cake is sent back in the pipeline it travels forward through all the steps again (even if nothing needs to be done, the department at least has to sign off on the cake). I modelled it the above way to avoid having to connect every activity to every activity . Every activity that can initiate a rework request has an outgoing transition to a common decision and the decision node has an outgoing transition to every node that can be a target. So you notice tha bakers can only be the target of a rework request and the boxers can only initiate them.
Really this is meant to give my client an overarching view of what is going on in their shop (the actual activity nodes are subprocesses of arbitrary complexity). These single path pipeline works fine inside of jbpm. The problem arose when we discovered that certain activities could go on in parallel (sorry my imagination fails me with regard to extending the example). In fact most of the use cases work for pipelines with forks. The only time it fails is if you fork then try to transition back to before the fork.
Hope this helps. I am appreciative of your time.
Regards,
Robert
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/531811#531811
16 years, 4 months
