September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-3167) Support Pack200 compression for WAR/EAR files to reduce upload time

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3167?page=all ] Dimitris Andreadis updated JBAS-3167: ------------------------------------- Fix Version/s: (was: JBossAS-4.0.5.GA) Affects Version/s: JBossAS-4.0.2 Final (was: JBossAS-4.0.4.CR2) If someone wants to prototype this fine, but for now there are no cycles for it. > Support Pack200 compression for WAR/EAR files to reduce upload time > ------------------------------------------------------------------- > > Key: JBAS-3167 > URL: http://jira.jboss.com/jira/browse/JBAS-3167 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Deployment services > Affects Versions: JBossAS-4.0.2 Final > Environment: n/a > Reporter: Richard Kennard > Priority: Optional > Original Estimate: 1 week > Remaining Estimate: 1 week > > First, thank you for such an outstanding Application Server: JBoss is truly a magnificent piece of software that is an absolute joy to work with. You guys are a shining testament to the quality of Open Source. > My feature request is to support Sun's new(ish) Pack200 compression format for WARs and EARs. I know precious little about this, other than it is built into the JRE and can pack JARs to a fraction of their original size. I'm not even sure it can be applied 'as is' to WARs and EARs, so perhaps this can be a proprietary JBoss feature? > Anyway, at 20MB+ an EAR takes a good 10-15 minutes to upload to my hosting service using my home broadband connection, so any move to help reduce EAR size would be a boon. > I understand that Pack200 JARs must first be uncompressed into JARs before they can be used, but this should be fairly natural for JBoss (which uncompresses into the tmp folder anyway, I believe). -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-2148) ServerInfo MBean operations return HTML code as java.lang.String

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2148?page=all ] Dimitris Andreadis closed JBAS-2148. ------------------------------------ Fix Version/s: (was: JBossAS-4.0.5.GA) Resolution: Rejected Won't deal with this, unless someone wants to contribute. > ServerInfo MBean operations return HTML code as java.lang.String > ---------------------------------------------------------------- > > Key: JBAS-2148 > URL: http://jira.jboss.com/jira/browse/JBAS-2148 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMX > Affects Versions: JBossAS-4.0.3RC2 > Environment: Fedora Core 4 (x86-32bit) > JDK5.0_04 > unmodified minimal server configuration > System.properties from: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossMBeansInJConsole > Reporter: Mikko Tiihonen > Priority: Minor > > The ServerInfo MBean which can be viewed through the Java 5.0 jconsole returns responses to operations as Strings that contain HTML code. > Instead of <TABLE><TR><TD>... etc the operations should return objects that implement MBean interface or they should be split to smaller operations that can show simple objects. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-460) Make *-service.xml 'validable'

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-460?page=all ] Dimitris Andreadis updated JBAS-460: ------------------------------------ Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.GA) > Make *-service.xml 'validable' > ------------------------------ > > Key: JBAS-460 > URL: http://jira.jboss.com/jira/browse/JBAS-460 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: MicroContainer bus > Affects Versions: JBossAS-4.0.0 Final > Reporter: SourceForge User > Assigned To: Scott M Stark > Priority: Minor > Fix For: JBossAS-4.0.6.CR1 > > > SourceForge Submitter: hanming . > A little while back, I reported this bug: > https://sourceforge.net/tracker/?func=detail&atid=376685&aid=715680&group... > It brought jboss-service_3_2.dtd closer to what David > Jencks has in mind: > "we do not have a dtd for *-service files because > attributes can have xml > element values. AFAIK the only way to cater to this > is with namespaces and > xml schema. We may need to do this for jboss 4. > basically... > <depends optional-attribute-name="foo">[object name or > another mbean > dd]</depends> > and > <depends-list optional-attribute-name="bar"> > <depends-list-element>[o-n or mbean > dd]</depends-list-element> > <depends-list-element>[o-n or mbean > dd]</depends-list-element> > ... > </depends-list>" > jboss-service_3_2.dtd is as good a DTD as in reflecting > what David has in mind but it has a major problem: it > can never be used to validate any *-service.xml file. > This is because XML 1.0 can never have this kind of > construct (represented here as using DTD language, as > opposed to Schema because it cannot be represented > using the latter): > <!ELEMENT depends (#PCDATA | mbean)> > The closest that one can come up with is > <!ELEMENT depends (#PCDATA | mbean)*> > This is how XML 1.0 (may XML 1.1 changes it, I don't > know) deal with a class of SGML problem known as the > 'pernicious mixed content". Search Google for more details. > http://www.w3.org/TR/REC-xml#sec-mixed-content > Summary: > --------------- > I know it's too late to change anything for 3.2 but I > have suggestions for 4.0 > 1. Don't use mixed content, if possible. It's easy to > get it wrong in different level: API, parsing and > writing of DTDs/Schemas. > 2. The easiest local workaround for the element > <depends> is to use Element wrapper pattern, e.g: > <!ELEMENT depends-content (#PCDATA)> > <!ELEMENT depends (depends-content | mbean)> > But that might not be a good overall solution. > 3. Bear in mind that XML Schema in designed to work > with XML 1.0, hence the closest one can use Schema to > constraint <depends> is: > <xs:element name="depends"> > <xs:complexType mixed="true"> > <xs:choice> > <xs:element ref="mbean"/> > </xs:choice> > <xs:attribute name="optional-attribute-name" > type="xs:string"/> > </xs:complexType> > </xs:element> > which is not really what David's original intention is. > Thank you, Han Ming -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1288) Java5 Enum for mbean and configurations

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1288?page=all ] Dimitris Andreadis updated JBAS-1288: ------------------------------------- Fix Version/s: JBossAS-5.0.0.CR1 (was: JBossAS-4.0.5.GA) > Java5 Enum for mbean and configurations > --------------------------------------- > > Key: JBAS-1288 > URL: http://jira.jboss.com/jira/browse/JBAS-1288 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JMX > Affects Versions: JBossAS-4.0.1 Final > Reporter: Michael Kopp > Priority: Minor > Fix For: JBossAS-5.0.0.CR1 > > > Whenever you try to get a PropertyEditor for something but none is there, do the following additional check: > if (type.getSuperclass().getName().equals("java.lang.Enum")) > { > editor = new EnumPropertyEditor(type); > } > where the EnumPropertyEditor is: > public class EnumPropertyEditor extends PropertyEditorSupport implements PropertyEditor > { > private final Class targetType; > public EnumPropertyEditor(Class targetType) > { > this.targetType = targetType; > } > public void setAsText(String text) throws IllegalArgumentException > { > try > { > setValue(targetType.getMethod("valueOf",new Class[]{String.class}).invoke(null,new Object[]{text}); > } catch (IllegalAccessException e) > { > throw new IllegalStateException(e); > } catch (InvocationTargetException e) > { > if (e.getTargetException() instanceof RuntimeException); > throw (RuntimeException)e.getTargetException(); > throw new IllegalStateException(e); > } catch (NoSuchMethodException e) > { > String err = type.getName() + > " does not contain the required method: public static " + > type.getName() + " valueOf(String);"; > throw new IllegalArgumentException(err,e); > } > > } > public String getAsText() > { > > try > { > return targetType.getMethod("name",null).invoke(getValue(),null) > } catch (IllegalAccessException e) > { > throw new IllegalStateException(e); > } catch (InvocationTargetException e) > { > if (e.getTargetException() instanceof RuntimeException); > throw (RuntimeException)e.getTargetException(); > throw new IllegalStateException(e); > } catch (NoSuchMethodException e) > { > String err = type.getName() + > " does not contain the required method: public String name()"; > throw new IllegalStateException(err,e); > } > } > } -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2848) Tool to analyze class loader consistency

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2848?page=all ] Dimitris Andreadis updated JBAS-2848: ------------------------------------- Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.GA) > Tool to analyze class loader consistency > ---------------------------------------- > > Key: JBAS-2848 > URL: http://jira.jboss.com/jira/browse/JBAS-2848 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Other > Reporter: Scott M Stark > Fix For: JBossAS-4.0.6.CR1 > > > Since users don't generally care to think about the typesystem ramifications of the generally conflciting class loader setup allowed in ear deployments as evidenced in the associated forum thread, we need better out of the box smarter than the average deployment archive mess that creates an approriate canonical set of classpaths and class loader configuration. A first step is just a tool that identifies potential problems. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2407) EJB3 integration

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2407?page=all ] Dimitris Andreadis updated JBAS-2407: ------------------------------------- Component/s: EJB3 (was: EJB2) Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.GA) > EJB3 integration > ---------------- > > Key: JBAS-2407 > URL: http://jira.jboss.com/jira/browse/JBAS-2407 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: EJB3 > Affects Versions: JBossAS-4.0.3 SP1, JBossAS-4.0.3 Final > Reporter: Adrian Brock > Fix For: JBossAS-4.0.6.CR1 > > > Need to review EJB3 integartion such that fixes/features don't get lost across EJB2.1/3.0 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2330) Create Hibernate based timer persistence layer

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2330?page=all ] Dimitris Andreadis updated JBAS-2330: ------------------------------------- Fix Version/s: JBossAS-4.0.6.CR1 (was: JBossAS-4.0.5.GA) > Create Hibernate based timer persistence layer > ---------------------------------------------- > > Key: JBAS-2330 > URL: http://jira.jboss.com/jira/browse/JBAS-2330 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Scott M Stark > Fix For: JBossAS-4.0.6.CR1 > > > In the update of the timer service to support persistence independent of the server lifecycle, we should move to a hibernate based pm as opposed to screwing around with sql. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1797) Need to investigate the ejb3 admin/monitoring requirements

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1797?page=all ] Dimitris Andreadis updated JBAS-1797: ------------------------------------- Component/s: EJB3 (was: EJB2) Fix Version/s: JBossAS-5.0.0.CR1 (was: JBossAS-4.0.5.GA) > Need to investigate the ejb3 admin/monitoring requirements > ---------------------------------------------------------- > > Key: JBAS-1797 > URL: http://jira.jboss.com/jira/browse/JBAS-1797 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Management services, EJB3 > Reporter: Scott M Stark > Fix For: JBossAS-5.0.0.CR1 > > > With the integration of the first j2ee5 technology into a jems product, we need to see what the integration issues are from the perspective of the jboss network admin and monitoring integration. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-536) The CallbackServer cannot be contacted for some particular network interface configurations

by Ovidiu Feodorov (JIRA)

The CallbackServer cannot be contacted for some particular network interface configurations ------------------------------------------------------------------------------------------- Key: JBMESSAGING-536 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-536 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.0.1.CR4 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.0.1.CR5 -- 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, 8 months

2
6
0 / 0

[JBoss JIRA] Created: (JBAS-3593) Add a Marshaller to HAPartitionImpl

by Brian Stansberry (JIRA)

Add a Marshaller to HAPartitionImpl ----------------------------------- Key: JBAS-3593 URL: http://jira.jboss.com/jira/browse/JBAS-3593 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.0.5.GA HAPartitionImpl is quasi implementing Marshaller by overriding RpcDispatcher.handle() and doing custom *unmarshalling* with MarshalledValueInputStream. This breaks with JG 2.4, since the default JG marshalling is different and incompatible with the custom unmarshalling. Solution to allow use of 2.4+ in 4.0.5+ is to properly implement Marshaller and do the marshalling as well. This is done in HEAD; need to port to Branch_4_0. The 4.0 marshaller must use the binary format of the old JGroups method to ensure backward interoperability. -- 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, 8 months

1
1
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 September 2006