March 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBVFS-85) Implement close on ZipEntryHandler

by Ales Justin (JIRA)

Implement close on ZipEntryHandler ---------------------------------- Key: JBVFS-85 URL: https://jira.jboss.org/jira/browse/JBVFS-85 Project: JBoss VFS Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.GA Reporter: Ales Justin Assignee: Marko Strukelj Fix For: 2.0.1.Beta1 ZipEntryHandler is missing close/doClose method impl. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBVFS-86) Add a cleanup method to VirtualFIle

by Ales Justin (JIRA)

Add a cleanup method to VirtualFIle ----------------------------------- Key: JBVFS-86 URL: https://jira.jboss.org/jira/browse/JBVFS-86 Project: JBoss VFS Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.0.0.GA Reporter: Ales Justin Assignee: Ales Justin Fix For: 2.0.1.Beta1 VirtualFile should have a cleanup method. e.g. this is where we do temp file deletion, etc -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (JBAS-6341) Upgrade JBossWS Native to 3.0.5.GA

by Richard Opalka (JIRA)

Upgrade JBossWS Native to 3.0.5.GA ---------------------------------- Key: JBAS-6341 URL: https://jira.jboss.org/jira/browse/JBAS-6341 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Web Services Reporter: Richard Opalka Assignee: Richard Opalka Fix For: JBossAS-5.1.0.Beta1 Was fixed with JBAS-6340 -- 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, 10 months

3
10
0 / 0

[JBoss JIRA] Created: (JBMETA-39) jboss-client_5_0.xsd element order should not be required as its inconsistent with previous dtds

by Scott M Stark (JIRA)

jboss-client_5_0.xsd element order should not be required as its inconsistent with previous dtds ------------------------------------------------------------------------------------------------ Key: JBMETA-39 URL: http://jira.jboss.com/jira/browse/JBMETA-39 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta15 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: 1.0.0.CR1 The sequence declared by the xsd is inconsistent with the element ordering of previous dtds. For all of these optional elements, the order should not matter. -- 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, 10 months

4
11
0 / 0

[JBoss JIRA] Created: (JBCOMMON-81) java.lang.NoSuchMethodError during processing xml files

by cset telo (JIRA)

java.lang.NoSuchMethodError during processing xml files ------------------------------------------------------- Key: JBCOMMON-81 URL: https://jira.jboss.org/jira/browse/JBCOMMON-81 Project: JBoss Common Issue Type: Bug Environment: - HP-UX release B.11.23, i64, vmunix: B11.23_LR FLAVOR=perf - Sun Java VM 1.5.0.14 Standard Edition (build 1.5.0.14-_25_jul_2008_05_19) Java HotSpot(TM) Server VM (build 1.5.0.14 jinteg:07.25.08-11:41 IA64, mixed mode) - JBoss 4.2.2.GA. - Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production - JDBC: Ojdbc1.4.jar - java starting parameters: -Xms128m -Xmx1024m Reporter: cset telo Assignee: Dimitris Andreadis java.lang.NoSuchMethodError during processing xml files: We are loading data from xml files (at about 0,5 Gb) to the database. The handler uses JSR-173 implementation for reading the xml files and for inserting data to database uses JDBC PreparedStatement's addBatch method. Periodically there are System.gc() method calls (each 15 seconds, 6 times) because of the many, but little objects. This time the database connection is closed and opened again. During this process we get java.lang.NoSuchMethodError: javax.resource.spi.ResourceAdapterInternalException: method <init>(Ljava/lang/String;Ljava/lang/Throwable;)V not found message into the log file. This event occurs different times after starting the process. There's no included stack trace. This object constructor exists; the implementation is in the \server\default\lib\jboss-j2ee.jar, which can be found in the installed JBoss. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBXB-182) Parse error if a choice is between an element and a sequence which also contains the element

by Matt Wringe (JIRA)

Parse error if a choice is between an element and a sequence which also contains the element -------------------------------------------------------------------------------------------- Key: JBXB-182 URL: https://jira.jboss.org/jira/browse/JBXB-182 Project: JBoss XML Binding (JBossXB) Issue Type: Bug Environment: JBoss AS5, JBossXB 2.0.0.GA Reporter: Matt Wringe JBossXB fails to parse an xml file if the xsd contains a choice between an element and a sequence which also contains the element. For example, in the follow the choice should allow the option between specifying A and then B, or just B <choice> <sequence> <element name="A"/> <element name="B"/> </sequence> <element name="B"/> </choice> But, if an xml file used contains just B, an exception will be thrown saying that B is in the wrong order for the sequence. The expected result would be that it should work since just having B is valid. Part of the actual xsd file (http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd) in question: <choice> <sequence> <element name="resource-bundle" type="portlet:resource-bundleType"/> <element name="portlet-info" type="portlet:portlet-infoType" minOccurs="0"/> </sequence> <element name="portlet-info" type="portlet:portlet-infoType"/> </choice> Part of the stacktrace thrown when a portlet-info element is declared in an portlet.xml file without resource-bundle: Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Requested element {http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd}portlet-info is not allowed in this position in the sequence. The next element should be {http://java.sun.com/xml/ns/portlet/portlet-app_1_0.xsd}resource-bundle at org.jboss.xb.binding.sunday.unmarshalling.SequenceBinding$1.startElement(SequenceBinding.java:226) at org.jboss.xb.binding.sunday.unmarshalling.ChoiceBinding$1.startElement(ChoiceBinding.java:230) at org.jboss.xb.binding.sunday.unmarshalling.SequenceBinding$1.startElement(SequenceBinding.java:254) at org.jboss.xb.binding.sunday.unmarshalling.ModelGroupBinding$Cursor.startElement(ModelGroupBinding.java:185) at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:451) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401) 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) Note: when using other tools, the xsd file validates as a proper xsd file, and the xml file used properly validates against the specified xsd. More information (stacktraces, actual files used, etc...) is available upon requested. -- 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, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1747) Make the individual tutorials runnable through Maven

by jaikiran pai (JIRA)

Make the individual tutorials runnable through Maven ---------------------------------------------------- Key: EJBTHREE-1747 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1747 Project: EJB 3.0 Issue Type: Task Components: docs Affects Versions: 1.1.1 Environment: JBoss-AS 5.0.x Reporter: jaikiran pai Assignee: jaikiran pai The EJB3 tutorials currently can be built and run through Ant and Maven. However Maven support is not that great and currently works as follows: 1) An aggregator (jboss-ejb3-tutorial-parent) first triggers the AS to start (through a "init" module) 2) All the tutorials are then run one after other 3) The aggregator then finally uses a "shutdown" module to stop the server. This doesn't allow a single tutorial to be run through Maven, because the AS is started outside the tutorial. To fix this, maven profile(s) need to be created. Ex: A "RunAllTutorial" profile which does the same steps as above and a "RunOneTutorial" which is responsible for running the single tutorial (with the additional steps of starting/stopping the AS). -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1746) EJB3 tutorials not working against JBossAS-5.0.1 GA

by jaikiran pai (JIRA)

EJB3 tutorials not working against JBossAS-5.0.1 GA --------------------------------------------------- Key: EJBTHREE-1746 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1746 Project: EJB 3.0 Issue Type: Bug Components: docs Affects Versions: 1.1.1 Environment: JBossAS-5.0.1 GA Reporter: jaikiran pai Assignee: jaikiran pai Priority: Critical Some of the EJB3 tutorials (which mainly involve the jboss.security related stuff) work on JBossAS-5.0 GA but not on JBossAS-5.0.1 GA. The issue is because AS5.0.1 is not compatible with AS5.0 as tracked through this thread on jboss-dev mailing list http://www.nabble.com/JBoss-5.0-GA-and-JBoss-5.0.1-GA-incompatible--td219... -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-806) JBM is assuming it can look up system properties on the client side

by Tim Fox (JIRA)

JBM is assuming it can look up system properties on the client side ------------------------------------------------------------------- Key: JBMESSAGING-806 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-806 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.SP3, 1.2.0.Beta1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Beta2, 1.0.1.SP4 JBM (JMSRemotingConnection) does several System.getProperties() to get the override bind address and port. However in a security restricted environment e.g. jnlp or applet this may not work. This causes an exception to be thrown and the connection is not created. Need to catch the exception and set to null. -- 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, 10 months

5
15
0 / 0

[JBoss JIRA] Resolved: (GPD-241) jBPM plugin doesn't support default replyTo in ESB Node configuration

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/GPD-241?page=com.atlassian.jira.plugin... ] Koen Aers resolved GPD-241. --------------------------- Resolution: Done > jBPM plugin doesn't support default replyTo in ESB Node configuration > --------------------------------------------------------------------- > > Key: GPD-241 > URL: https://jira.jboss.org/jira/browse/GPD-241 > Project: JBoss jBPM GPD > Issue Type: Feature Request > Components: jpdl > Affects Versions: jBPM jPDL Designer 3.1.5 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.1.7 > > > The jBPM editor in JBoss IDE doesn't support configuration of storing original replyTo message, described here : https://jira.jboss.org/jira/browse/SOA-295 (SOA-295). It's very usefull feature, i'd be glad to have this done without editing xml by hand. -- 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, 10 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-jira March 2009