July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBXB-16) support for binding with jaxb xsd annotations

by Alexey Loubyansky (JIRA)

[ https://jira.jboss.org/jira/browse/JBXB-16?page=com.atlassian.jira.plugin... ] Alexey Loubyansky closed JBXB-16. --------------------------------- Resolution: Out of Date At this point the most useful jaxb xsd annotations are supported and there haven't been requests to make sure every jaxb annotation is covered. So, this general issue is going to be closed. And if a there is a need to add support for other annotations, a separate issue can be opened. > support for binding with jaxb xsd annotations > --------------------------------------------- > > Key: JBXB-16 > URL: https://jira.jboss.org/jira/browse/JBXB-16 > Project: JBoss XML Binding (JBossXB) > Issue Type: Feature Request > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > XML to Java bindings should be customizable with annotations in xsd following the jaxb2.0 spec. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCL-21) Recursive use of JDKCheckerFactory

by Adrian Brock (JIRA)

Recursive use of JDKCheckerFactory ---------------------------------- Key: JBCL-21 URL: https://jira.jboss.org/jira/browse/JBCL-21 Project: JBoss ClassLoader Issue Type: Task Components: ClassLoader Affects Versions: JBossCL.2.0.0.Beta12 Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossCL.2.0.0.CR1 The JDKCheckerFactory could end up calling itself if the classloader used in the class initializer is a BaseClassLoader. If this occurs then we should just temporarily use the AbstractJDKChecker until the class is fully initialized. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBXB-106) xsd:attribute ref not supported by SchemaBinding

by Anil Saldhana (JIRA)

xsd:attribute ref not supported by SchemaBinding ------------------------------------------------ Key: JBXB-106 URL: http://jira.jboss.com/jira/browse/JBXB-106 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Affects Versions: JBossXB-2.0.0.CR2 Reporter: Anil Saldhana Priority: Critical Refer to forum for additional details. -- 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

16 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBREFLECT-29) Allow MetaData to passed in explictly to the ConstructorJoinpoint

by Adrian Brock (JIRA)

Allow MetaData to passed in explictly to the ConstructorJoinpoint ----------------------------------------------------------------- Key: JBREFLECT-29 URL: https://jira.jboss.org/jira/browse/JBREFLECT-29 Project: JBoss Reflection Issue Type: Task Components: Joinpoint Affects Versions: JBossReflection.2.0.0.Beta12 Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossReflection.2.0.0.CR1 Add a new factory method to the JoinPointFactory to pass in an opaque object to the constructor. This will allow the MetaData to passed through to AOP when required. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-320) Pass the MetaData to the AOPJoinpointConstructor explictly

by Adrian Brock (JIRA)

Pass the MetaData to the AOPJoinpointConstructor explictly ---------------------------------------------------------- Key: JBMICROCONT-320 URL: https://jira.jboss.org/jira/browse/JBMICROCONT-320 Project: JBoss MicroContainer Issue Type: Task Components: AOP Affects Versions: JBossMC.2.0.0.Beta16 Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossMC.2.0.0.CR1 The AOPConstructorJoinpoint is getting confused by other uses of the BeanInfo/ConstructorJoinPoint since the MetaData is getting passed on the MetaDataStack. Since the usage is effectively "recursive" the MetaData context "leaks". The MetaData should be passed in explictly to AOP to avoid this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBXB-54) review public API and move to a new package

by Alexey Loubyansky (JIRA)

[ https://jira.jboss.org/jira/browse/JBXB-54?page=com.atlassian.jira.plugin... ] Alexey Loubyansky closed JBXB-54. --------------------------------- Resolution: Out of Date This issue is out of date. > review public API and move to a new package > ------------------------------------------- > > Key: JBXB-54 > URL: https://jira.jboss.org/jira/browse/JBXB-54 > Project: JBoss XML Binding (JBossXB) > Issue Type: Task > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > Includes reviewing Adrian's prototype and merging useful stuff. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBPORTAL-531) Import/Export of Portal Page and Portlet Database Settings

by Thomas Heute (JIRA)

[ https://jira.jboss.org/jira/browse/JBPORTAL-531?page=com.atlassian.jira.p... ] Thomas Heute closed JBPORTAL-531. --------------------------------- Fix Version/s: (was: 2.8 Final) Resolution: Won't Fix The solution would be part of the redesign work we intend to do > Import/Export of Portal Page and Portlet Database Settings > ---------------------------------------------------------- > > Key: JBPORTAL-531 > URL: https://jira.jboss.org/jira/browse/JBPORTAL-531 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal Server > Affects Versions: 2.2 Final, 2.6.2 Final > Reporter: James Williams > > There is a need to export portal page and portlet setting changes that are made via the "management" portlet GUI interface, and then import those changes in another JBoss Portal instance. > For example - If I want to migrate all of my QA portal page/portlet changes to Production today, I have to hard code those changes in the XML descriptors. A db export/import utility is preferred. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (SECURITY-263) Document JBoss Negotiation with FreeIPA

by Darran Lofthouse (JIRA)

Document JBoss Negotiation with FreeIPA --------------------------------------- Key: SECURITY-263 URL: https://jira.jboss.org/jira/browse/SECURITY-263 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 2.0.3.Beta2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMETA-81) BasicJndiBindingPolicy uses JAR name as Base

by Andrew Lee Rubinger (JIRA)

BasicJndiBindingPolicy uses JAR name as Base -------------------------------------------- Key: JBMETA-81 URL: https://jira.jboss.org/jira/browse/JBMETA-81 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta30 Reporter: Andrew Lee Rubinger Assignee: Andrew Lee Rubinger Introduced by JBMETA-78, in order to fulfill http://wiki.jboss.org/wiki/DevJNDIBinding. Powering the "base" notion is deploymentScopeBaseName, which in the presence of a JAR, is the name of the JAR. This should not be used as a base. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-2087) show apt. message when archive type is not supported

by Prabhat Jha (JIRA)

show apt. message when archive type is not supported ---------------------------------------------------- Key: JBPORTAL-2087 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2087 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.6 Final Reporter: Prabhat Jha Assignee: Sohil Shah I don't think it's a bug. I think CMS can only upload archive in zip format. I uploaded a .tgz file and I see 14:24:40,013 ERROR [STDERR] Caused by: java.io.IOException: Negative seek offset 14:24:40,013 ERROR [STDERR] at java.io.RandomAccessFile.seek(Native Method) 14:24:40,013 ERROR [STDERR] at org.apache.tools.zip.ZipFile.positionAtCentralDirectory(ZipFile.java:365) 14:24:40,013 ERROR [STDERR] at org.apache.tools.zip.ZipFile.populateFromCentralDirectory(ZipFile.java:243) 14:24:40,013 ERROR [STDERR] at org.apache.tools.zip.ZipFile.<init>(ZipFile.java:142) 14:24:40,013 ERROR [STDERR] at org.apache.tools.zip.ZipFile.<init>(ZipFile.java:101) 14:24:40,013 ERROR [STDERR] at org.jboss.portal.cms.impl.jcr.command.StoreArchiveCommand.execute(StoreArchiveCommand.java:84) 14:24:40,013 ERROR [STDERR] ... 26 more It should display appropriate message if it can not upload a file of particular type. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 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-jira July 2008