November 2007 - jboss-user - Jboss List Archives

[Microcontainer] - OSGi Deployer on MC 2.0

by vbatista

Hi, I have read on these forums that jboss 5.0 Beta3 will have the microcontainer 2.0, and that this version of the MC will have an OSGi deployer. Can any one confirm this? Is there any planned date for the release of JBoss 5.0 Beta3? If my assumption is wrong, is there any one who have already integrated any OSGi framework with JBoss (fenix, equinox,..), even if this in not a full integration (Classloader issues, ...)? I really need OSGi on top of JBoss...even if I can't have class versioning... Thanks in advance. Best regards, Victor Batista View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101119#4101119 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4101119

18 years, 5 months

1
0
0 / 0

[JBoss Seam] - Re: Configuring MultipartFilter

by shane.bryzak＠jboss.com

In components.xml: <web:multipart-filter create-temp-files="true" | max-request-size="1000000" | url-pattern="*.seam"/> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101118#4101118 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4101118

18 years, 5 months

1
0
0 / 0

[JBoss Seam] - Re: GWT Example in 2.0 CR3 doesn't work

by shane.bryzak＠jboss.com

I've just done a clean build of both Seam and the GWT example, deployed in JBoss AS 4.2.2.GA, and I can confirm that the example does work. There were a couple of minor changes to the GWT example that I just committed to CVS however it's unlikely that they're related to your exception. Which JDK version are you using? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101117#4101117 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4101117

18 years, 5 months

1
0
0 / 0

[JBoss Seam] - Re: identiy.login called twice

by shane.bryzak＠jboss.com

The ref docs were incorrect here (I've fixed them in CVS) - it's not the role of the authenticator to add faces messages, as Pete already pointed out. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101116#4101116 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4101116

18 years, 5 months

1
0
0 / 0

[JBoss Seam] - Re: Seam with multiple web pages

by shane.bryzak＠jboss.com

"DiegoCoronel" wrote : this is the question i tried to do a few days ago, so, if i got multiple war´s in same EAR can i have 1 authentication ? because it wasnt working with multiple ear's. What wasn't working? Was an exception being thrown? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101115#4101115 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4101115

18 years, 5 months

1
0
0 / 0

[J2EE Design Patterns] - Design for heavy processing

by yoggi2k5

Hi all experts. I'm about to design a "price-finder" application that read prices from a website. I have about 10 000 URLs to products in a database right now. Some URLs needs to be read every 5 minutes, others every 20 minutes and the rest every hour. It takes up to 2 sec to download and process every page. It's the downloading thats the bottleneck right now, due to the "slow" webservers I read the data from. I need to have around 10 "processes" working at the same time to be able to process it all. I was thinking of having a scheduled MDB's that is triggered every 5, 20 and 60 minutes. Every time it's triggered it will get rellevant URLs from the database (about 3500 each time), split it up into 10 parts and send each part to a stateless session bean for processing. The stateless session beans will then processes around 350 URLs each. What do you experts think about that design? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101114#4101114 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4101114

18 years, 5 months

1
0
0 / 0

[Clustering/JBoss] - Re: XAConnectionFactory not found only in Clustering

by seoeng

Let me add one more thing, as anything can help at this point. I have overriden some settings in my jboss.xml in my ejb.jar...maybe this is causing the issue? (it works in the default server setting in a standalone configuration): | <!DOCTYPE jboss PUBLIC | "-//JBoss//DTD JBOSS 4.0//EN" | "http://www.jboss.org/j2ee/dtd/jboss_4_0.dtd"> | <jboss> | <enterprise-beans> | <message-driven> | <ejb-name>MDB1</ejb-name> | <configuration-name>MDB1MDBConfig</configuration-name> | <destination-jndi-name>queue/MDB1Queue</destination-jndi-name> | </message-driven> | <message-driven> | <ejb-name>MDB2</ejb-name> | <configuration-name>MDB2MDBConfig</configuration-name> | <destination-jndi-name>queue/MDB2Queue</destination-jndi-name> | </message-driven> | <message-driven> | <ejb-name>MDB3</ejb-name> | <configuration-name>MDB3MDBConfig</configuration-name> | <destination-jndi-name>queue/MDB3Queue</destination-jndi-name> | </message-driven> | <message-driven> | <ejb-name>MDB4</ejb-name> | <configuration-name>MDB4MDBConfig</configuration-name> | <destination-jndi-name>queue/MDB4Queue</destination-jndi-name> | </message-driven> | </enterprise-beans> | | <container-configurations> | | <container-configuration> | <container-name>MDB4MDBConfig</container-name> | <call-logging>false</call-logging> | <invoker-proxy-binding-name>MDB4-message-driven-bean</invoker-proxy-binding-name> | <container-interceptors> | <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor> | <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor> | <interceptor>org.jboss.ejb.plugins.RunAsSecurityInterceptor</interceptor> |  | <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor> | <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor> | <interceptor transaction="Container">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor> |  | <interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor> | <interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT</interceptor> | <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor> | <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor> | </container-interceptors> | <instance-pool>org.jboss.ejb.plugins.MessageDrivenInstancePool</instance-pool> | <instance-cache></instance-cache> | <persistence-manager></persistence-manager> | <container-pool-conf> | <MaximumSize>50</MaximumSize> | </container-pool-conf> | </container-configuration> | | <container-configuration> | <container-name>MDB3MDBConfig</container-name> | <call-logging>false</call-logging> | <invoker-proxy-binding-name>MDB3-message-driven-bean</invoker-proxy-binding-name> | <container-interceptors> | <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor> | <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor> | <interceptor>org.jboss.ejb.plugins.RunAsSecurityInterceptor</interceptor> |  | <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor> | <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor> | <interceptor transaction="Container">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor> |  | <interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor> | <interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT</interceptor> | <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor> | <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor> | </container-interceptors> | <instance-pool>org.jboss.ejb.plugins.MessageDrivenInstancePool</instance-pool> | <instance-cache></instance-cache> | <persistence-manager></persistence-manager> | <container-pool-conf> | <MaximumSize>50</MaximumSize> | </container-pool-conf> | </container-configuration> | | <container-configuration> | <container-name>MDB2MDBConfig</container-name> | <call-logging>false</call-logging> | <invoker-proxy-binding-name>MDB2-message-driven-bean</invoker-proxy-binding-name> | <container-interceptors> | <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor> | <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor> | <interceptor>org.jboss.ejb.plugins.RunAsSecurityInterceptor</interceptor> |  | <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor> | <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor> | <interceptor transaction="Container">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor> |  | <interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor> | <interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT</interceptor> | <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor> | <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor> | </container-interceptors> | <instance-pool>org.jboss.ejb.plugins.MessageDrivenInstancePool</instance-pool> | <instance-cache></instance-cache> | <persistence-manager></persistence-manager> | <container-pool-conf> | <MaximumSize>50</MaximumSize> | </container-pool-conf> | </container-configuration> | | <container-configuration> | <container-name>MDB1MDBConfig</container-name> | <call-logging>false</call-logging> | <invoker-proxy-binding-name>MDB1-message-driven-bean</invoker-proxy-binding-name> | <container-interceptors> | <interceptor>org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor</interceptor> | <interceptor>org.jboss.ejb.plugins.LogInterceptor</interceptor> | <interceptor>org.jboss.ejb.plugins.RunAsSecurityInterceptor</interceptor> |  | <interceptor transaction="Container">org.jboss.ejb.plugins.TxInterceptorCMT</interceptor> | <interceptor transaction="Container">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor> | <interceptor transaction="Container">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor> |  | <interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor</interceptor> | <interceptor transaction="Bean">org.jboss.ejb.plugins.MessageDrivenTxInterceptorBMT</interceptor> | <interceptor transaction="Bean">org.jboss.ejb.plugins.CallValidationInterceptor</interceptor> | <interceptor>org.jboss.resource.connectionmanager.CachedConnectionInterceptor</interceptor> | </container-interceptors> | <instance-pool>org.jboss.ejb.plugins.MessageDrivenInstancePool</instance-pool> | <instance-cache></instance-cache> | <persistence-manager></persistence-manager> | <container-pool-conf> | <MaximumSize>50</MaximumSize> | </container-pool-conf> | </container-configuration> | </container-configurations> | | <invoker-proxy-bindings> | | <invoker-proxy-binding> | <name>MDB4-message-driven-bean</name> | <invoker-mbean>default</invoker-mbean> | <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory> | <proxy-factory-config> | <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI> | <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI> | <CreateJBossMQDestination>true</CreateJBossMQDestination> |  | <MinimumSize>1</MinimumSize> | <MaximumSize>5</MaximumSize> | <KeepAliveMillis>30000</KeepAliveMillis> | <MaxMessages>1</MaxMessages> | <MDBConfig> | <ReconnectIntervalSec>10</ReconnectIntervalSec> | <DLQConfig> | <DestinationQueue>queue/DLQ</DestinationQueue> | <MaxTimesRedelivered>10</MaxTimesRedelivered> | <TimeToLive>0</TimeToLive> | </DLQConfig> | </MDBConfig> | </proxy-factory-config> | </invoker-proxy-binding> | | <invoker-proxy-binding> | <name>MDB3-message-driven-bean</name> | <invoker-mbean>default</invoker-mbean> | <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory> | <proxy-factory-config> | <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI> | <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI> | <CreateJBossMQDestination>true</CreateJBossMQDestination> |  | <MinimumSize>1</MinimumSize> | <MaximumSize>1</MaximumSize> | <KeepAliveMillis>30000</KeepAliveMillis> | <MaxMessages>1</MaxMessages> | <MDBConfig> | <ReconnectIntervalSec>10</ReconnectIntervalSec> | <DLQConfig> | <DestinationQueue>queue/DLQ</DestinationQueue> | <MaxTimesRedelivered>10</MaxTimesRedelivered> | <TimeToLive>0</TimeToLive> | </DLQConfig> | </MDBConfig> | </proxy-factory-config> | </invoker-proxy-binding> | | <invoker-proxy-binding> | <name>MDB1-message-driven-bean</name> | <invoker-mbean>default</invoker-mbean> | <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory> | <proxy-factory-config> | <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI> | <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI> | <CreateJBossMQDestination>true</CreateJBossMQDestination> |  | <MinimumSize>1</MinimumSize> | <MaximumSize>2</MaximumSize> | <KeepAliveMillis>30000</KeepAliveMillis> | <MaxMessages>1</MaxMessages> | <MDBConfig> | <ReconnectIntervalSec>10</ReconnectIntervalSec> | <DLQConfig> | <DestinationQueue>queue/DLQ</DestinationQueue> | <MaxTimesRedelivered>10</MaxTimesRedelivered> | <TimeToLive>0</TimeToLive> | </DLQConfig> | </MDBConfig> | </proxy-factory-config> | </invoker-proxy-binding> | | <invoker-proxy-binding> | <name>MDB2-message-driven-bean</name> | <invoker-mbean>default</invoker-mbean> | <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory> | <proxy-factory-config> | <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI> | <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI> | <CreateJBossMQDestination>true</CreateJBossMQDestination> |  | <MinimumSize>1</MinimumSize> | <MaximumSize>1</MaximumSize> | <KeepAliveMillis>30000</KeepAliveMillis> | <MaxMessages>1</MaxMessages> | <MDBConfig> | <ReconnectIntervalSec>10</ReconnectIntervalSec> | <DLQConfig> | <DestinationQueue>queue/DLQ</DestinationQueue> | <MaxTimesRedelivered>10</MaxTimesRedelivered> | <TimeToLive>0</TimeToLive> | </DLQConfig> | </MDBConfig> | </proxy-factory-config> | </invoker-proxy-binding> | </invoker-proxy-bindings> | | </jboss> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101113#4101113 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4101113

18 years, 5 months

1
0
0 / 0

[JBoss Seam] - Re: HTTPS redirection

by rjstanford

In fact, it would appear according to this JIRA that there is a problem - any thoughts as to a solution? Surely we're not the only volume-oriented business planning to move forward in this way - I'd like to think its a solved problem :-) http://jira.jboss.com/jira/browse/JBSEAM-1024 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101110#4101110 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4101110

18 years, 5 months

1
0
0 / 0

[JBoss Messaging] - Re: ClientCallback Multiplex

by clebert.suconic＠jboss.com

>> jboss.messaging.callback.bind.port This variable is not used any more. We have fixed the documentation removing this old option from doc. On 1.3.0 we started using something called Bisocket where the client will create sockets and the server will use them to callback on the client. Can you try the new 1.4.0.SP1 release? We have done a bunch of fixed on remoting and configuration improvements. If you are behind a firewal you will also see some extra configuration options on the Remoting-bisocket. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101109#4101109 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4101109

18 years, 5 months

1
0
0 / 0

[JBoss Seam] - Re: HTTPS redirection

by rjstanford

Does this process work with external SSL decoding? We need to be able to mark certain pages as requiring SSL (or at least make sure that links to the contain https:// on them); but we're setting up external SSL decoders so the Seam app will never actually see any SSL traffic. Is there some kind of best-practice in this situation? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101107#4101107 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4101107

18 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user November 2007