September 2007 - jboss-dev-forums

[Design of JBoss/Tomcat Integration] - Stopping connectors early in the shutdown process

by bstansberry＠jboss.com

(Related to http://jira.jboss.com/jira/browse/JBAS-4735) When the work was done to delay starting the Tomcat connectors until a START_NOTIFICATION_TYPE JMX notification was received from ServerImplMBean, why wasn't STOP_NOTIFICATION_TYPE also handled, to allow early shutdown of the connectors? Do the connectors cleanly handle having their stop() method invoked while they are servicing requests; i.e allow requests to complete but disallow new requests? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089150#4089150 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089150

17 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: So what does unification mean for the ejb containers

by wolfc

EJB 3 will barf if it encounters such a DD. How will we keep the two apart? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089090#4089090 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089090

17 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: So what does unification mean for the ejb containers

by alex.loubyansky＠jboss.com

I guess the majority of EJB2 applications would be ported from previous JBoss versions rather than developed from scratch for JBoss 5. In that case, it would be better to have the same EJB2 containers and configuration. That work well and, AFAIK, are in the maintenance and there haven't been plans to major refactor or add new features. Plus, new EJB2 containers would be one more module to maintain, support, document, etc. What would be the reasons to go for it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089066#4089066 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089066

17 years, 3 months

1
0
0 / 0

[Design of JBossXB] - Re: JBossXB-2.0.0.CR5

by alex.loubyansky＠jboss.com

It's not because there wildcards but because the properties order doesn't match the elements order in the schema. If I don't specify the propOrder then the properties will be processed in the following sequence: key; descriptions; proxyFactoryConfig; class; proxyFactory; name; wildcard; invokerProxyBindingName; id; invokerMBean; And this will be the sequence of the elements in the schema. Now elements are parsed in this sequence: start: invoker-proxy-binding start: description end: description start: description end: description start: description end: description start: invoker-proxy-binding-name end: invoker-proxy-binding-name start: invoker-mbean end: invoker-mbean start: proxy-factory UNRESOLVED: proxy-factory end: proxy-factory Everything after invoker-mbean is going to be wildcard content because we reached the last element in the sequence. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089046#4089046 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089046

17 years, 3 months

1
0
0 / 0

[Design of JBossXB] - Re: container-configuration model group problem

by alex.loubyansky＠jboss.com

You also had to add descriptions property to the propOrder list. Otherwise, it was treated as wildcard content. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089032#4089032 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089032

17 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: [GPD 3.1.0.SP1] NPE when opening process

by koen.aers＠jboss.com

Please get a JBoss id so that you can file this as a JIRA issue. Make sure to post the entire processdefinition file. Regards, Koen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089021#4089021 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089021

17 years, 3 months

1
0
0 / 0

[Design of JBossXB] - container-configuration model group problem

by scott.stark＠jboss.org

After I updated the ejb container config metadata I started seeing this new error: anonymous wrote : | Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to start {http://java.sun.com/xml/ns/javaee}description: the element is not repeatable, repeatable parent expected to be a model group but got element {http://www.jboss.com/xml/ns/javaee}container-configuration | at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endRepeatableParent(SundayContentHandler.java:672) | at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:311) | at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:402) | 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:180) | ... 23 more | 1687 DEBUG [JBoss5xEverythingUnitTestCase] testEverything took 1672ms | 1687 DEBUG [JBoss5xEverythingUnitTestCase] ==== Stopping testEverything ==== | 1687 DEBUG [JBoss5xEverythingUnitTestCase] ==== tornDown org.jboss.test.ejb.metadata.test.JBoss5xEverythingUnitTestCase ==== | | I originally saw this problem in the metadata project, but have copied the changes over to the jbossxb project so that the JBoss5xEverythingUnitTestCase shows the problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089014#4089014 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089014

17 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: ManagedOperation aspects for the ProfileService.Manageme

by alesj

"scott.stark(a)jboss.org" wrote : "alesj" wrote : | | The question is, should a change of Fields.VALUE value always trigger both changes/invocation as well --> changing metadata property and runtime component. | No, only when the value is set on behalf of the profileservice update. | Is there a way to write such an aop pointcut that is caller aware? But it's the ManagedProperty that gets the first hit from profileservice, making ManagedProperty more appropriate to be aspectized for the setValue invocation. OK, I'll impl something and then we can discuss further. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089009#4089009 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4089009

17 years, 3 months

1
0
0 / 0

[Design of JBossXB] - Re: JBossXB-2.0.0.CR5

by scott.stark＠jboss.org

Why does one need to specify the property order for these wildcard type bindings? Is it that the unknown elements need to come at the end of the type parsing? Its going to make it tedious to have to specify all the elements in the larger metadata types like the ejb container. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088992#4088992 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088992

17 years, 3 months

1
0
0 / 0

[Design of POJO Server] - So what does unification mean for the ejb containers

by scott.stark＠jboss.org

Right now I'm going through the TODOs in the ContainerConfigurationMetaData, but some items like the legacy interceptors and invoker proxy config only apply to the ejb2 container. Are we going to try to deprecate these and transition the implementation to a proper aspectized container that leverages remoting and aop like the ejb3 container does, or just phase these legacy item out over time? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088988#4088988 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088988

17 years, 3 months

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 September 2007