April 2009 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Queue not registered with JNDI service in AS 5

by gaohoward

sorry, the props are | <start ignored="true"/> | <stop ignored="true"/> | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226419#4226419 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226419

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Queue not registered with JNDI service in AS 5

by gaohoward

The following prop should put in entry in the beans configs. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226417#4226417 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226417

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: HDScanner scanPeriod

by jaikiran

"pete.muir(a)jboss.org" wrote : | | Any reason not reduce this by a factor of 10 to 500ms? I only side-effect that i can think of is the HDScanner picking up incompletely "copied" deployments. Assuming that a existing deployment is being overwritten or a new deployment is being copied to the deploy folder and the copy is still in progress, then the HDSCanner will complain about invalid deployments. Till scenario exists even now (when the scanning time is set to 5 seconds), but reducing the scanning time to a very low value is going increase the likelihood of such cases. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226416#4226416 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226416

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: HDScanner scanPeriod

by jaikiran

"alesj" wrote : | | | protected boolean hasStructureBeenModifed(VirtualFile root, VFSDeploymentContext deploymentContext) throws IOException | | { | | ... | | // check for addition | | AddVisitor addVisitor = new AddVisitor(originalAttributes, getCache(), synchAdapter, tempRoot, root.getPathName().length()); | | root.visit(addVisitor); | | } | | return modified; | | } | | | | AddVisitor traverses over originals, checking if matching temp exists, | if not, new file has been added --> solving your problem. ;-) Assuming the HDScanner is set to run every 5 seconds, wouldn't this scanning for new files within the original deployment lead to time delays? From what i see, the AddVisitor looks for new files in the original deployments and these new files can be nested too. Which effectively means scanning the entire deployment every 5 seconds. I haven't given this change a try against the AS, so don't know whether i am talking sense :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226414#4226414 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226414

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Queue not registered with JNDI service in AS 5

by gaohoward

The jms/clustered-queue has same problem. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226412#4226412 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226412

17 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: JBossAS5 deployers for JBossESB 4.x

by beve

This MicroContainer thread is also related to this issue: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=154263 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226406#4226406 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226406

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Queue not registered with JNDI service in AS 5

by gaohoward

mdb, hajndi not working also. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226405#4226405 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226405

17 years, 1 month

1
0
0 / 0

[Design of JBoss ESB] - Re: ESB4.x/AS 5 classloading

by beve

Since the forums have been down I've made some progress on this. The classloading issue that I reported previously was a configuration error on my part. I had created jboss-structure.xml files for our services. <structure> | <context> | <path name=""/> | <metaDataPath> | <path name="META-INF"/> | </metaDataPath> | <classpath> | <path name=""/> | </classpath> | </context> | </structure> I was assuming that this would include all files in the root of the the deployment archive but it seems that I need to specify that jars are to be included. Adding <path name="" suffixes=".jar"/> to the classpath worked. The complete jboss-structure.xml now looks like this: <structure> | <context> | <path name=""/> | <metaDataPath> | <path name="META-INF"/> | </metaDataPath> | <classpath> | <path name=""/> | <path name="" suffixes=".jar"/> | </classpath> | </context> | </structure> View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226404#4226404 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226404

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Queue not registered with JNDI service in AS 5

by gaohoward

Today I got exception when running javaee servlet example: Exception in thread "main" javax.naming.NameNotFoundException: queue not bound I lookup the JNDIView on AS 5 and didn't find any queue in it. Did I miss something? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226402#4226402 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226402

17 years, 1 month

1
0
0 / 0

[Design of JBoss Identity] - Identity Management integration with JBossAS5.

by jeff.yuchang

With the latest code from trunk, run the mvn clean install -Pdistro and then from the distro/target, run: java -jar jbidm-1.0.0-SNAPSHOT.jar you will be able to deploy the identity management module into JBoss AS5. The tasks that the integration and distro module did are as following: 1. Generate the database schema in the build time. 2. Start the IdentitySessionFactory from the META-INF/idm-service-jboss-beans.xml in the JBoss AS5. 3. Register and the IdentitySessionFactory in the JNDI. The file structure for the idm-service.sar is: | idm-service.sar | |--idm-sql | |---------jboss.idm.hsql.create.sql | |---META-INF | |---------idm-service-jboss-beans.xml | |----jboss-idm.xml | |----jboss.idm.hibernate.cfg.xml the content of idm-service-jboss-beans.xml is: <bean name="jboss.identity.IDMService" | class="org.jboss.identity.idm.integration.jboss5.IDMService"> | <constructor> | <parameter>jboss-idm.xml</parameter> | </constructor> | <property name="idmSessionFactoryJNDI">java:/IdentitySessionFactory</property> | <property name="SQLScript">idm-sql/jboss.idm.hsql.create.sql</property> | <property name="datasource">java:jbossidmDS</property> | <property name="exitSQL">select * from jbid_io</property> | <depends>jboss.jca:service=DataSourceBinding,name=jbossidmDS</depends> | </bean> So, in this case, we installed the default identity management module in the JBoss AS5. other projects who want to use the idm (like jBPM4) can get the IdentitySessionFactory can get it through the jndi. This is one way to use the identity management, say using the sharing/default one. Another two scenarios that I can see is: 1. Use it in the embedded way, they want to create the database table schemas in its own database, instead of the sharing one. AFAIK like portal. It will start the identitySessionFactory through the API. In this case, I don't think we need to any integration for it. 2. Use it in the standalone but with its own repository(database) back-end. say like SOA-Repository(Guvnor) project, it has defined its own guvnor-idm.xml configuration file for the jboss identity. In this case, users need to do as following to start the IdentitySessionFactory. Users just have to write a *-jboss-beans.xml, like what we did for the idm-service.sar, and then can populate the database schema to target DB, and register the IdentitySessionFactory into the specified JNDI. Above all, I don't think we need to write the deployer for -idm.xml(configuration file for identity management) at the moment. However, I do think we need to put the idm related jars in a folder that other artifacts can depends on, so that they don't need to have the duplicated idm libraries. (as of writing, I think can can specify other artifacts depends on the idm-service.sar, so that all of libraries in the idm-service.sar can be seen in the artifact, but haven't tried it yet.) So, above is what I have & thought about the integration, did I miss something here, or which way will you use the jboss identity project? Any comments and suggestions are welcome. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4226400#4226400 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4226400

17 years, 1 month

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-dev-forums April 2009