October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBRULES-44) Dynamic proxy for shadow fact support

by Edson Tirelli (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-44?page=all ] Edson Tirelli updated JBRULES-44: --------------------------------- Summary: Dynamic proxy for shadow fact support (was: Dynamic proxy for adding change listener support to user objects) Component/s: Drl Parser/Builder Manual Reteoo Fix Version/s: 3.1-m1 (was: 3.1-m3) Affects Version/s: 3.1-m1 Description: The idea is to use dynamic proxies to support shadow facts. So changes to the facts can be queued up, and the shadows refreshed when propagation has finished. (was: Proxy provides change listener support, which can automatically notify the enging of changes. Further to this, shadow copies can be made of fields, and the changes to the facts can be queued up, and the shadows refreshed when propagation has finished.) Priority: Major (was: Minor) > Dynamic proxy for shadow fact support > ------------------------------------- > > Key: JBRULES-44 > URL: http://jira.jboss.com/jira/browse/JBRULES-44 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Reteoo, Manual, Drl Parser/Builder > Affects Versions: 3.1-m1 > Reporter: Michael Neale > Assigned To: Michael Neale > Fix For: 3.1-m1 > > > The idea is to use dynamic proxies to support shadow facts. So changes to the facts can be queued up, and the shadows refreshed when propagation has finished. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBRULES-44) Dynamic proxy for shadow fact support

by Edson Tirelli (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-44?page=all ] Edson Tirelli reassigned JBRULES-44: ------------------------------------ Assignee: Edson Tirelli (was: Michael Neale) > Dynamic proxy for shadow fact support > ------------------------------------- > > Key: JBRULES-44 > URL: http://jira.jboss.com/jira/browse/JBRULES-44 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Reteoo, Manual, Drl Parser/Builder > Affects Versions: 3.1-m1 > Reporter: Michael Neale > Assigned To: Edson Tirelli > Fix For: 3.1-m1 > > > The idea is to use dynamic proxies to support shadow facts. So changes to the facts can be queued up, and the shadows refreshed when propagation has finished. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-316) The view attribute functionality of s:link tag extension

by Slawomir Trybus (JIRA)

The view attribute functionality of s:link tag extension -------------------------------------------------------- Key: JBSEAM-316 URL: http://jira.jboss.com/jira/browse/JBSEAM-316 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.0.1 Environment: N/A Reporter: Slawomir Trybus Priority: Minor Fix For: 1.1 I'd like to propose extending of the <s:link .../> tag functionality in the view attribute area by adding value-binding feature. example: <s:link view="#{...}" /> There is inevitible to create another method returning outcome string with the action attribute in the current functionality of this tag. Such a solution would provide derived url without extra method execution. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

3
3
0 / 0

[JBoss JIRA] Closed: (JBAS-3148) Unified JGroups MBean to configure the channel running inside the JBoss AS.

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3148?page=all ] Brian Stansberry closed JBAS-3148. ---------------------------------- Resolution: Done Assignee: Brian Stansberry (was: Jerry Gauthier) > Unified JGroups MBean to configure the channel running inside the JBoss AS. > --------------------------------------------------------------------------- > > Key: JBAS-3148 > URL: http://jira.jboss.com/jira/browse/JBAS-3148 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Priority: Critical > Fix For: JBossAS-5.0.0.Beta > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Add an MBean for the JGroups JChannelFactory and configure the ClusterPartition to use it. Determine where the MultiplexerConfig comes from. Once JBossCache supports it, ensure that all cache config files use the JChannelFactory by default. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (EJBTHREE-477) Implement @WebServiceRef and <service-ref>

by Georges Berscheid (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-477?page=comments#action_12344450 ] Georges Berscheid commented on EJBTHREE-477: -------------------------------------------- repos/jbossas/trunk/ejb3/src/main/org/jboss/injection/WebServiceHandler.java throws an exception in loadXml() if <mapped-name> is not defined for a <service-ref>. This is however not allowed by the ejb-jar.xml 2.1 schema. Hence, currently is doesn't seem to be possible to use a<service-ref> in the ejb-jar.xml file. I thought it might be helpful to add this. > Implement @WebServiceRef and <service-ref> > ------------------------------------------ > > Key: EJBTHREE-477 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-477 > Project: EJB 3.0 > Issue Type: Task > Reporter: Bill Burke > Assigned To: William DeCoste > Priority: Critical > Fix For: EJB 3.0 RC10 - FD > > > This will be fun!!!! > Take a look at code in EJB 2.1 container. DO NOT USE THAT CODE DIRECTLY. I want to start removing dependencies on that code. You can also work with WS team on this too. This should be a HIG PRIORITY task. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3701) SystemPropertiesService does not properly generate server path on windows

by Anil Saldhana (JIRA)

SystemPropertiesService does not properly generate server path on windows ------------------------------------------------------------------------- Key: JBAS-3701 URL: http://jira.jboss.com/jira/browse/JBAS-3701 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-4.0.4.GA Reporter: Anil Saldhana Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.6.CR1 <mbean code="org.jboss.varia.property.SystemPropertiesService" name="jboss:type=Service,name=SystemProperties"> <attribute name="Properties" replace="false"> log.file.location=${jboss.server.home.dir}/log </attribute> </mbean> The jboss.server.home.dir is not string replaced properly on windows. I suspect it to be related to the Property class in the Jboss common module. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBXB-86) Add support for XInclude

by Adrian Brock (JIRA)

Add support for XInclude ------------------------ Key: JBXB-86 URL: http://jira.jboss.com/jira/browse/JBXB-86 Project: JBoss XML Binding (JBossXB) Issue Type: Feature Request Affects Versions: JBossXB-1.0.0.CR6 Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossXB-1.0.0.CR7 As per the discussion thread, add support for XInclude to JBossXB. e.g. <some-xml> <xi:include href="some_included.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> <xi:include href="some_other.xml" xmlns:xi="http://www.w3.org/2001/XInclude"/> </some-xml> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBXB-78) NPE marshalling simple anonymous types

by Alexey Loubyansky (JIRA)

NPE marshalling simple anonymous types -------------------------------------- Key: JBXB-78 URL: http://jira.jboss.com/jira/browse/JBXB-78 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-1.0.0.CR6 Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Fix For: JBossXB-1.0 If a complex type contains an element which contains an anonymous simple type with restriction. E.g: - <complexType name='TelephoneNumber'> <sequence> <element name='areaCode' nillable='true'> <simpleType> <restriction base='string'> <pattern value='[0-9]{5}'/> </restriction> </simpleType> </element> <element name='number' nillable='true' type='string'/> </sequence> </complexType> This causes a NullPointerException because the class MarshallerImpl is expecting the type to have a QName. The exception is at the bottom of the e-mail, the attached war can be used to reproduce the problem (use SoapUI to send the request message). Looking at the marshalSimpleType method of the MarshallerImpl class the QName of the type is used to check if it is QName or NOTATION, checking that the QName is set before using it appears to fix this problem. Second the method marshalCharacters also makes use of the QName of the type to check if the namespace of the type is the schema namespace. For both of these problems checking for null before using the QName appears to fix the problem and my web service works as expected (I have attached a patch containing my changes). Could you please let me know if this is an appropriate fix? Regards, Darran Lofthouse. java.lang.NullPointerException at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalSimpleType (MarshallerImpl.java:458) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalElementTyp e(MarshallerImpl.java:415) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalElement(Ma rshallerImpl.java:331) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalElementOcc urence(MarshallerImpl.java:311) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalParticle(M arshallerImpl.java:730) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalModelGroup Sequence(MarshallerImpl.java:920) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalModelGroup (MarshallerImpl.java:860) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalParticle(M arshallerImpl.java:641) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalComplexTyp e(MarshallerImpl.java:608) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalElementTyp e(MarshallerImpl.java:419) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalElement(Ma rshallerImpl.java:331) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshalElementOcc urence(MarshallerImpl.java:311) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshallInternal( MarshallerImpl.java:210) at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.marshal(Marshalle rImpl.java:168) at org.jboss.ws.jaxb.JBossXBMarshallerImpl.marshal(JBossXBMarshallerImpl.ja va:146) at org.jboss.ws.jaxrpc.encoding.JAXBSerializer.serialize(JAXBSerializer.jav a:107) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBXB-81) DTDMarshaller: redundant startElement call for complex elements with character content

by Alexey Loubyansky (JIRA)

DTDMarshaller: redundant startElement call for complex elements with character content -------------------------------------------------------------------------------------- Key: JBXB-81 URL: http://jira.jboss.com/jira/browse/JBXB-81 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-1.0.0.CR6 Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Fix For: JBossXB-1.0 Characters content of an element with mixed content will appear in a child element with the same name as the element being marshalled. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBXB-77) wrong parent object for nested model groups

by Alexey Loubyansky (JIRA)

wrong parent object for nested model groups ------------------------------------------- Key: JBXB-77 URL: http://jira.jboss.com/jira/browse/JBXB-77 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-1.0.0.CR6 Reporter: Alexey Loubyansky Assigned To: Alexey Loubyansky Fix For: JBossXB-1.0 In the current impl If the model group binding is used then the parent object for a model group on the stack that will be the object created for the last element on the stack. Even if the parent of the model group is another model group. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 3 months

1
3
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2006