[JBoss JIRA] Resolved: (JBAS-7050) "ClassNotFoundException: org.jboss.resource.deployers.management.DsDataSourceTemplateInfo" on remote calls to ManagementView.getTemplate()
by Scott M Stark (JIRA)
[ https://jira.jboss.org/jira/browse/JBAS-7050?page=com.atlassian.jira.plug... ]
Scott M Stark resolved JBAS-7050.
---------------------------------
Resolution: Done
The template info server classes are now using writeReplace to only return BasicDeploymentTemplateInfo class.
> "ClassNotFoundException: org.jboss.resource.deployers.management.DsDataSourceTemplateInfo" on remote calls to ManagementView.getTemplate()
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBAS-7050
> URL: https://jira.jboss.org/jira/browse/JBAS-7050
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ProfileService
> Affects Versions: JBossAS-5.1.0.GA
> Reporter: Lukas Krejci
> Assignee: Scott M Stark
> Priority: Blocker
> Fix For: JBossAS-5.2.0.Beta1
>
>
> When trying to create a datasource in AS5 using JON, the following exception occurs:
> java.lang.ClassNotFoundException: org.jboss.resource.deployers.management.DsDataSourceTemplateInfo
> at org.jboss.remoting.serialization.ClassLoaderUtility.loadClass(ClassLoaderUtility.java:103)
> at org.jboss.remoting.loading.RemotingClassLoader.loadClass(RemotingClassLoader.java:86)
> at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:247)
> at org.jboss.remoting.loading.ObjectInputStreamWithClassLoader.resolveClass(ObjectInputStreamWithClassLoader.java:179)
> at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1575)
> at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1496)
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1732)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
> at org.jboss.aop.joinpoint.InvocationResponse.readExternal(InvocationResponse.java:119)
> at java.io.ObjectInputStream.readExternalData(ObjectInputStream.java:1792)
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1751)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
> at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1947)
> at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1871)
> at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
> at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
> at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
> at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObjectVersion2_2(JavaSerializationManager.java:238)
> at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.receiveObject(JavaSerializationManager.java:138)
> at org.jboss.remoting.marshal.serializable.SerializableUnMarshaller.read(SerializableUnMarshaller.java:123)
> at org.jboss.invocation.unified.marshall.InvocationUnMarshaller.read(InvocationUnMarshaller.java:59)
> at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedRead(MicroSocketClientInvoker.java:1220)
> at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:850)
> at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:165)
> at org.jboss.remoting.Client.invoke(Client.java:1724)
> at org.jboss.remoting.Client.invoke(Client.java:629)
> at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
> at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
> at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
> at org.jboss.aop.generatedproxies.AOPProxy$1.getTemplate(AOPProxy$1.java)
> at org.rhq.plugins.jbossas5.ApplicationServerComponent.createConfigurationBasedResource(ApplicationServerComponent.java:415)
> at org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:295)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:526)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
> at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
> at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
> at org.jboss.aop.generatedproxies.AOPProxy$1.getTemplate(AOPProxy$1.java)
> at org.rhq.plugins.jbossas5.ApplicationServerComponent.createConfigurationBasedResource(ApplicationServerComponent.java:415)
> at org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:295)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:526)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:619)
> I was only able to find this class in jboss-embedded-all maven module.
--
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, 6 months
[JBoss JIRA] Created: (JBBOOT-86) Reduce logging noise by making file/urls' relative
by Max Rydahl Andersen (JIRA)
Reduce logging noise by making file/urls' relative
--------------------------------------------------
Key: JBBOOT-86
URL: https://jira.jboss.org/jira/browse/JBBOOT-86
Project: JBoss Bootstrap
Issue Type: Feature Request
Reporter: Max Rydahl Andersen
Assignee: Andrew Lee Rubinger
> In some effort to address frequent user feedback that our logging is difficult to weed through, I'm considering changing the server info dump to something like:
>
> 12:02:08,263 INFO [JBossASServerImpl] Server Configuration:
>
> Bootstrap URL: file:/home/alrubinger/business/jboss/wc/jbossas/branches/Branch_5_x_BootstrapLegacyRemoval/build/output/jboss-5.1.0.GA/server/default/conf/bootstrap.xml
> JBOSS_HOME URL: file:/home/alrubinger/business/jboss/wc/jbossas/branches/Branch_5_x_BootstrapLegacyRemoval/build/output/jboss-5.1.0.GA/
> Common Base URL: file:/home/alrubinger/business/jboss/wc/jbossas/branches/Branch_5_x_BootstrapLegacyRemoval/build/output/jboss-5.1.0.GA/common/
> Common Library URL: file:/home/alrubinger/business/jboss/wc/jbossas/branches/Branch_5_x_BootstrapLegacyRemoval/build/output/jboss-5.1.0.GA/common/lib/
> Server Name: default
> Server Base URL: file:/home/alrubinger/business/jboss/wc/jbossas/branches/Branch_5_x_BootstrapLegacyRemoval/build/output/jboss-5.1.0.GA/server/
> Server Library URL: file:/home/alrubinger/business/jboss/wc/jbossas/branches/Branch_5_x_BootstrapLegacyRemoval/build/output/jboss-5.1.0.GA/server/default/lib/
> Server Config URL: file:/home/alrubinger/business/jboss/wc/jbossas/branches/Branch_5_x_BootstrapLegacyRemoval/build/output/jboss-5.1.0.GA/server/default/conf/
> Server Home URL: file:/home/alrubinger/business/jboss/wc/jbossas/branches/Branch_5_x_BootstrapLegacyRemoval/build/output/jboss-5.1.0.GA/server/default/
> Server Data URL: file:/home/alrubinger/business/jboss/wc/jbossas/branches/Branch_5_x_BootstrapLegacyRemoval/build/output/jboss-5.1.0.GA/server/default/data
> Server Log URL: file:/home/alrubinger/business/jboss/wc/jbossas/branches/Branch_5_x_BootstrapLegacyRemoval/build/output/jboss-5.1.0.GA/server/default/log/
> Server Temp URL: file:/home/alrubinger/business/jboss/wc/jbossas/branches/Branch_5_x_BootstrapLegacyRemoval/build/output/jboss-5.1.0.GA/server/default/tmp
>
> Do we like the additional whitespace to separate this stuff out from the rest? We've done a similar thing in EJB3 where we print out the target JNDI names.
>
> Ultimately we should probably look at each INFO statement on AS boot and decide if it should really be there or not.
Any chance you could print these as *relative* locations to i.e. current working directory or HOME_URL instead of full canonical names which is very redundant and hard to read ?
i.e., using JBOSS_HOME_URL as base: file:/home/alrubinger/business/jboss/wc/jbossas/branches/Branch_5_x_BootstrapLegacyRemoval/build/output/jboss-5.1.0.GA/
12:02:08,263 INFO [JBossASServerImpl] Server Configuration:
JBOSS_HOME URL: file:/home/alrubinger/business/jboss/wc/jbossas/branches/Branch_5_x_BootstrapLegacyRemoval/build/output/jboss-5.1.0.GA/
Bootstrap: server/default/conf/bootstrap.xml
Common Base: common/
Common Library: common/lib/
Server Name: default
Server Base: server/
Server Library: server/default/lib/
Server Config: default/conf/
Server Home: server/default/
Server Data: server/default/data
Server Log: default/log/
Server Temp: default/tmp
Note, that I removed the redundant URL for those that aren't necessarily full url's when printed like 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, 6 months
[JBoss JIRA] Created: (JBREM-1121) Client SocketFactory should be configurable by InvokerLocator
by Ron Sigal (JIRA)
Client SocketFactory should be configurable by InvokerLocator
-------------------------------------------------------------
Key: JBREM-1121
URL: https://jira.jboss.org/jira/browse/JBREM-1121
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.2.2.SP11, 2.5.1 (Flounder)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.2.2.SP12, 2.5.2 (Flounder)
org.jboss.remoting.RemoteClientInvoker, which creates the client invoker's SocketFactory, uses only the parameters passed in the configuration map (except for looking in the InvokerLocator for org.jboss.remoting.SOCKET_FACTORY_CLASS_NAME (actual value "socketFactoryClassName"), which was introduced in JBREM-1014 "Support injection of socket factory class name into AbstractInvoker"). There should be a configurable option to use all parameters from the InvokerLocator.
--
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, 6 months
[JBoss JIRA] Created: (JBXB-211) @XmlType.propOrder required with no schema sequence
by Thomas Diesler (JIRA)
@XmlType.propOrder required with no schema sequence
---------------------------------------------------
Key: JBXB-211
URL: https://jira.jboss.org/jira/browse/JBXB-211
Project: JBoss XML Binding (JBossXB)
Issue Type: Bug
Affects Versions: JBossXB-2.0.1.GA
Reporter: Thomas Diesler
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Property order is not specified for type or
g.jboss.osgi.blueprint.parser.xb.TRegistrationListener bound to a sequence. Property order can be sp
ecified using @XmlType.propOrder or @XmlAccessorOrder. List of properties: ref refFIXME bean any unr
egistrationMethod registrationMethod reference
at org.jboss.xb.builder.JBossXBNoSchemaBuilder.assertPropOrderNotRequired(JBossXBNoSchemaBuilder.ja
va:1278)
at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateType(JBossXBNoSchemaBuilder.java:1071)
at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:779)
at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:767)
Please see forum post
--
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, 6 months
[JBoss JIRA] Created: (HIBERNATE-119) one-to-one with property-ref always non-lazy
by Sandeep Vaid (JIRA)
one-to-one with property-ref always non-lazy
--------------------------------------------
Key: HIBERNATE-119
URL: https://jira.jboss.org/jira/browse/HIBERNATE-119
Project: Hibernate
Issue Type: Feature Request
Reporter: Sandeep Vaid
Assignee: Steve Ebersole
I have one-to-one relationship between Product and ProductBasic.
PRODUCT ------> PRODUCTID(PK)
PRODUCT ------> PID, CODE, STARTTIME (Composite-key) and PID is FK
In product.hbm.xml
<one-to-one name="productBasic" cascade="save-update" property-ref="activeProduct" constrained="true">
<formula>PRODUCTID</formula>
</one-to-one>
ProductBasic.hbm.xml as :
<properties name="activeProduct">
<many-to-one name="product" class="Product" insert="false" update="false" lazy="proxy" />
</properties>
When i am using property-ref, and try to load all Products, it fetches ProductBasic also as :
select * from PRODUCT; //suppose it return 2 records with productId as 100 and 101 respectively.
select * from PRODUCTBASIC where productId='100'
select * from PRODUCTBASIC where productId='101'
How can i fetch ProductBasic in a Non-Lazy manner in this case.
I found few information regarding my problem as :
https://forum.hibernate.org/viewtopic.php?f=25&t=969713
NOTE: Without property-ref, we can load one-to-one lazily (by sepcifying constrained="true")....... outer-join="true"
It's shows the message as :
DEBUG - total objects hydrated: 1
DEBUG - resolving associations for [model.Product#1]
DEBUG - loading entity: [model.ProductName#1]
DEBUG - creating new proxy for entity
DEBUG - done materializing entity [model.Product#1]
Now the thing now remaining in this is to load one-to-one lazily with property-ref.
EntityType.resolve() line 382
if ( isReferenceToPrimaryKey() ) {
return resolveIdentifier( (Serializable) value, session );
}
else {
return loadByUniqueKey( getAssociatedEntityName(), uniqueKeyPropertyName, value, session );
}
and in loadByUniqueKey() method, there is a comment :
//TODO: implement caching?! proxies?!
I think this is the culprit
--
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, 6 months
[JBoss JIRA] Created: (JBAS-7075) Communication from JSP (scriptlet) to managed bean is not working
by anil kumar (JIRA)
Communication from JSP (scriptlet) to managed bean is not working
-----------------------------------------------------------------
Key: JBAS-7075
URL: https://jira.jboss.org/jira/browse/JBAS-7075
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Integration
Affects Versions: JBossAS-5.1.0.GA
Environment: windows
Reporter: anil kumar
Priority: Critical
I am trying to set few parameters from JSP scriptlet. Here is the snippet.HeaderBean is a managed bean with dispalyTitle as setters and getters.
here its printing auditlog,auditlog,auditlog with command link instead of dashboard,transaction,auditlog command link.
HeaderBean scope is request.
Please suggest me on this.
<h:form>
<%
ArrayList<String> names = new ArrayList<String>();
names.add("dashboard");
names.add("transaction");
names.add("auditlog");
%>
<%
HttpServletRequest facesRequest = (HttpServletRequest)FacesContext.getCurrentInstance().getExternalContext().getRequest();
for (String name: names){
HeaderBean header = new HeaderBean();
header.setDispalyTitle(name);
facesRequest.setAttribute("HeaderBean", header);
%>
<h:commandLink title="#{HeaderBean.dispalyTitle}" value= "#{HeaderBean.dispalyTitle}"> </h:commandLink> <br>
<%}%>
--
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, 6 months
[JBoss JIRA] Created: (HIBERNATE-118) one-to-one with composite-id must have common CompositeId class
by Sandeep Vaid (JIRA)
one-to-one with composite-id must have common CompositeId class
---------------------------------------------------------------
Key: HIBERNATE-118
URL: https://jira.jboss.org/jira/browse/HIBERNATE-118
Project: Hibernate
Issue Type: Bug
Reporter: Sandeep Vaid
Assignee: Steve Ebersole
One query before asking this question:
I can see 2 different sites for Hibernate Bug Tracking:
1) Hibernate JIRA - http://opensource.atlassian.com/projects/hibernate/secure/Dashboard.jspa
2) JBOSS JIRA- This site
Which is the official site? Out of these 2 sites on which i should post the bugs etc.. ?
I have one-to-one relationship between Product and ProductBasic..
I have Product (PId, PDesc) as composite-key
I have ProductBasic (ProductId, ProductDesc) as composite-Key
Case 1: I created one Composite class which is common for both Product and ProductBasic..
class CompProductRelated{
string pid;
string pdesc;
}
then try to fetch Product.. It worked !!!
Case 2: If i create seperate Composite class for Product & ProductBasic viz. CompProduct and CompProductBasic respectively as :
class CompProduct{
string productId;
string productDesc;
}
and not if i define the mapping accordingly as:
In Product.hbm.xml
<composite-id name="compProduct" class="CompProduct">
<key-property name="pid" type="string" column="PRODUCTID" length="10"></key-property>
<key-property name="desc" type="string" column="DESC" length="10"></key-property>
</composite-id>
In ProductBasic.hbm.xml
<composite-id name="compProductBasic" class="CompProductBasic">
<key-property name="productId" column="PRODUCTID" type="string" length="10"/>
<key-property name="productDesc" column="DESC1" type="string" length="10"/>
</composite-id>
Now while fetching Product (and internally it will fetch ProductBasic), it gives the following exception:
org.hibernate.TypeMismatchException: Provided id of the wrong type. Expected: class model.CompProductBasic, got class model.CompProduct
So the only approach for one-to-one with composite-id is to have a common compositeId class..
The link http://docs.jboss.org/hibernate/stable/core/reference/en/html_single/#map...
recommends 3 solutions (3rd being to have a common compositeId class) but as per my understanding 1st and 2nd approach will give exception for one-to-one with composite-id ...
I think this hibenate restriction (of having common CompositeId class for one-to-one relationship) is not good as it puts a constraint on how domain model (java) should be which could not be possible everytime in legacy applications..
NOTE: This is the similar exception if i don't use a seperate class for CompositeId..
Hibernate docs have a statement about this situation as :
Unfortunately, this approach to composite identifiers means that a persistent object is its own identifier. There is no convenient "handle" other than the object itself. You must instantiate an instance of the persistent class itself and populate its identifier properties before you can load() the persistent state associated with a composite key. We call this approach an embedded composite identifier, and discourage it for serious applications.
A second approach is what we call a mapped composite identifier, where the identifier properties named inside the <composite-id> element are duplicated on both the persistent class and a separate identifier class.
<composite-id class="MedicareId" mapped="true">
<key-property name="medicareNumber"/>
<key-property name="dependent"/>
</composite-id>
Useful Links : https://forum.hibernate.org/viewtopic.php?f=1&t=993886
--
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, 6 months
[JBoss JIRA] Created: (HIBERNATE-117) Part of Composite-Id is foreign Key:How specify in Mapping?
by Sandeep Vaid (JIRA)
Part of Composite-Id is foreign Key:How specify in Mapping?
-----------------------------------------------------------
Key: HIBERNATE-117
URL: https://jira.jboss.org/jira/browse/HIBERNATE-117
Project: Hibernate
Issue Type: Feature Request
Reporter: Sandeep Vaid
Assignee: Steve Ebersole
I have 2 classes viz. Product and ProductBasic having one-to-one relationship
class Product{
String productId;
ProductBasic productBasic;
}
class ProductBasic{
String productId;
String useCode;
TimeStamp startTime;
Product product;
}
Product is mapped to a table PRODUCT which has PRODUCTID as PK.
ProductBasic is mapped to a table PRODUCTBASIC which has PRODUCTID,USECODE and STARTTTIME as composite key.
Also PRODUCTID (of PRODUCTBASIC table) is the foreign key referencing PRODUCT table...
How can i define my one-to-one mapping considering ProductBasic.productId should get its value from Product.productId ?
<composite-id>
<key-property name="productId" column="PRODUCTID" type="string" length="10" />
<key-property name="useCode" column="USECODE" type="string" length="10" />
<key-property name="startTime" column="STARTTIME" />
<composite-id>
In this only productId is the foreign key..
I am aware that i can use a <generator> tag (with class="foreign") inside <composite-id> but i guess it will generate the
value for entire composite-id and not just a field of it.
--
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, 6 months