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

[Design of POJO Server] - Re: Stable deployment API for tools

by jason.greene＠jboss.com

Also FYI, JSR88 will be removed from EE7, although we have quite a ways to go for that :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211618#4211618 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211618

17 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - Re: statefull vs stateless delegation classes

by alex.guizar＠jboss.com

Won't caching make expression evaluation in delegation properties unfeasible? <delegation class="org.example.Taco"> | <sauce>${actor.sauce.preference}</sauce> | </delegation> If the above is not a requirement (I have wished for it more than once, and not just me, see JBPM-1752) then we can have a single object per process definition. Otherwise we need a pool. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211611#4211611 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211611

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - State of JDK logging in jboss-logging-jdk

by david.lloyd＠jboss.com

The jboss-logging-jdk module has three different implementations of java.util.logging.LogManager in it. Rather than adding a fourth, is it OK if I just replace org.jboss.logging.jdk.JBossJDKLogManager? In addition to disabling the reset() method, my implementation completely disables configuration, and fixes about half a dozen bugs. Since it disables the configuration API, it might be considered a compatibility change. In any case it will likely mean a 2.1.0 release. Alternately I could put it in a separate class, or even a separate module - either way it needs to be on the boot classpath. Thoughts? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211600#4211600 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211600

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Stable deployment API for tools

by max.andersen＠jboss.com

with respect to JSR-88 then that was attempted once a loong time ago and the conclusion back then was that it only seemed to implement just enough for the TCK to pass but when trying to actually use it that just failed. And when we then were told it was not supported and not really something we thought would be living on it was dropped. If that has changed then cool. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211568#4211568 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211568

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Logging integration requirements

by david.lloyd＠jboss.com

Trying to put this more plainly, if I were looking at it from a user's perspective, my expectation might fall along one of these lines: 1) All log messages that originate from my log categories get handled separately. 2) All log messages that originate from loggers within my deployment (regardless of category) get handled separately. 3) All log messages that originate or relate to my deployment in any way (regardless of category or originating module) get handled separately. We obviously can do (1) now with no changes. The question is, do we want to do (2) or (3)? Are existing solutions good enough? Even (3) is doable, if we're willing to monkey with the microcontainer enough to provide hooks into any code that invokes a task or method in a user's deployment (maybe these hooks already exist and we just aren't utilizing them). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211567#4211567 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211567

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Bringing the trunk profile service changes to 5_x

by emuckenhuber

"scott.stark(a)jboss.org" wrote : "emuckenhuber" wrote : | | Furthermore - what's actually DeploymentTemplate.updateTemplate supposed to do? | | It's not implemented and i'm wondering why you should not call ManagementView.updateComponent ? | | Which is then the last thing referencing a VFSDeployment. | | | The notion was that the template might need to create the attachments that define the deployment after it has a VFSDeployment because it may not have put out enough information in the VirtualFile returned by the first phase when applyTemplate was called. A template may not want to have a complete xml or file based view of the properties what it writes out. | Hmm looking at applyTemplate() in ManagementView again, i noticed that applyTemplate() is actually creating a real file in a profile and therefore bypassing the minimal synchronization we have for ModifiedDeployments. I think it would make more sense to use the DeploymentManager for this. So it could write the template into a temp file and then use deploymentManager to distribute and deploy it? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211559#4211559 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211559

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Logging integration requirements

by david.lloyd＠jboss.com

"scott.stark(a)jboss.org" wrote : Related to better tools integration, a notion of being able to capture all logging related to a deployment. In reality I think all we can do is capture the logging related to a MainDeployer.process context, but for the tools, this will generally be just for their deployment so it should be sufficient. It looks like one way, or perhaps the (recommended?) way to do this today is with TCLFilter, though I don't know if this is adequate, or if filters are the way to go going forward (once you get a few going, that might start to incur a pretty substantial overhead). Making an isolated logging context based on the process context is another idea, but even if there wasn't a bunch of work to make this work, this will only capture log messages directly generated by the deployment, not by other modules involved in actions performed by or on behalf of the deployment, which may or may not be useful (I think this is what you're referring to)? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211555#4211555 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211555

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Logging integration requirements

by adrian＠jboss.org

"scott.stark(a)jboss.org" wrote : Related to better tools integration, a notion of being able to capture all logging related to a deployment. In reality I think all we can do is capture the logging related to a MainDeployer.process context, but for the tools, this will generally be just for their deployment so it should be sufficient. | There already is a way to capture "deployment" (really context classloader) logging http://www.jboss.org/community/docs/DOC-11277 But I don't think that will capture all the deployment time logging since the application's TCL is only set for a very brief period during that time (e.g. during servlet initialization). I did do some stuff a long time ago where you could add "call logging" where you collect all logging for a particular thread/invocation on the server and then log it on the client. http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/projects/aop/trunk/asp... but it only works if you use aop-remoting. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211553#4211553 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211553

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Stable deployment API for tools

by scott.stark＠jboss.org

Ok, so an mbean variation of the DeploymentManager is the starting point. We just need some variation of the existing DeployUnitTestCase to validate the tools api usage is stable. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211548#4211548 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211548

17 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Logging integration requirements

by scott.stark＠jboss.org

Related to better tools integration, a notion of being able to capture all logging related to a deployment. In reality I think all we can do is capture the logging related to a MainDeployer.process context, but for the tools, this will generally be just for their deployment so it should be sufficient. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211545#4211545 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4211545

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