data聽聽 The data directory is avaliable for use by services that want to store cotent in the file system.
deploy聽 The delploy dirctory is the default location the hot deployment service looks to for dynamic deployment content. This may be overridden through the URLDeployScanner URLs attribute.
log聽聽聽聽 The log directory is the directory log files are wrriten to. Thie may be overridden through the conf/log4j.xml configuration file.
tmp聽聽聽聽 The tmp directory is used by JBoss to store temporarily files such as unpacked deployments.
Drools杞Щ鍒癑Boss瀵規瘡涓漢鏉ヨ鏄竴浠跺ソ浜嬫儏錛屾病鏈変換浣曟潯浠跺湴錛屾牳蹇僁rool寮鍙戜漢鍛樿冭檻嫻佺▼騫朵笖鎵鏈夐兘鏇村揩涔愮殑鎯呭艦銆?BR>
Rule engines are a specialised field, this is recognised by JBoss, and they trust us as the experts so we retain full control of development. I now get to work full time on Drools and we will hopefully be hiring another full time Drools developer. Bob McWhirter will continue to be involved in Drools, in an official JBoss capacity under a part time basis, as he continues to have other responsibilities. This will really accelerate the development process; which benefits everyone.
Rule寮曟搸鏄竴涓笓闂ㄧ殑棰嗗煙錛岃繖鏄JBoss鎵胯錛屽茍涓斿畠浠俊浠繪垜浠綔涓轟笓瀹訛紝鎵浠ユ垜浠繚鐣欐墍鏈夌殑寮鍙戞帶鍒躲傛垜鐜板湪寮濮嬪湪Drools涓婂叏鑱屽紑鍙戝茍涓旀垜浠皢甯屾湜闆囦劍鍏朵粬鍏ㄨ亴鐨凞rools寮鍙戣呫侭ob McWhirter灝嗙戶緇繚鎸佸湪Drools,鍦ㄤ竴涓畼鏂圭殑JBoss鍦頒綅 under a part time basis,鎵浠ヤ粬緇х畫鎷ユ湁鍏朵粬璐ｄ換銆備粬浠皢鐪熸鐨勪績榪涘紑鍙戞祦紼嬶紱鎴戜滑鏀剁泭浜庢瘡涓漢銆?/P>
Drools will continue to work as a standalone product, as part of the JBoss JEMS stack. We will of course work on great JBoss AS integration, especially with jBPM - however we will continue to fully support other AS. I want Drools to be used absolutely everywhere and will do everything I can to achieve this; I want NO artificial barriers to adoption - this has always been important to me and the main reason for not going LGPL. The license will stay BSDish, although we may change it to a standardised BSD/ASF/MIT license ?this has been planned for a while and will help to avoid confusion.
Drools灝嗙戶緇綔涓轟竴涓嫭绔嬬殑欏圭洰宸ヤ綔錛屼綔涓篔Boss JEMS stack鐨勪竴閮ㄥ垎銆傛垜浠皢褰撶劧緇х畫宸ヤ綔JBoss AS 闆嗘垚錛岀壒鍒槸jBPM-鐒惰屾垜浠皢緇х畫鍏ㄩ潰鏀寔鍏朵粬AS.鎴戞兂璁〥rools鐢ㄦ潵琚嬌鐢ㄧ粷瀵規瘡涓湴鏂瑰茍涓斿仛鎴戝彲浠ュ幓瀹屾垚榪欎釜鐨勪換浣曚簨鎯咃紱鎴戞兂娌℃湁鍋囩殑闅滅鏉ラ噰鐢?-榪欐繪槸瀵規垜鏉ヨ寰堥噸瑕佸茍涓旀病鏈夎繘琛孡GPL鐨勪富瑕佸師鍥犮傝繖涓猯icense浠嶇劧閫楃暀鍦˙SDish,铏界劧鎴戜滑鍙互淇敼浠栨垚涓涓爣鍑嗗寲鐨凚SD/ASF/MIT 鐨刲icense?榪欏凡緇忚鍒掍簡涓孌墊椂闂村茍涓斿府鍔╂垜浠伩鍏嶆販涔便?/P>
Now that Drools is part of JBoss we can work on strong jBPM integration. We will bring standardised and easily understandable solutions to Workflow/BPM and Business Rules integration to the masses. I have already met with Tom Baeyens and we have identified some initial areas to work on for our first product release in Q1 2006. This is exciting work and will provide new ways of being able to build better affordable solutions without the high costs of existing specialised systems.
On a more personal note neither I nor Bob McWhirter are corporate type people, in fact Bob is famous for it!!! I would not have joined JBoss without full autonomy in an environment that would fully support my vision and the Drools community. We expected JBoss to take bully boy tactics in negotiations; however they were quite the contrary - this was unexpected and very refreshing and one of the key factors in my decision. Throughout the entire process they were surprisingly flexible; they listened to all our concerns and responded supportively - this was especially demonstrated in licensing talks, I hope the community takes note of that. While JBoss would have liked us to LGPL they respected our reasoning and never put any undue pressure on us. Since joining I have been continually asked about community feedback and response from all key JBoss people, Marc Fleury has taken a personal interest in this and repeatedly asked me if there is anything more he can do. This concern has been truly genuine and very much appreciated by me. Luckily the response has been great; we have had overwhelmingly positive feedback, especially once we clarified the licensing.
It would take 24+ months for a small company without an existing track record or infrastructure to try and build a strong brand around Drools, with all the support/consultancy/training/partner infrastructure that is needed for enterprise systems - this is a huge risk and one that I and Iterion were very much aware of. With JBoss we can achieve these in 6 months to a far greater effect, with negligible risk; as JBoss depends heavily on partners this will result in a larger ROI, due to scaling, with far less risk for them.
鍘熸枃鍦板潃錛?A >http://blogs.codehaus.org/people/mproctor/archives/001192_drools_joins_jboss.html