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

[Design of JBoss ESB] - Re: Scoped deployments in AS 5.x

by beve

So for a ESB 4.x scoped deployment users will be required to create a META-INF/jboss-classloading.xml: <classloading xmlns="urn:jboss:classloading:1.0" domain="simple-scoped" parent-first="false" /> | which will "replace" the 'loader-repository' element in META-INF/deployment.xml: <jbossesb-deployment> | <loader-repository> | org.jboss.soa.esb:loader=simple-scoped | <loader-repository-config> | java2ParentDelegaton=false | </loader-repository-config> | </loader-repository> | </jbossesb-deployment> The 'loader-repository' element can be left but will be ignored by the AS 5 esb deployers. /Daniel View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227683#4227683 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227683

15 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: org.jboss.test.messaging.jms.ConnectionTest failiin

by clebert.suconic＠jboss.com

Tim, I am commenting out the test for now, so we can get a clear run today. I tried to fix it earlier but I couldn't find the cause quickly. I believe it would be easy for you though as it was something you were working on. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227655#4227655 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227655

15 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: org.jboss.test.messaging.jms.ConnectionTest failiin

by clebert.suconic＠jboss.com

anonymous wrote : And Hudson shows occasional failures. | | http://hudson.qa.jboss.com/hudson/view/JBM%202/job/JBM2-tests/4724/testRe... | | Actually, it aways fail View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227635#4227635 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227635

15 years

1
0
0 / 0

[Design of JBossXB] - Re: problem parsing sip.xml with JBossXB

by alex.loubyansky＠jboss.com

If that's a choice binding based on a super class then you could try: - jboss-specific binding e.g. http://anonsvn.jboss.org/repos/jbossas/projects/metadata/trunk/src/main/j... (here you would uncomment @JBossXmlModelGroup annotation, hopefully it's clear enough?) - or look here at enterpriseBeans property http://anonsvn.jboss.org/repos/jbossas/projects/metadata/trunk/src/main/j... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227633#4227633 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227633

15 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - org.jboss.test.messaging.jms.ConnectionTest failiin

by clebert.suconic＠jboss.com

The test will aways fail if running from eclipse. It started failing at r6605: r6605 | timfox | 2009-04-28 13:28:45 -0500 (Tue, 28 Apr 2009) | 1 line | | https://jira.jboss.org/jira/browse/JBMESSAGING-1581 | | if you update the repository to r6604, the test will aways pass on eclipse, and it will aways fail on 6605. And Hudson shows occasional failures. http://hudson.qa.jboss.com/hudson/view/JBM%202/job/JBM2-tests/4724/testRe... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227628#4227628 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227628

15 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Scoped deployments in AS 5.x

by beve

anonymous wrote : This is no longer necessary in AS 5 so we should follow the standard mechanism, using the jboss-classloader.xml. Glad I asked :) jboss-classloader.xml it is then. Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227617#4227617 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227617

15 years

1
0
0 / 0

[Design of JBoss ESB] - Re: Scoped deployments in AS 5.x

by Kevin.Conner＠jboss.com

The configuration in deployment.xml just proxies through to the app server code, we do not do anything with it. The main reason for doing this within the AS 4 deployer was probably a consequence of the app server's restriction in only allowing a single deployer per deployment, so each deployer was responsible for handling this. This is no longer necessary in AS 5 so we should follow the standard mechanism, using the jboss-classloader.xml. Kev View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227564#4227564 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227564

15 years

1
0
0 / 0

[QA of JBoss Portal] - Re: Problem with Tomcat SSO valve while being in 'Admin' rol

by sohil.shah＠jboss.com

anonymous wrote : | But from my point of view, the behaviour in situation when you are in role "Admin" (or "User") and not in "Authenticated" is not logical. | Needing an "Authenticated" Threshold only makes the difference between an authenticated user and an anonymous user. After that within authenticated state itself, resources are access controlled based on whether they have "Admin" role, "User" role etc. Atleast thats the default security policy of portal we ship out of the box. To change this, you can modify the security constraints I mentioned in portal server configuration. I thought you needed a solution that would work with the out of the box portal policy. But, looks like you are looking to modify the default portal security policy, which is fine too. Try the first option I suggested and see if that works. You will need to add the "User" and "Admin" role references in the web.xml instead of the Authenticated we have today anonymous wrote : | Solution may be to inform our customers that for correct usage of Tomcat SSO Valve, they must have users in their web applications in both roles "Admin" and "Authenticated" (or "User" and "Authenticated" for normal non-admin users). | Yes that is correct for the default security policy that we ship with Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227549#4227549 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227549

15 years

1
0
0 / 0

[Design of JBossXB] - Re: problem parsing sip.xml with JBossXB

by deruelle_jean

Hi, I stumbled on a new problem, but that might be due to my newbieness on JAXB still. The sip app.xsd http://www.jcp.org/xml/ns/sipservlet/sip-app_1_1.xsd defines an element called condition which is abstract and many elements such as and, or, equals ... that are child of this condition (belong to the same substitutiongroup). My corresponding mapping classes are available here : http://mobicents.googlecode.com/svn/trunk/servers/sip-servlets/sip-servle... http://mobicents.googlecode.com/svn/trunk/servers/sip-servlets/sip-servle... http://mobicents.googlecode.com/svn/trunk/servers/sip-servlets/sip-servle... When I try to load this sip.xml : http://mobicents.googlecode.com/svn/trunk/servers/sip-servlets/sip-servle... I get the following exception : Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: and not found as a child of pattern | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203) | at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168) | at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:199) | at org.jboss.deployers.vfs.spi.deployer.JBossXBDeployerHelper.parse(JBossXBDeployerHelper.java:170) | at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:132) | at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:118) | at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256) | at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:188) | at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:323) | ... 22 more | Caused by: org.jboss.xb.binding.JBossXBRuntimeException: and not found as a child of pattern | at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:400) | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401) | at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) | at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) | at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) | at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.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) | ... 30 more | 17:25:41,319 INFO [TomcatConvergedDeployer] vfsfile:/home/deruelle/servers/jboss-5.0.1.G Any help would be appreciated on how to make the AndMetaData a child of ConditionMetaData Thanks in advance Best regards Jean Deruelle View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227538#4227538 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227538

15 years

1
0
0 / 0

[Design of JBoss ESB] - Scoped deployments in AS 5.x

by beve

In ESB 4.x you can specify that a deployment be scoped by configuring this in deployment.xml: <jbossesb-deployment> | <depends>jboss.esb:test=server</depends> | <depends>jboss.esb.qa.junit.destination:service=Queue,name=esb_gateway_channel_versioned</depends> | <depends>jboss.esb.qa.junit.destination:service=Queue,name=esb_channel_versioned</depends> | <loader-repository> | org.jboss.soa.esb:loader=simple-scoped | <loader-repository-config> | java2ParentDelegaton=false | </loader-repository-config> | </loader-repository> | </jbossesb-deployment> In AS 5.x something similar can be done by adding a META-INF/jboss-classloading.xml file to a deployment. I'm guessing that our deployers should act upon a loader-repository element in deployment.xml and take care of this when a .esb archive is deployed into AS 5, and not force users to declare such a file? /Daniel View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4227536#4227536 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4227536

15 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums April 2009