April 2009 - jboss-user - Jboss List Archives

[JBoss Messaging] - Re: Problem with user authorization using JBM Bridge configu

by armsargis

In fact the same story with user, for instance I have 2 JBoss servers running on different servers: 1) JBoss - 1, username = local, password local123 queue = LocalQueue 2) JBoss - 2, username = remote, password remote123 queue = RemoteQueue Now I want when there is messages in LocalQueue forward it automatically to RemoteQueue. and for do it I need to create user: 'remote' in JBoss - 1. I think its not logical and can create problem with maintenance. If I change password in one side I should do it also in other side as well. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224605#4224605 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224605

17 years

1
0
0 / 0

[JCA/JBoss] - Re: java.lang.NoClassDefFoundError: net/sf/hibernate/Hiberna

by rasa

Ok. Yes my application is using higernate2 any way i dnt have any plan to change my hibernate version. So i deleted the existing version 3 from the lib direcory and then copied the version 2. Is that will make any other issue. Thanks and Regards Rasa. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224604#4224604 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224604

17 years

1
0
0 / 0

[Security & JAAS/JBoss] - Regarding the SubjectFactory and SecurityDomainJndiName iss

by kesi.wei

1. I defined a application policy in login-config.xml files in JBoss5.0.0GA for example: <application-policy name="bvdb-password-encrypted" > | <authentication> | <login-module code="org.jboss.resource.security.SecureIdentityLoginModule" flag="required"> | <module-option name="username">bv1to6</module-option> | <module-option name="password">68e9a814ca20b431</module-option> | <module-option name="managedConnectionFactoryName">bv.ds:service=LocalTxCM,name=bv_framework.bvdbPool</module-option> | </login-module> | </authentication> | </application-policy> 2. I add the following code in our DataSource. <attribute name="SecurityDomainJndiName">bvdb-password-encrypted</attribute> | <depends optional-attribute-name="JaasSecurityManagerService">jboss.security:service=JaasSecurityManager</depends> 3. Now the login module can't work in JBoss5.0.0GA, It can work well in JBoss4.2.3GA. I study the BaseConnectionManager2.java code. It have the following code private Subject getSubject() | { | Subject subject = null; | if(subjectFactory != null && securityDomainJndiName != null) | { | subject = subjectFactory.createSubject(securityDomainJndiName); | } | if (trace) | log.trace("subject: " + subject); | return subject; | } 4. If we don't pass subjectFactory. The subjectFactory is null. So we can't get subjcet. Now we want to know How to pass subjectFactory in our datasource in xml files. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224599#4224599 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224599

17 years

1
0
0 / 0

[JBoss Messaging] - Re: Problem with user authorization using JBM Bridge configu

by armsargis

Sorry I should provide info about JBoss before here is my version: 11:18:45,872 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902232048)] Started in 44s:525ms I just copy default server configuration and I am using: oracle-persistence-service.xml just and just change in DataSource. Please not I have not problem when I am working locally without bridging. and here is my security config:  | <application-policy xmlns="urn:jboss:security-beans:1.0" name="messaging"> | <authentication> | <login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule" flag="required"> | <module-option name="unauthenticatedIdentity">guest</module-option> | <module-option name="dsJndiName">java:/FormMJMSDS</module-option> | <module-option name="principalsQuery">SELECT PASSWD FROM JBM_USER WHERE USER_ID=?</module-option> | <module-option name="rolesQuery">SELECT ROLE_ID, 'Roles' FROM JBM_ROLE WHERE USER_ID=?</module-option> | </login-module> | </authentication> | </application-policy> | | <bean name="SecurityStore" class="org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore"> |  | <property name="defaultSecurityConfig"> | <![CDATA[ | <security> | <role name="guest" read="true" write="true" create="true"/> | </security> | ]]> | </property> | <property name="suckerPassword">CHANGE ME!!</property> | <property name="securityDomain">java:/jaas/messaging</property> | <property name="securityManagement"><inject bean="JNDIBasedSecurityManagement"/></property> |  | <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss.messaging:service=SecurityStore",exposedInterface=org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStoreMBean.class)</annotation> | </bean> View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224598#4224598 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224598

17 years

1
0
0 / 0

[JBoss jBPM] - Re: Hibernate Error when persist the outer ProcessInstance.

by boercher

Obviously creation of ProcessInstances involves the database. I've looked up the ProcessInstance constructor: public ProcessInstance(ProcessDefinition processDefinition, Map<String, Object> variables, String key) | { | [...] | // if this process instance is created in the context of a persistent operation | Services.assignId(this); | [...] | } | You are surely operating in the context of a persistent operation so this call to this static method of Services (I guess these are the services from the jbpm.cfg.xml) will do some Hibernate stuff. Since jBPM heavily relies on a database for everything (transaction safety, logging, ...) I would guess that it will be hard to work around that by other means than by crude hacks. Volker View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224595#4224595 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224595

17 years

1
0
0 / 0

[EJB 3.0] - Re: NullPointerException in JavaEEComponentHelper with JBoss

by wolfc

Just before the NPE there should a log debug message starting with: Found endpoint for interface: If so, please post it. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224590#4224590 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224590

17 years

1
0
0 / 0

[JBoss Tools (users)] - Re: Problems using

by bernie_h

Ok, I've just retested everything with a fresh installation of eclipse 3.4.2 and JBoss Tools 3.0.0GA and both JBoss AS 4.2.2 and 4.2.3. I can always replicate the problem - the application.xml is never touched and a simple facelets-saving (with auto-publishing feature turned on) causes the perstistence unit to restart... Maybe it's an OS-Problem (?), I'm working on Windows Vista... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224588#4224588 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224588

17 years

1
0
0 / 0

[Installation, Configuration & DEPLOYMENT] - .ear file deployment problem in JBOSS5.0.1

by sekhar_td

Hi I have an .ear file working in Jboss4.0.4. I modified the <web-app> xsd version from 2.4 to 2.5 and deployed the .ear file in Jboss5.0.1. when i ran the Jboss I am getting below exception. Please suggest me the solution to overcome this problem. ERROR [org.jboss.system.server.profileservice.ProfileServiceBootstrap] (main) Failed to load profile: org.jboss.deployers.spi.DeploymentException: Exception determining structure: AbstractVFSDeployment(auctions.ear) at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:85) at org.jboss.deployers.plugins.main.MainDeployerImpl.determineStructure(MainDeployerImpl.java:1000) at org.jboss.deployers.plugins.main.MainDeployerImpl.determineDeploymentContext(MainDeployerImpl.java:440) at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:390) at org.jboss.deployers.plugins.main.MainDeployerImpl.addDeployment(MainDeployerImpl.java:300) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:303) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.RuntimeException: Error determining structure: auctions.ear at org.jboss.deployment.EARStructure.determineStructure(EARStructure.java:293) at org.jboss.deployers.vfs.plugins.structure.StructureDeployerWrapper.determineStructure(StructureDeployerWrapper.java:73) at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.doDetermineStructure(VFSStructuralDeployersImpl.java:196) at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.determineStructure(VFSStructuralDeployersImpl.java:221) at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:77) ... 10 more Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: The ' = ' character must follow "http:" in the XML declaration. @ *unknown*[3,26] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:183) at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:161) at org.jboss.deployment.EARStructure.determineStructure(EARStructure.java:160) ... 14 more Caused by: org.xml.sax.SAXException: The ' = ' character must follow "http:" in the XML declaration. @ *unknown*[3,26] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.fatalError(SaxJBossXBParser.java:432) at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source) at org.apache.xerces.impl.XMLScanner.scanPseudoAttribute(Unknown Source) at org.apache.xerces.impl.XMLScanner.scanXMLDeclOrTextDecl(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanXMLDeclOrTextDecl(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$XMLDeclDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199) ... 17 more Thanks, Sekhar View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224587#4224587 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224587

17 years

1
0
0 / 0

[JBoss Tools (users)] - Re: Problems using

by max.andersen＠jboss.com

No, we should not be touching any descriptors if you are just doing a normal incremental publish View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224584#4224584 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224584

17 years

1
0
0 / 0

[JBoss jBPM] - Re: Ensure consistency of logging

by jbarrez

Simply call the jBPMContext.save(processInstance) operation before the close() method is invoked. The logging for the process instance, including the subprocesses, will be stored in the log table. For a task, you should do | JbpmContext context = ...; | TaskInstance task = context.getTaskInstance(id); | task.end(); | context.save(task.getProcessInstance); | context.close(); | Or, better, use the jBPM command service. The commands automatically save the process instance (and closes the context): | TaskEndCommand command = new TaskEndCommand(taskId); | commandService.execute(command); | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4224579#4224579 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4224579

17 years

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