[Installation, Configuration & Deployment] - Re: Exploded WebModul: Can web-uri point outside of jboss?
by rogerdengcn
Thanks Thomasmarkus 's patch, It works very well for exploded ear. But I want to deploy a exploded war with web-uri point to directory outside of the ear file. I changed the code from 256 line of EARDeployer, it works for me. Hope the later JBoss AS release support this feature, it's very important if application want to support more than one J2EE AS(sicne other J2EE AS have such feature, even it is not J2EE mandatory feature).
| // if( nestedURL == null )
| // throw new DeploymentException("Failed to find module file: "+fileName);
| // sub = new DeploymentInfo(nestedURL, di, getServer());
|
| if( nestedURL == null ) {
| File f = new File(fileName);
| if (f.exists())
| {
| sub = new DeploymentInfo(f.toURL(), di, getServer());
| } else {
| throw new DeploymentException("Failed to find module file: "+fileName);
| }
| } else {
| sub = new DeploymentInfo(nestedURL, di, getServer());
| }
|
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030076#4030076
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030076
19Â years, 1Â month
[JBossCache] - JDBCCacheLoader config
by rocken7
Using JBossCache v1.4.0.SP1 ... It seems JDBCCacheLoader is never called, the jbosscache table is always empty, the logs seem to indicate the cache is enabled ...
What gives?
| 2007-03-20 16:55:37,669 INFO [org.hibernate.cfg.SettingsFactory] Query language substitutions: {}
| 2007-03-20 16:55:37,669 INFO [org.hibernate.cfg.SettingsFactory] JPA-QL strict compliance: enabled
| 2007-03-20 16:55:37,669 INFO [org.hibernate.cfg.SettingsFactory] Second-level cache: enabled
| 2007-03-20 16:55:37,669 INFO [org.hibernate.cfg.SettingsFactory] Query cache: enabled
| 2007-03-20 16:55:37,669 INFO [org.hibernate.cfg.SettingsFactory] Cache provider: org.jboss.ejb3.entity.TreeCacheProviderHook
| 2007-03-20 16:55:37,669 INFO [org.hibernate.cfg.SettingsFactory] Optimize cache for minimal puts: disabled
| 2007-03-20 16:55:37,669 INFO [org.hibernate.cfg.SettingsFactory] Structured second-level cache entries: disabled
| 2007-03-20 16:55:37,669 INFO [org.hibernate.cfg.SettingsFactory] Query cache factory: org.hibernate.cache.StandardQueryCacheFactory
|
| 2007-03-20 16:55:05,824 DEBUG [org.jboss.system.ServiceCreator] Created bean: jboss.cache:service=EJB3EntityTreeCache
|
<?xml version="1.0" encoding="UTF-8"?>
| <server>
|
| <!-- ==================================================================== -->
| <!-- Defines TreeCache configuration -->
| <!-- ==================================================================== -->
| <mbean code="org.jboss.cache.TreeCache" name="jboss.cache:service=EJB3EntityTreeCache">
| <depends>jboss:service=Naming</depends>
| <depends>jboss:service=TransactionManager</depends>
| <!--<depends>jboss.jca:service=DataSourceBinding,name=DefaultDS</depends>-->
|
| <!-- uncomment next three statements if using JGroups multiplexer,
| requires JGroups 2.3 or later, JBossCache 1.4 or later -->
| <!--
| <depends>jgroups.mux:name=Multiplexer</depends>
| <attribute name="MultiplexerService">jgroups.mux:name=Multiplexer</attribute>
| <attribute name="MultiplexerStack">fc-fast-minimalthreads</attribute>
| -->
|
| <!-- Configure the TransactionManager -->
| <attribute name="TransactionManagerLookupClass">org.jboss.cache.JBossTransactionManagerLookup</attribute>
|
| <!--
| Node locking level : SERIALIZABLE
| REPEATABLE_READ (default)
| READ_COMMITTED
| READ_UNCOMMITTED
| NONE
| -->
| <attribute name="IsolationLevel">REPEATABLE_READ</attribute>
|
| <!-- Valid modes are LOCAL
| REPL_ASYNC
| REPL_SYNC
| -->
| <attribute name="CacheMode">LOCAL</attribute>
|
| <!-- Name of cluster. Needs to be the same for all clusters, in order
| to find each other -->
| <attribute name="ClusterName">EJB3-entity-cache</attribute>
|
| <!-- Must be true if any entity deployment uses a scoped classloader -->
| <attribute name="UseRegionBasedMarshalling">true</attribute>
| <!-- Must match the value of "UseRegionBasedMarshalling" -->
| <attribute name="InactiveOnStartup">true</attribute>
|
| <attribute name="ClusterConfig">
| <config>
| <!-- UDP: if you have a multihomed machine,
| set the bind_addr attribute to the appropriate NIC IP address
| -->
| <!-- UDP: On Windows machines, because of the media sense feature
| being broken with multicast (even after disabling media sense)
| set the loopback attribute to true
| -->
| <UDP mcast_addr="${jboss.partition.udpGroup:228.1.2.3}" mcast_port="43333" ip_ttl="${jgroups.mcast.ip_ttl:2}" ip_mcast="true"
| mcast_send_buf_size="150000" mcast_recv_buf_size="80000" ucast_send_buf_size="150000"
| ucast_recv_buf_size="80000" loopback="false" />
| <PING timeout="2000" num_initial_members="3" up_thread="false" down_thread="false" />
| <MERGE2 min_interval="10000" max_interval="20000" />
| <FD_SOCK down_thread="false" up_thread="false"/>
| <FD shun="true" up_thread="false" down_thread="false"
| timeout="20000" max_tries="5"/>
| <VERIFY_SUSPECT timeout="1500" up_thread="false" down_thread="false" />
| <pbcast.NAKACK gc_lag="50" max_xmit_size="8192" retransmit_timeout="600,1200,2400,4800" up_thread="false"
| down_thread="false" />
| <UNICAST timeout="600,1200,2400" window_size="100" min_threshold="10" down_thread="false" />
| <pbcast.STABLE desired_avg_gossip="20000" up_thread="false" down_thread="false" />
| <FRAG frag_size="8192" down_thread="false" up_thread="false" />
| <pbcast.GMS join_timeout="5000" join_retry_timeout="2000" shun="true" print_local_addr="true" />
| <pbcast.STATE_TRANSFER up_thread="false" down_thread="false" />
| </config>
| </attribute>
|
| <!-- The max amount of time (in milliseconds) we wait until the
| initial state (ie. the contents of the cache) are retrieved from
| existing members in a clustered environment
| -->
| <attribute name="InitialStateRetrievalTimeout">50000</attribute>
|
| <!-- Number of milliseconds to wait until all responses for a
| synchronous call have been received.
| -->
| <attribute name="SyncReplTimeout">10000</attribute>
|
| <!-- Max number of milliseconds to wait for a lock acquisition -->
| <attribute name="LockAcquisitionTimeout">15000</attribute>
|
| <!-- Name of the eviction policy class. -->
| <attribute name="EvictionPolicyClass">org.jboss.cache.eviction.LRUPolicy</attribute>
|
| <!-- Specific eviction policy configurations. This is LRU -->
| <attribute name="EvictionPolicyConfig">
| <config>
| <attribute name="wakeUpIntervalSeconds">5</attribute>
| <!-- Cache wide default -->
| <region name="/_default_">
| <attribute name="maxNodes">5000</attribute>
| <attribute name="timeToLiveSeconds">0</attribute>
| </region>
| </config>
| </attribute>
|
| <!--<attribute name="NodeLockingScheme">OPTIMISTIC</attribute>-->
|
| <attribute name="CacheLoaderConfiguration">
| <config>
| <!-- if passivation is true, only the first cache loader is used; the rest are ignored -->
| <passivation>false</passivation>
| <!--<preload>/a/b, /allTempObjects, /some/specific/fqn</preload>-->
| <shared>false</shared>
| <cacheloader>
| <class>org.jboss.cache.loader.JDBCCacheLoader</class>
| <!-- same as the old CacheLoaderConfig attribute -->
| <properties>
| cache.jdbc.driver=com.mysql.jdbc.Driver
| cache.jdbc.url=jdbc:mysql://somebody-mysql-dev:3306/jboss_ad_internals
| cache.jdbc.user=jboss
| cache.jdbc.password=jokers
| </properties>
| <!-- whether the cache loader writes are asynchronous -->
| <async>true</async>
| <!-- only one cache loader in the chain may set fetchPersistentState to true.
| An exception is thrown if more than one cache loader sets this to true. -->
| <fetchPersistentState>true</fetchPersistentState>
| <!-- determines whether this cache loader ignores writes - defaults to false. -->
| <ignoreModifications>true</ignoreModifications>
| <!-- if set to true, purges the contents of this cache loader when the cache starts up.
| Defaults to false. -->
| <purgeOnStartup>false</purgeOnStartup>
| </cacheloader>
|
| </config>
| </attribute>
| </mbean>
|
| </server>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030071#4030071
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030071
19Â years, 1Â month
[JBoss Seam] - Re: Seam jBPM: use annotation or pages.xml to get next task?
by gavin.kingï¼ jboss.com
"bsmithjj" wrote : "gavin.king(a)jboss.com" wrote : Of course, if you created it yourself via some other mechanism, *you* will have to associate it will the conversation using BusinessProcess.instance().setProcessId( processInstance.getId() ).
| |
| | Seam isn't magic. Seam only knows about processes it creates or retrieves. If you get it yourself, by going to jBPM APIs directly, then it is up to you to do the job of associating it with the conversation.
|
| I realize what you're saying above about Seam - I'm attempting to use the EL as you showed earlier to have an ActionHandler invoke a Seam component instead of having to implement an ActionHandler which you claim I should never have to do ;-). Anyway, now we're coming to why I suggested earlier the possibility of creating a Seam-jBPM interceptor that fires around the execute(...) method in an ActionHandler, DecisionHandler, etc...
|
|
Yes, well, I happen to agree with you on this one. Two reasons:
(1) It is needed for the problem of jBPM async events and timers, for me to set up my Seam contexts.
(2) I would be able to transparently associate the processinstance, and save you from doing that explicitly.
Currently, AFAIK, jBPM does not provide the hooks I need for this, but I have asked Tom for them. Not sure the status there.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030058#4030058
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030058
19Â years, 1Â month