[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
[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
[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