[Design of Security on JBoss] - Re: Cleaned up security project
by scott.stark@jboss.org
Another dependency that still needs to be cleaned up are these jbossas references:
| <dependency>
| <groupId>jboss</groupId>
| <artifactId>jboss-j2ee</artifactId>
| <version>SNAPSHOT</version>
| </dependency>
| <dependency>
| <groupId>jboss</groupId>
| <artifactId>jboss-j2se</artifactId>
| <version>5.0-SNAPSHOT</version>
| </dependency>
| <dependency>
| <groupId>jboss</groupId>
| <artifactId>jboss-system</artifactId>
| <version>5.0-SNAPSHOT</version>
| </dependency>
| <dependency>
| <groupId>jboss</groupId>
| <artifactId>jboss-transaction</artifactId>
| <version>5.0-SNAPSHOT</version>
| </dependency>
| <dependency>
| <groupId>jboss</groupId>
| <artifactId>jboss</artifactId>
| <version>5.0-SNAPSHOT</version>
| </dependency>
| <dependency>
| <groupId>jboss</groupId>
| <artifactId>jnpserver</artifactId>
| <version>5.0-SNAPSHOT</version>
| </dependency>
| <dependency>
| <groupId>jboss</groupId>
| <artifactId>jboss-mbeans</artifactId>
| <version>5.0-SNAPSHOT</version>
| </dependency>
|
Some should just be removed and the security project refactored to remove the dependency. Others need the jbossas project to be splitup.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989413#3989413
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989413
17 years, 11 months
[Design of EJB 3.0] - Re: Problems with replicating entity queries via JBC
by bstansberry@jboss.com
Thanks, Max.
I figured if update timestamps was replicated it should be OK. I'll of course test it out :).
anonymous wrote :
| Saying that, I'm surprised to hear that JBC isn't able to use the applications current thread context classloader ?! I thought this were the way these serilaization issues were solved before ?
|
Problem arises because the cache is not deployed as part of the application -- it's a shared resource. Deserialization is done by a thread coming up from the JGroups layer, not an "application" thread, so there is no single correct TCCL to use.
But, you raise an interesting point about when the cache is not a shared resource. In that case it still uses the classloader that loaded JGroups to deserialize messages, rather than the TCCL that was in effect when the cache was deployed. I'll open a forum thread about that.
anonymous wrote :
| Note, I don't think the serialization issues only occur for querycache - it would AFAIK also occur if a user has his own UserType in the id of his entities.
|
Yep. That requires JBCACHE-876 to fix, since the user class will be in the Fqn rather than the data map. :(
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989409#3989409
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989409
17 years, 11 months
[Design of Kosmos] - Re: Kosmos refresh button
by aron.gombas
Hi!
"bjoy" wrote : The portlet has a refresh button. However all that seems to happen when pressed is that the entire portal page refreshes. I don't see updated information about the repository.
That button is reserved for partial reloads via AJAX (implemented at some point in the future): I mean the plan is that you can reload a single portlet without reloading the whole portal page. Currently, it simply reloads the whole page.
"bjoy" wrote : How can I get the latest information without having to restart the portal?
You can schedule your updates as you wish! See the server configuration section in the Kosmos Manual:
| The trigger for the update scheduler can be configured as a standard Spring trigger bean, either a simple one or a cron-style one:
|
| <bean id="serviceResultUpdateTrigger" class="org.springframework.scheduling.quartz.SimpleTriggerBean">
| <property name="jobDetail" ref="serviceResultUpdaterJob"/>
| <property name="startDelay" value="7200000"/><!-- start and repeat in every 2 hours -->
| <property name="repeatInterval" value="7200000"/>
| </bean>
| <!--
| Alternatively, a cron-style trigger can be used.
| For this, remove the previous bean definition and use this one:
|
| <bean id="serviceResultUpdateTrigger" class="org.springframework.scheduling.quartz.CronTriggerBean">
| <property name="jobDetail" ref="serviceResultUpdaterJob"/>
| <property name="cronExpression" value="0 0 6 * * ?"/>
| </bean>
| -->
|
| All the information delivered by the services will be automatically refreshed in the given time. For example, you can schedule a very expensive Subversion repository traversal at 2 o'clock in the morning every day, so the portal will reflect up-to-date results by the time you get to your browser.
|
"bjoy" wrote : I see in the roadmap that the 0.3.0 version is supposed to have an auto refresh capability.
This is already available in 0.2.0RC2.
"bjoy" wrote : A secondary question: is Kosmos is under active development? It has been a long time without any updates.
Unfortunately (fortunately? :)), I got very busy recently with other (day time) projects, and I contributed 95% of the code so far. Feel free to join the project or donate to the project, if you like it and would like to see this improving.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3989408#3989408
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3989408
17 years, 11 months