[Design of JBoss Collaboration Server] - Collaboration other services?
by enazareno
Hi,
I just want to know if there are plans for other communication services that will be built on top of JBCS and not just email or calendaring. Example, is it part of the direction to support like instant messaging? or have support for winpop and the like, or SMS perhaps? I don't know if my question is out of scope but we have requirements also for IM and chat(for enterprise use) and I think it would be great if we can have only one source for it. I'm quite happy that JBCS leverages our knowledge with JBoss and basically we don't have to learn too many new stuff (I'm quite a newbie to email and learning it was the only thing I had to do). So I think it'd be great if JBCS would include all other communication and collaboration stuff that'd be great for the workplace. If this has been discussed or there are other projects for this functionality, I'd appreciate if you can point me to those threads. Thanks!
Regards,
Elmo
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957284#3957284
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957284
20 years
[Design of Kosmos] - Re: Kosmos Jira Authentication using Soap
by melpelotones
Hi Aron,
Thanks a lot again,in the end I changed to exo-portal,
where the portlets are deployed as well without problems.
I have configured the Jira Portlet as you told me in
former mail.
This is my portlet.xml
<portlet-name>MyProjectJiraMonitoringPortlet</portlet-name>
<portlet-class>hu.midori.kosmos.portlet.jira.JiraMonitoringPortlet</portlet-class>
<init-param>
monitored.resource
Myproject Issues
</init-param>
<init-param>
service.url
http://localhost:8091/kosmos-server/kosmos-services/jirasoap-service
</init-param>
<init-param>
monitored.urls
http://myuser:mypassword@myjiraservice:8080/rpc/soap/jirasoapservice-v2?w...
</init-param>
<mime-type>text/html</mime-type>
<portlet-mode>HELP</portlet-mode>
<portlet-mode>VIEW</portlet-mode>
<supported-locale>en</supported-locale>
<supported-locale>fr</supported-locale>
<resource-bundle>hu.midori.kosmos.portlet.jira.jira_monitoring</resource-bundle>
<portlet-info>
JIRA Monitoring
</portlet-info>
and I have got the following error
[INFO] Http11Protocol - Starting Coyote HTTP/1.1 on http-8443
[INFO] ChannelSocket - JK2: ajp13 listening on /0.0.0.0:8009
[INFO] JkMain - Jk running ID=0 time=0/18 config=/home/ONE/exo-tomcat/conf/jk2.properties
[INFO] Catalina - Server startup in 18918 ms
[INFO] JiraMonitoringPortlet - Initializing...
[INFO] JiraMonitoringPortlet - Viewing...
[INFO] MethodResultCacheInterceptor - Cache-miss: reloading "hu.midori.kosmos.server.jira.JiraSoapServiceImpl.getProjects.http://myuser:mypassword@myjiraserver:8080/rpc/soap/jirasoapservice-v2?wsdl:Myproject"...
[ERROR] JiraSoapServiceImpl - Unable to log out <java.lang.NullPointerException>java.lang.NullPointerException
at hu.midori.kosmos.server.jira.JiraSoapServiceImpl.disconnect(JiraSoapServiceImpl.java:217)
at hu.midori.kosmos.server.jira.JiraSoapServiceImpl.getProjects(JiraSoapServiceImpl.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:287)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:181)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
at hu.midori.kosmos.server.MethodResultCacheInterceptor.invoke(MethodResultCacheInterceptor.java:56)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:176)
at $Proxy3.getProjects(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:287)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:181)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
at org.springframework.remoting.support.RemoteInvocationTraceInterceptor.invoke(RemoteInvocationTraceInterceptor.java:68)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:176)
at $Proxy4.getProjects(Unknown Source).
When I try to access to
http://user:password@myjiraserver:8080/rpc/soap/jirasoapservice-v2?wsdl:M...
>From mozilla, axis tell me that there is a web service in this adress.
Do you have any Idea?
Thank you in advance and best regards
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957266#3957266
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957266
20 years
[Design of JCA on JBoss] - POJO JCA
by weston.price＠jboss.com
Fleshing out the jboss-jca implementation. The existing functionality leads to a few points that need to be considered in the POJO implementation.
Pool Management/Lifecycle
a) Typical pooling variables (min, max, idle). As an initial implementation, these can be injected via the PoolFactory.
b) Pool lifecyle tasks (dumb runnables). My initial idea for this was dynamically setup PoolMonitors after the pool is created via a simple Advice. Basically:
|
| public Object invoke(Invocation invocation) throws Throwable
| {
| final ManagedConnectionContextPool pool = (ManagedConnectionContextPool)invocation.invokeNext();
|
| for (Iterator iter = monitors.iterator(); iter.hasNext();)
| {
| ManagedConnectionContextPoolMonitor monitor = (ManagedConnectionContextPoolMonitor) iter.next();
| monitor.setManagedConnectionContextPool(pool);
|
| }
|
| return pool;
| }
|
|
This would be used for the IdleRemover, PoolFiller and BackgroundValidator. Also, this may be an interesting use case for the new Timer SPI (expiration tasks that do *something* to the underlying pool).
3)Validation/ErrorHandling
This could be encapsulated in simple advices to start.
Advanced Pooling Features (TODO)
Smarter Pool Handling:
I think this is a good area for drastic improvement. Ideas off the top of my head would include
Dynamic latch policies to reduce pool contention. This would supplant the simple Semaphore in the code today. Latch policies could be pluggable. This is a natural area for an spi.
Generational pools (sort of like heaps) might be an interesting to think about in terms of having 'generational' handling of managed connections where time, or some other generational policy (also pluggable) would move a ManagedConnection through different phases/pools until death (timeout).
Load optimizing pools (basically recording a history of load averages and attempting to make 'smart' anticipitory judgements about pool loads and access.
Statistics (this really goes across JCA and is not particular to pools).
All of the above should be pluggable via the MC/AOP etc, etc. Working examples of some of the above are going in.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957228#3957228
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3957228
20 years