January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-366) Smooks examples.

by Mark Little (JIRA)

Smooks examples. ---------------- Key: JBESB-366 URL: http://jira.jboss.com/jira/browse/JBESB-366 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Examples, Transformation Service Affects Versions: 4.0 CR2 Reporter: Mark Little Assigned To: Tom Fennelly Fix For: 4.0 EDI, CSV, XML, XSLT, Java serializable, binary, use of a C-based transformer. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBESB-395) More SAR classloader woes :-)

by Tom Fennelly (JIRA)

More SAR classloader woes :-) ----------------------------- Key: JBESB-395 URL: http://jira.jboss.com/jira/browse/JBESB-395 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.0 CR2 Reporter: Tom Fennelly Assigned To: Kevin Conner Fix For: 4.0 I think I've another classloader puzzle for ye to tease out :-) So, we have the 2 sars now. The service gets deployed into jbossesb.sar and the dependencies into the other etc etc. One of the quickstarts (transform_XML2POJO) defines an action that follows a SmooksTransformer action. This 2nd action expected some POJO instances to be attached to the message (attached and populated by Smooks). The The classloading gets screwed because Smooks uses the jbossesb-dependencies.sar classloader (because it's in that .sar) to load the POJO bean class instances that are attached to the message. The action instance extracts the beans from the message and tries to cast them but because that action class is in the jbossesb.sar it uses the jbosses.sar classloader to load the POJO class instances, we get a ClassCastException. -- 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
9
0 / 0

[JBoss JIRA] Created: (JBESB-340) Update getting started guide

by Mark Little (JIRA)

Update getting started guide ---------------------------- Key: JBESB-340 URL: http://jira.jboss.com/jira/browse/JBESB-340 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.0 CR2 Reporter: Mark Little Assigned To: Kurt Stam Fix For: 4.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, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBRULES-637) Replace ListBox in MetaData widget as it can't be tweaked visually or behaviorally

by Michael Neale (JIRA)

Replace ListBox in MetaData widget as it can't be tweaked visually or behaviorally ---------------------------------------------------------------------------------- Key: JBRULES-637 URL: http://jira.jboss.com/jira/browse/JBRULES-637 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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: (JBCACHE-693) TreeCache configuration bombs with InvocationTargetException when JVM locale is set to Turkish.

by Yasar Safkan (JIRA)

TreeCache configuration bombs with InvocationTargetException when JVM locale is set to Turkish. ----------------------------------------------------------------------------------------------- Key: JBCACHE-693 URL: http://jira.jboss.com/jira/browse/JBCACHE-693 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Environment: Tested on Linux, using Resin 3.0.14 with Hibernate 3. Reporter: Yasar Safkan Assigned To: Manik Surtani When the parameters: -Duser.language=tr -Duser.country=TR are passed to the JVM, the AppServer startup bombs when it tires to configure TreeCache using treecache.xml. Seems that it reads the value fine, but thinks the value is invalid for some reason. My best guess is this stems from the way the letters i and I are handled in Turkish. If there is any upper/lowercase conversion code within JBossCache, these letters are handled funny, thus string constants like READ_COMMITED are not recognized. The fix will probably be to use upper/lowercase conversion by specifying a character set in the JBossCache code, and not relying on the JVM defaults. The JVM itself had a similar bug, which prevented encrytion from working under these same conditions. -- 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] Created: (JBESB-125) Installer

by Mark Little (JIRA)

Installer --------- Key: JBESB-125 URL: http://jira.jboss.com/jira/browse/JBESB-125 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Mark Little Priority: Minor Fix For: 4.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, 3 months

2
7
0 / 0

[JBoss JIRA] Reopened: (JBAS-2215) Datasource deployments should only depend on a jrmp invoker when use-java-context is true

by Weston Price (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2215?page=all ] Weston Price reopened JBAS-2215: -------------------------------- Assignee: Weston Price (was: Scott M Stark) The ConnectionFactoryTemplate.xsl includes the correct template for this solution, however, it never seemed to be used. As a result, the JRMPInvoker is always being assigned to the WrapperDataSourceService regardless of the use-java-context setting. > Datasource deployments should only depend on a jrmp invoker when use-java-context is true > ----------------------------------------------------------------------------------------- > > Key: JBAS-2215 > URL: http://jira.jboss.com/jira/browse/JBAS-2215 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.2 Final > Reporter: Scott M Stark > Assigned To: Weston Price > Fix For: JBossAS-5.0.0.Beta1, JBossAS-4.0.3 Final > > > Currently every *-ds.xml deployment has a dependency on a JMXInvoker even if the DataSource is not bound into the global JNDI for use outside of the server. The only time a remote proxy should be created and a dependency on a JMXInvoker created is when the *-ds.xml use-java-context element is false. -- 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: (JBESB-363) Make the trailblazer an easier comparison example

by Mark Little (JIRA)

Make the trailblazer an easier comparison example ------------------------------------------------- Key: JBESB-363 URL: http://jira.jboss.com/jira/browse/JBESB-363 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation, Examples Affects Versions: 4.0 CR2 Reporter: Mark Little Assigned To: Daniel Brum Fix For: 4.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, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-360) Empty docs directory in trailblazer

by Mark Little (JIRA)

Empty docs directory in trailblazer ----------------------------------- Key: JBESB-360 URL: http://jira.jboss.com/jira/browse/JBESB-360 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Examples Affects Versions: 4.0 CR2 Reporter: Mark Little Assigned To: Daniel Brum Priority: Minor Fix For: 4.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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBESB-373) Basic aggregator

by Mark Little (JIRA)

Basic aggregator ---------------- Key: JBESB-373 URL: http://jira.jboss.com/jira/browse/JBESB-373 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Content Based Routing Affects Versions: 4.0 CR2 Reporter: Mark Little Assigned To: Kurt Stam Priority: Optional Fix For: 4.0 Driven by config and Java. -- 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
2
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 January 2007