September 2007 - jboss-dev-forums

[Design of POJO Server] - Re: JBossAppParsingDeployer issue (Repost)

by anil.saldhana＠jboss.com

An immediate issue that I am noticing is if there exists a jboss-app.xml that defines a security domain and there is no jboss.xml in the EAR, then the ApplicationMetaData that gets generated in the process has lost the merge from the ear level settings, because the merge of the security domain is currently being done in the JBossEJBParsingDeployer. So no jboss.xml, implies no invocation of the JBossEJBParsingDeployer. So should this merging be also done in the EjbParsingDeployer? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083262#4083262 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083262

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: JBossAppParsingDeployer issue

by anil.saldhana＠jboss.com

An immediate issue that I am noticing is if there exists a jboss-app.xml that defines a security domain and there is no jboss.xml in the EAR, then the ApplicationMetaData that gets generated in the process has lost the merge from the ear level settings, because the merge of the security domain is currently being done in the JBossEJBParsingDeployer. So no jboss.xml, implies no invocation of the JBossEJBParsingDeployer. So should this merging be also done in the JBossAppParsingDeployer? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083262#4083262 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083262

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - ServiceDeployer.deploy not seeing deployment errors

by scott.stark＠jboss.org

The http://jira.jboss.com/jira/browse/JBAS-4684 issue is due to the ServiceDeployer.deploy method not seeing the deployment error. This is due to the AbstractController.incrementState uninstalling context with errors: | ... | finally | { | lockWrite(); | if (error != null) | { | log.error("Error installing to " + toState.getStateString() + ": " + context.toShortString(), error); | uninstallContext(context, ControllerState.NOT_INSTALLED, trace); | errorContexts.put(context.getName(), context); | context.setError(error); | return false; | } | } | AbstractControllerContext.uninstall(ControllerState fromState, ControllerState toState) clears the error state, and the ServiceContext problem is nulled out when the CreateDestroyLifecycleAction.uninstallAction calls getServiceContext: | public ServiceContext getServiceContext() | { | try | { | serviceContext.proxy = getServiceProxy(); | } | catch (Exception ignored) | { | } | serviceContext.setProblem(getError()); | if (getState() == ControllerState.ERROR) | serviceContext.state = ServiceContext.FAILED; | return serviceContext; | } | The context after the ServiceDeployer.deploy calls start(context), the context is in a DESTROYED state, but has no problem set: | ObjectName: jboss.web.deployment:war=/custom-context | State: DESTROYED | Because of this, the MainDeployer.checkComplete call has no information about the failed deployment. If I just fail to null out the ServiceContext.problem then the deployment failure propagates as expected. However, it seem like we should not be able to transition out of the ERROR state to DESTROYED? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083243#4083243 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083243

18 years, 6 months

1
0
0 / 0

[Design of JBoss Portal] - Maven Migration Status

by wesleyhales

So I have a working Maven build (minus this problem) with the common module. I have also created the JbossPortal and JbossModules pom ready for all kinds of inheritance fun ;) The problem I am currently having is that it looks like maven does not allow us to set System Properties for use in the JVM from within a pom.xml file. i.e. when we set: | <pathelement location="${build.resources}"/> | (in the old ant build.xml) and use it in ImplodeTestCase as: | File foo_sarDir = new File(System.getProperty("build.resources") + "/test/implode/foo.sar"); | assertTrue(foo_sarDir.exists()); | ...the system property returns null and the test fails using maven. I also tried setting it via the maven-ant plugin to no avail. You can read any system property in the pom.xml (see this properties guide) but you cannot write to them via the pom. This is discussed on the maven mail list here. The suggested way is to pass a system property in with "mvn install -Dmyprop=whatever" on the command line. I have 2 possible solutions for this problem, but wanted to get input: 1.) Create a .bat & .sh file to add the parameter (but we still have to dynamically detect the file path to the resources or maybe we could use a relative path) 2.) or use code like this: | File f = new File(""); | String path = f.getAbsolutePath(); | File foo_sarDir = new File(path + "/target/test-classes/implode/foo.sar"); | this also occurs in LocaleFormatTestCase and URLNavigatorTestCase Let me know your thoughts, View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083231#4083231 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083231

18 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Unspecified XAException error code.

by clebert.suconic＠jboss.com

Thanks Adrian, I just looked over all the instantiations of MessagingXAException and we aways initialize the error code. Also, we don't use XA_RMERR anywhere. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083214#4083214 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083214

18 years, 6 months

1
0
0 / 0

[Design the new POJO MicroContainer] - docbook build error

by scott.stark＠jboss.org

After I introduced some chapter tags to fix the broken formatting of the book, I started seeing this error: | [INFO] [jdocbook:generate] | [INFO] building formatting result [/home/svn/JBossMC/jbossmc/docs/gettingstarted/en-US/target/docbook/pdf/gettingstarted.pdf] | Sep 11, 2007 3:51:33 PM org.apache.fop.hyphenation.Hyphenator getHyphenationTree | SEVERE: Couldn't find hyphenation pattern en | Sep 11, 2007 3:51:34 PM org.apache.fop.layoutmgr.inline.LineLayoutManager$LineBreakingAlgorithm updateData2 | WARNING: Line 1 of a paragraph overflows the available area. (fo:block, location: -1/-1) | Error at fo:static-content on line 1601 of jar:file:/home/svn/repository.jboss.com/maven2/net/sf/docbook/docbook/1.7...: | org.apache.fop.fo.ValidationException: Error(-1/-1): fo:page-sequence is not a valid child element of fo:flow. | [INFO] ------------------------------------------------------------------------ | [ERROR] BUILD ERROR | [INFO] ------------------------------------------------------------------------ | [INFO] XSLT problem | | Embedded error: error performing translation [; SystemID: jar:file:/home/svn/repository.jboss.com/maven2/net/sf/docbook/docbook/1.7...; Line#: 1601; Column#: -1] : org.apache.fop.fo.ValidationException: Error(-1/-1): fo:page-sequence is not a valid child element of fo:flow. | [INFO] ------------------------------------------------------------------------ | [INFO] For more information, run Maven with the -e switch | [INFO] ------------------------------------------------------------------------ | [INFO] Total time: 8 seconds | [INFO] Finished at: Tue Sep 11 15:51:34 PDT 2007 | [INFO] Final Memory: 26M/302M | [INFO] ------------------------------------------------------------------------ | [starksm@succubus gettingstarted]$ | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083209#4083209 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083209

18 years, 6 months

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: JBAS-4543 Design

by bstansberry＠jboss.com

Let's give preference to the kernel (bean) name. Another tiny step in getting JMX out of the middle of everything. :) What would happen if you annotate setServiceHAName and then set it to something other than the kernel via xml? Will the xml value win out? If yes, you can annotate setServiceHAName. If not we need to create another property and annotate that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083159#4083159 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083159

18 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: ManagedObject support in next messaging release

by scott.stark＠jboss.org

Yes, I would say it should be in AS or an AS specific codebase outside of the jms core. You simply need to annotate the service mbean code class: | import org.jboss.managed.api.ManagedOperation.Impact; | import org.jboss.managed.api.annotation.ManagementObject; | import org.jboss.managed.api.annotation.ManagementObjectID; | import org.jboss.managed.api.annotation.ManagementOperation; | import org.jboss.managed.api.annotation.ManagementParameter; | import org.jboss.managed.api.annotation.ManagementProperties; | import org.jboss.managed.api.annotation.ManagementProperty; | import org.jboss.managed.api.annotation.ViewUse; | | @ManagementObject(componentType=@ManagementComponent(type="JMSDestination",subtype="Queue"), properties=ManagementProperties.EXPLICIT) | class QueueService | { | | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083157#4083157 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083157

18 years, 6 months

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: JBAS-4543 Design

by JerryGauth

Brian, Now that the required version of the microcontainer is available, I can complete this issue. One question here - JBAS-4543 suggests that the service's ObjectName should be used first and the bean name should only be used as an alternative. Is this actually the case or should the bean name be preferred? For HAServiceMBeanSupport, the canonical name of the service is "jboss.ha:service=HASingletonDeployer" while the bean name is "HASingletonDeployer". Note that I can't use setServiceHAName() unless we want to use the bean name since this name would be set on initialization and we wouldn't retrieve the canonical name. Of course it would be trivial to add another getter/setter to the class to accommodate the bean name. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083145#4083145 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083145

18 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: ManagedObject support in next messaging release

by clebert.suconic＠jboss.com

> or 1.4.0.GA to be usable in jbossas5/4.x, a separate integration layer is needed to isolate the jbossas specific dependencies Shouldn't this integration with MC exist on jbossas/trunk? on that case there is no need to hold the 1.4.0.GA release? JBossMessaging, as you said, could be both used by JBAS 4 and JBAS 5... so we can't implement those MC interfaces directly, right? anyway... do you have any other service as an example with what needs to be done? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083141#4083141 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083141

18 years, 6 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-dev-forums September 2007