[JBoss JIRA] Created: (HIBERNATE-43) SQL native Request who respond only the first letter
by Alexandre PETRILLO (JIRA)
SQL native Request who respond only the first letter
----------------------------------------------------
Key: HIBERNATE-43
URL: http://jira.jboss.com/jira/browse/HIBERNATE-43
Project: Hibernate
Issue Type: Bug
Environment: Jboss 4.0.4 G.A. patch 1
Reporter: Alexandre PETRILLO
Assigned To: Steve Ebersole
I need to do some sql native query (to a data base Oracle 9i) from an EJB session Bean.
I use Jboss in version 4.0.4 G.A. patch 1
My simple code :
public List doNativeQueryMultiple(String sqlQuery) {
List list = manager.createNativeQuery(sqlQuery).getResultList();
return list;
}
This is some exemple for understand the probleme.
SELECT 'OUI' val FROM dual union SELECT 'NON' FROM dual Order BY 1 asc
Response is : O,N
SELECT 'TOTO' val FROM dual union SELECT 'NON' FROM dual Order BY 1 asc
Response is : TOTO,NON
SELECT 'TOT' val FROM dual union SELECT 'NON' FROM dual Order BY 1 asc
Response is : T,N
SELECT 'OUI' val FROM dual union SELECT 'abc' FROM dual Order BY 1 asc
Response is : O,a
SELECT 'OUI' val FROM dual union SELECT 'abcd' FROM dual Order BY 1 asc
Response is : OUI,abcd
SELECT 'OUI' val FROM dual union SELECT 'NON' FROM dual union SELECT 'TOT' FROM dual Order BY 1 asc
Response is : O,N,T
SELECT 'OUI' val FROM dual union SELECT 'NON' FROM dual union SELECT 'TOTO' FROM dual Order BY 1 asc
Response is : OUI,NON,TOTO
When the response of the request is correct, the return class type is java.lang.String
And when is incorrect , the return class type is java.lang.Charactere, and the response contain the first letter.
The bug is when the size of all of the selected string have the same length.
The test done by Jboss for determine the class return type maybe is wrong.
--
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
15 years, 2 months
[JBoss JIRA] Created: (JBOSGI-5) OSGi Deployers
by Adrian Brock (JIRA)
OSGi Deployers
--------------
Key: JBOSGI-5
URL: http://jira.jboss.com/jira/browse/JBOSGI-5
Project: JBoss OSGi
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Adrian Brock
Assigned To: Ales Justin
Holder task for OSGi aspectized deployers.
The deployers will include at least:
1) Structure deployer to recognise OSGi bundles and setup "subdeployments" according to the jars
specified in the osgi classpath.
2) OSGi parser deployer that turns the manifest entries into an OSGIMetaData model
3) DeploymentResolver that sets up the dependencies for deployments
4) OSGi classloader deployer - replacement for UCL classloader with OSGi classloading semantics
5) OSGi real deployer - creates a bean that provides an OSGi facade (the lifecycle)
--
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
15 years, 2 months
[JBoss JIRA] Created: (JGRP-430) Support accessing multiple GossipRouters in TUNNEL
by Bela Ban (JIRA)
Support accessing multiple GossipRouters in TUNNEL
--------------------------------------------------
Key: JGRP-430
URL: http://jira.jboss.com/jira/browse/JGRP-430
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.5
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.6
Multiple GossipRouters can only be used for lookups, not for routing... However, since all traffic to the GR goes out via TUNNEL (as JGroups transport), and TUNNEL uses a RouterStub to send a message to the GR, we could do the following:
* the RouterStub is currently configured with the address of *one* GR
* a Stub.send() succeeds in connecting to the GR and sending the
message, or goes into a state where it tries to reconnect *forever*
* I could simply change that to configure the RouterStub with
multiple GRs:
o for send(), we iterate through the GRs until send() returns
true
EFFECT: a GossipRouter is not a single point of failure any longer
--
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
15 years, 3 months
[JBoss JIRA] Created: (JBJMX-100) Class loader doesn't contain classes from MBean jar file when the MBean is redeployed.
by Doug Palmer (JIRA)
Class loader doesn't contain classes from MBean jar file when the MBean is redeployed.
--------------------------------------------------------------------------------------
Key: JBJMX-100
URL: http://jira.jboss.com/jira/browse/JBJMX-100
Project: JBoss JMX
Issue Type: Bug
Affects Versions: JBossAS-4.0.0
Environment: Mac OSX and Windows XP
Reporter: Doug Palmer
This is a simplified version of a Deployer MBean that I have been writing. The MBean uses some jaxb generated classes. When the MBean is first deployed it's create method functions perfectly. However, if the MBean is redeployed then calling create fails because the class loader can't find the package "decs2.process_definition".
To replicate the problem execute the ant target named "deploy-all"; then run JBoss; then execute the ant target named "deploy".
If the package "decs2.process_definition" is is placed in a seperate jar file and that jar file is placed in the server/lib directory then the MBean redeploys successfully.
--
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
15 years, 3 months