[JBoss Web Services] - JBossWS - Supported Target Containers
by Alessio Soldano
Alessio Soldano [https://community.jboss.org/people/asoldano] modified the document:
"JBossWS - Supported Target Containers"
To view the document, visit: https://community.jboss.org/docs/DOC-13569
--------------------------------------------------------------
The following tables show the JBoss Application Server (community) versions JBossWS has been tested with before the release.
h2. Latest JBossWS versions
|| AS Version -> || 5.0.0 || 5.0.1 || 5.1.0 || 6.0.0.M1 || 6.0.0.M3 || 6.0.0.CR1 || 6.0.0.Final || 7.0.0 || 7.0.1 || 7.0.2 || 7.1.0 || 7.1.1 || 7.1.2 ||
| jbossws-cxf-3.1.2 | X | X | X |
|
|
|
|
|
|
|
|
|
|
| jbossws-cxf-3.2.0 | X | X | X |
|
|
|
|
|
|
|
|
|
|
| jbossws-cxf-3.2.1 | X | X | X |
|
|
|
|
|
|
|
|
|
|
| jbossws-cxf-3.2.2 | X | X | X | X |
|
|
|
|
|
|
|
|
|
| jbossws-cxf-3.3.0 |
| X | X |
| X |
|
|
|
|
|
|
|
|
| jbossws-cxf-3.3.1 |
| X | X |
| X |
|
|
|
|
|
|
|
|
| jbossws-cxf-3.4.0 |
| X | X |
|
| X |
|
|
|
|
|
|
|
| jbossws-cxf-3.4.1 |
|
|
|
|
|
| X |
|
|
|
|
|
|
| jbossws-cxf-4.0.0 |
|
|
|
|
|
|
| X | X | X |
|
|
|
| jbossws-cxf-4.0.1 |
|
|
|
|
|
|
| X | X | X |
|
|
|
| jbossws-cxf-4.0.2 |
|
|
|
|
|
|
|
| X | X | X |
|
|
| jbossws-cxf-4.1.0 |
|
|
|
|
|
|
|
|
|
| X | X | X |
|| AS Version -> || 5.0.0 || 5.0.1 || 5.1.0 || 6.0.0.M1 || 6.0.0.M3 || 6.0.0.CR1 || 6.0.0.Final || 7.0.0 || 7.0.1 || 7.0.2 || 7.1.0 ||
| jbossws-native-3.1.2 | X | X | X |
|
|
|
|
|
|
|
|
| jbossws-native-3.2.0 | X | X | X |
|
|
|
|
|
|
|
|
| jbossws-native-3.2.1 | X | X | X |
|
|
|
|
|
|
|
|
| jbossws-native-3.2.2 | X | X | X | X |
|
|
|
|
|
|
|
| jbossws-native-3.3.0 |
| X | X |
| X |
|
|
|
|
|
|
| jbossws-native-3.3.1 |
| X | X |
| X |
|
|
|
|
|
|
| jbossws-native-3.4.0 |
| X | X |
|
| X |
|
|
|
|
|
| jbossws-native-3.4.1 |
|
|
|
|
|
| X |
|
|
|
|
| jbossws-native-4.0.0 |
|
|
|
|
|
|
| X | X | X |
|
| jbossws-native-4.0.1 |
|
|
|
|
|
|
| X | X | X |
|
| jbossws-native-4.0.2 |
|
|
|
|
|
|
|
| X | X | X |
h2. Legacy / old JBossWS versions
|| AS Version -> || 4.0.5 || 4.2.1 || 4.2.2 || 4.2.3 || 5.0.0
Beta4 || 5.0.0
CR1 || 5.0.0
CR2 || 5.0.0 || 5.0.1 ||
| jbossws-native-2.0.1 | X | X |
|
|
|
|
|
|
|
| jbossws-native-2.0.2 | X | X | X |
|
|
|
|
|
|
| jbossws-native-2.0.3 | X | X | X |
|
|
|
|
|
|
| jbossws-native-3.0.0 |
| X | X |
| X |
|
|
|
|
| jbossws-native-3.0.1 |
| X | X |
| X |
|
|
|
|
| jbossws-native-3.0.2 |
| X | X |
| X | X |
|
|
|
| jbossws-native-3.0.3 |
|
| X | X |
| X | X |
|
|
| jbossws-native-3.0.4 |
|
| X | X |
|
| X |
|
|
| jbossws-native-3.0.5 |
|
| X | X |
|
|
| X |
|
| jbossws-native-3.1.0 |
|
|
| X |
|
|
| X | X |
| jbossws-native-3.1.1 |
|
|
| X |
|
|
| X | X |
|| AS Version -> || 4.0.5 || 4.2.1 || 4.2.2 || 4.2.3 || 5.0.0
Beta4 || 5.0.0
CR1 || 5.0.0
CR2 || 5.0.0 || 5.0.1 || 5.1.0 || 6.0.0.M1 || 6.0.0.M3 ||
| jbossws-metro-3.0.0 |
|
| X |
| X |
|
|
|
|
|
|
|
| jbossws-metro-3.0.1 |
|
| X |
| X |
|
|
|
|
|
|
|
| jbossws-metro-3.0.2 |
|
| X |
| X | X |
|
|
|
|
|
|
| jbossws-metro-3.0.3 |
|
| X | X |
| X | X |
|
|
|
|
|
| jbossws-metro-3.0.4 |
|
| X | X |
|
| X |
|
|
|
|
|
| jbossws-metro-3.0.5 |
|
| X | X |
|
|
| X |
|
|
|
|
| jbossws-metro-3.1.0 |
|
|
| X |
|
|
| X | X |
|
|
|
| jbossws-metro-3.1.1 |
|
|
| X |
|
|
| X | X |
|
|
|
| jbossws-metro-3.2.0 |
|
|
|
|
|
|
| X | X | X |
|
|
| jbossws-metro-3.2.1 |
|
|
|
|
|
|
| X | X | X |
|
|
| jbossws-metro-3.2.2 |
|
|
|
|
|
|
| X | X | X | X |
|
| jbossws-metro-3.3.0 |
|
|
|
|
|
|
|
| X | X |
| X |
| jbossws-metro-3.3.1 |
|
|
|
|
|
|
|
| X | X |
| X |
|| AS Version -> || 4.0.5 || 4.2.1 || 4.2.2 || 4.2.3 || 5.0.0
Beta4 || 5.0.0
CR1 || 5.0.0
CR2 || 5.0.0 || 5.0.1 ||
| jbossws-cxf-3.0.0 |
|
| X |
| X |
|
|
|
|
| jbossws-cxf-3.0.1 |
|
| X |
| X |
|
|
|
|
| jbossws-cxf-3.0.2 |
|
| X |
| X | X |
|
|
|
| jbossws-cxf-3.0.3 |
|
| X | X |
| X | X |
|
|
| jbossws-cxf-3.0.4 |
|
| X | X |
|
| X |
|
|
| jbossws-cxf-3.0.5 |
|
| X | X |
|
|
| X |
|
| jbossws-cxf-3.1.0 |
|
|
| X |
|
|
| X | X |
| jbossws-cxf-3.1.1 |
|
|
| X |
|
|
| X | X |
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-13569]
Create a new document in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
13 years, 6 months
[JBoss Tools] - Use single folder for WebResources, avoid copying static resources to standalone/deployments/
by Rainer Zufall
Rainer Zufall [https://community.jboss.org/people/mmg1] created the discussion
"Use single folder for WebResources, avoid copying static resources to standalone/deployments/"
To view the discussion, visit: https://community.jboss.org/message/764667#764667
--------------------------------------------------------------
After many years coding with Java EE and JBoss, there is still a advantage when using PHP+Apache/Nginx/XAMPP: immediate visiblity of changes on static web resources (HTML, JS, CSS). The reason is clear: everything is in a *single* folder, PHP files doesn't need to be compiled/recompiled. But static resources doesn't need to be recompiled, so why not let JBoss directly serve static resource instaed of let Eclipse copying them to a secondary folder?
*PROBLEM*
Eclipse *tries* to detect changes in Java classes and static web resources in WebContent (HTML, JS, CSS), but in many cases it takes many seconds until modifications on static resources in WebContent\ are visible on JBoss.
I noticied that Eclipse *copies* folder WebContent\ to JBOSS\standalone\deployments\ when it detects changes. In my case the folders are c:\Users\dell\workspace\DynamicWeb\WebContent\ and d:\software\jboss7.1.1Final\standalone\deployments\DynamicWeb.war\.
The problem is *not* that Eclipse is not smart enough to detect changes immediately (is there no inotify in Windows 7?), but that there are two *seperate* folders that it needs to copy/synchronize.
*SOLUTION*
Why not let JBoss AS directly serve static resources from c:\Users\dell\workspace\DynamicWeb\WebContent\ to avoid introducing the lag introduced by copying folders? This avoids the need for a second folder in JBOSS\standalone\deployments\DynamicWeb.war\
When there is only a single folder, there is no need to copy or redeploy a project when only simple static resources (HTML, JS, CSS) changed. Only when Java classes are changes, but that's OK and not avoidable.
Also, I don't understand why the server adapter "JBossAS Tools" uses manual deploy with "touch DynamicWeb.war.dodeploy" instead of directly using the JBoss API to deploy and make changes visible?
*PREQUISITES*
I downloaded and extracted fresh copies of "Eclipse IDE for Java EE Developers" and "JBoss AS Brontes 7.1.1Final". I extracted JBoss AS in d:\software\jboss7.1.1Final\.
In Eclipse I switched to the "Java EE" perspective and addedd JBoss as a new Server. For this I needed to download a new adapter called "JBossAS Tools". I didn't install complete JBoss Tools for Eclipse.
I created a new "Dynamic Web Project" in Eclipse. The project files are located in c:\Users\dell\workspace\DynamicWeb\. I added the project ("Add and Remove") to the JBoss AS.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/764667#764667]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 6 months
[jBPM] - Unable to fire rules before and after human task using same rule flow group
by Sameer K
Sameer K [https://community.jboss.org/people/0sameerk0] created the discussion
"Unable to fire rules before and after human task using same rule flow group"
To view the discussion, visit: https://community.jboss.org/message/751823#751823
--------------------------------------------------------------
Hi I am newbie to jbpm.
I have a process as below
start-->rule task1-->human task1-->rule task2-->human task2-->end
I am using a knowledge session which is singleton(handled in code).
I am adding AgendaEventListener to session and in afterRuleFlowGroupActivated method executing fireallrules.
Also, I have added kcontext.getKnowledgeRuntime().insert(kcontext.getProcessInstance()); in human task1 on exit action.
Now when i am executing the process and if i provide two different rule flow groups in human task 1 and human task 2 then both the rule task are getting executed.
But when i use same rule flow group then process gets stuck on rule task, it doesnt move further as rules are not executed.
Please throw some pointers on what needs to be done.
Can i reactivate a rule flow group in any way?
Also in same session i am unable to fire same rule flow group for second process as well, which means my rule flow group is executing only once.
I know some prob from my end, any help would be appreciated.
JFYI the rule doesnt contain any thing which will manipulate the flow, its a simple when then condition and in then condition i have added a println.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/751823#751823]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 6 months
