November 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Web Services] - Re: [Productivity] Level 4 - Production

by alessio.soldano＠jboss.com

Hi Stefano, "maeste" wrote : What I would jbossws provide at this level is a sophisticated log system, giving me the opportunity to understand who is using my service and how. | My idea is to provide a log (and docs to explain how to enable/disable or set a dedicated file and so on) awstats compatible. I know awstats is designed for web apps, but I think you (we if I get time to contribute) can think how to provide compatible logs, because it is grat for immediate statistic and graphs. Graphical stats have the plus of being really powerful in providing informations in a way that is both brief and effective. For this reason I like your idea of giving the ws administrator a mean of viewing stats graphically. We have to think how this could be achieved; for example the informations we are interested in might be not all in the http header; most probably we would have to create a new log format and something able to deal with it (perhaps using awstat). Anyway, generally speaking, I think the idea of having something like a WS log repository to query with different filters for getting informations on both pre-defined and custom (the admin decides through the jmx-console) time period is definitively interesting. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104221#4104221 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104221

18 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2 and test framework

by clebert.suconic＠jboss.com

anonymous wrote : Does anyone have any views? If we ever rewrite our test framework, maybe we should just reuse the JBoss testsuite, and deploy our services in a JBoss instance, like everybody does. This would mean it would be easier to reuse our tests on the JBAS testsuite. Regarding the start/stop of the server, maybe we could run more tests for a single server kill, like the way I'm doing at: http://anonsvn.jboss.org/repos/jbossas/branches/JBPAPP_4_2/testsuite/src/... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104219#4104219 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104219

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJB3 AppClient - tests now pass but there are issues

by scott.stark＠jboss.org

anonymous wrote : log.warn("FIXME: using an unsupported hack to get metadata"); So we need a plan on what the supported mechanism for configuring the client is. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104207#4104207 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104207

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJB3 AppClient - tests now pass but there are issues

by adrian＠jboss.org

"wolfc" wrote : "adrian(a)jboss.org" wrote : I'd have thought JPA is a valid client api, it's JavaSE? | | But then I'm not a big fan of client side -> tier 3 type nonsense. :-) | By spec you can use a PersistenceUnit (see http://jira.jboss.com/jira/browse/EJBTHREE-1050). But Emmanuel doesn't like that, so he won't give me a remote persistence unit. :-) Isn't it just a case of proxying the persistent context requests over remoting and making sure the request handling on the server side runs in any UserTransaction context created on the client? I think we can do that in the appserver without hibernate having to implement it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104200#4104200 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104200

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJB3 AppClient - tests now pass but there are issues

by scott.stark＠jboss.org

"adrian(a)jboss.org" wrote : I've added the parsing to the ClientLauncher which revealed a number of | other issues, "fixing" these now makes the ejb3 appclient tests pass. | | * HARDWIRING | | I had to hack the resolver to hardwire the schemalocation -> annotated class | There must be a better way to do this? | Perhaps we can include a META-INF/schema-binding.xml in the jar | and jbossxb can look for this config at bootstrap/hotdeployment? | I would say only the launcher should look for this config file to avoid the usual problem of having defaults bundled in jars that end up conflicting with server config files like the metadata-beans.xml SchemaResolverConfig config. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104198#4104198 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104198

18 years, 4 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: ManagedObject stuff for AOP

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : | But that would require the MC being updated to also do that. | The MC based annotation parsing is prototyped in the JBossXB testsuite | so speak to Ales about getting it ported. | This is here: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/common/jbossxb-builder/trunk/s... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104181#4104181 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104181

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJB3 AppClient - tests now pass but there are issues

by wolfc

Rev 67024 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104179#4104179 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104179

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJB3 AppClient - tests now pass but there are issues

by adrian＠jboss.org

"wolfc" wrote : Here's my ClientLauncher: | I like it better, because it doesn't do any parsing and it uses server side metadata. So if you don't mind, I'll commit it. | Go ahead, this is better (like I said above) because it will pick up the profile server and deployer overrides to the metadata. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104178#4104178 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104178

18 years, 4 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJB3 AppClient - tests now pass but there are issues

by scott.stark＠jboss.org

"wolfc" wrote : | Nope, it's the patch above (and then some). It overwrites the change made by Adrian. Shall I commit? I would say yes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104175#4104175 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104175

18 years, 4 months

1
0
0 / 0

[Design of Management Features on JBoss] - Re: java.awt.headless by default

by dimitris＠jboss.org

That's a JVM property so it's all or nothing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104174#4104174 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4104174

18 years, 4 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 November 2007