[JBoss JIRA] (HIBERNATE-141) JBAS011910 Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=org.hibernate.criterion}
by Steve Ebersole (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-141?page=com.atlassian.jira.plu... ]
Steve Ebersole updated HIBERNATE-141:
-------------------------------------
Assignee: (was: Steve Ebersole)
> JBAS011910 Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=org.hibernate.criterion}
> ---------------------------------------------------------------------------------------------------------------
>
> Key: HIBERNATE-141
> URL: https://issues.jboss.org/browse/HIBERNATE-141
> Project: Hibernate Integration
> Issue Type: Enhancement
> Reporter: Darryl Miles
>
> EAP 6.1 with upgraded org.hibernate:main jars to 4.2.0.Final (to fix classloading issue HHH-8015 which I did observe).
> JPA has META-INF/jboss-deployment-structure.xml which has entry (amongst other things):
> <module name="org.hibernate" />
> <module name="org.hibernate.validator" />
> JPA has OSGi meta-data including OSGi-JPA:
> Meta-Persistence: META-INF/persistence.xml
> 23:00:16,860 INFO [org.jboss.osgi.framework] (MSC service thread 1-15) JBOSGI011005: Bundle uninstalled: com.domain.jpa:0.0.1.SNAPSHOT
> 23:00:16,862 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment com.domain.jpa-0.0.1-SNAPSHOT.jar (runtime-name: com.domain.jpa-0.0.1-SNAPSHOT.jar) in 4ms
> 23:00:16,863 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "com.domain.jpa-0.0.1-SNAPSHOT.jar" (runtime-name: "com.domain.jpa-0.0.1-SNAPSHOT.jar")
> 23:00:16,876 INFO [org.jboss.as.jpa] (MSC service thread 1-15) JBAS011401: Read persistence.xml for com.domain.jpa
> 23:00:16,880 INFO [org.jboss.osgi.framework] (MSC service thread 1-9) JBOSGI011001: Bundle installed: com.domain.jpa:0.0.1.SNAPSHOT
> 23:00:16,884 WARN [org.jboss.as.osgi] (MSC service thread 1-14) JBAS011910: Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=org.hibernate.criterion},[com.domain.jpa:0.0.1.SNAPSHOT]]]
> 23:00:16,884 INFO [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015970: Defer FIRST_MODULE_USE for com.domain.jpa-0.0.1-SNAPSHOT.jar making it NEVER
> 23:00:16,908 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "com.domain.jpa-0.0.1-SNAPSHOT.jar" with deployment "com.domain.jpa-0.0.1-SNAPSHOT.jar"
> I would expect the OSGi subsystem to have been able to find the import package org.hibernate.criterion
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (HIBERNATE-141) JBAS011910 Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=org.hibernate.criterion}
by Steve Ebersole (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-141?page=com.atlassian.jira.plu... ]
Steve Ebersole commented on HIBERNATE-141:
------------------------------------------
Darryl, I am going to move this over to the OSGi project since the problem really seems to be there, not in the Hibernate/WildFly integration (which is what this HIBERNATE Jira project is for).
> JBAS011910 Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=org.hibernate.criterion}
> ---------------------------------------------------------------------------------------------------------------
>
> Key: HIBERNATE-141
> URL: https://issues.jboss.org/browse/HIBERNATE-141
> Project: Hibernate Integration
> Issue Type: Enhancement
> Reporter: Darryl Miles
>
> EAP 6.1 with upgraded org.hibernate:main jars to 4.2.0.Final (to fix classloading issue HHH-8015 which I did observe).
> JPA has META-INF/jboss-deployment-structure.xml which has entry (amongst other things):
> <module name="org.hibernate" />
> <module name="org.hibernate.validator" />
> JPA has OSGi meta-data including OSGi-JPA:
> Meta-Persistence: META-INF/persistence.xml
> 23:00:16,860 INFO [org.jboss.osgi.framework] (MSC service thread 1-15) JBOSGI011005: Bundle uninstalled: com.domain.jpa:0.0.1.SNAPSHOT
> 23:00:16,862 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment com.domain.jpa-0.0.1-SNAPSHOT.jar (runtime-name: com.domain.jpa-0.0.1-SNAPSHOT.jar) in 4ms
> 23:00:16,863 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "com.domain.jpa-0.0.1-SNAPSHOT.jar" (runtime-name: "com.domain.jpa-0.0.1-SNAPSHOT.jar")
> 23:00:16,876 INFO [org.jboss.as.jpa] (MSC service thread 1-15) JBAS011401: Read persistence.xml for com.domain.jpa
> 23:00:16,880 INFO [org.jboss.osgi.framework] (MSC service thread 1-9) JBOSGI011001: Bundle installed: com.domain.jpa:0.0.1.SNAPSHOT
> 23:00:16,884 WARN [org.jboss.as.osgi] (MSC service thread 1-14) JBAS011910: Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=org.hibernate.criterion},[com.domain.jpa:0.0.1.SNAPSHOT]]]
> 23:00:16,884 INFO [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015970: Defer FIRST_MODULE_USE for com.domain.jpa-0.0.1-SNAPSHOT.jar making it NEVER
> 23:00:16,908 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018565: Replaced deployment "com.domain.jpa-0.0.1-SNAPSHOT.jar" with deployment "com.domain.jpa-0.0.1-SNAPSHOT.jar"
> I would expect the OSGi subsystem to have been able to find the import package org.hibernate.criterion
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (HIBERNATE-133) Function to detach Hibernate managed object.
by Steve Ebersole (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-133?page=com.atlassian.jira.plu... ]
Steve Ebersole closed HIBERNATE-133.
------------------------------------
Resolution: Rejected
1) You are using the wrong Jira as specified in the description for this project.
2) Plenty of ways to achieve this (OSiV, DTO, etc)
> Function to detach Hibernate managed object.
> --------------------------------------------
>
> Key: HIBERNATE-133
> URL: https://issues.jboss.org/browse/HIBERNATE-133
> Project: Hibernate Integration
> Issue Type: Feature Request
> Environment: Hibernate core.
> Reporter: jack luo
> Assignee: Steve Ebersole
> Labels: LazyInitializationException
>
> Currently, after retrieving data from database by hibernate like:
> User user = session.get(User.class, id);
> Then user object will become a hibernated managed object (po), if try to invoke any "lazy" property which haven't been initialized then it will throw an famous "LazyInitializationException". But so often, in web service or other scenarios, we need to serialize the object returned by Hibernate query, serializer doesn't know which properties are "lazy" field and haven't been initialized, then in serializing, it will throw an ""LazyInitializationException" exception which will stop the whole thing working. I found Session.evict(Object proxy) and Session.clear() seems might do the work that detaching PO from Hibernate, but it doesn't. I still got the error. After spent days searching in the internet, I found out there isn't any easy way to convert an PO to a POJO (detaching PO from Hibernate thoroughly), actually many people have implemented so many solutions like removing all the proxies from PO or copy PO to an POJO (DTO some people call it), any solution comes with cost of the system apparently. Well, if Hibernate can provide a simple function Hibernate.detach(Object obj) which will return an pure POJO then it will make our life so much easier. Check this link out, you see how many people have been struggling with this issue since 2008?
> http://www.mojavelinux.com/blog/archives/2006/06/hibernate_get_out_of_my_...
> My first try on Hibernate was back to 2007 and I found this issue, ending up copying properties of PO to a POJO to avoid "LazyInitializationException" exception. I absolute got the idea of lazy loading but DAO layer will pass the object to Business/View layer, I don't think they're responsible to check if every property's initialized by Hibernate before using it. It ok that un-initialized properties are null but throwing an exception is unacceptable. Requirement is quite straight forward, just want a pure POJO.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (HIBERNATE-142) @JoinColumn annotation doesn't fully support column names requiring double-quotes
by Steve Ebersole (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-142?page=com.atlassian.jira.plu... ]
Steve Ebersole commented on HIBERNATE-142:
------------------------------------------
This is the Jira project for the integration of Hibernate into JBoss/WildFly. For issues with Hibernate itself, use https://hibernate.atlassian.net/browse/HHH
You can report this issue there, or I'll "move" it when I get time.
> @JoinColumn annotation doesn't fully support column names requiring double-quotes
> ---------------------------------------------------------------------------------
>
> Key: HIBERNATE-142
> URL: https://issues.jboss.org/browse/HIBERNATE-142
> Project: Hibernate Integration
> Issue Type: Bug
> Environment: Hibernate 4.2.4-Final
> Eclipse Juno
> J2EE 3.0 Web app
> Reporter: Paul Spinelli
> Assignee: Steve Ebersole
> Priority: Minor
>
> Due to the way an existing database schema has been configured, my JPA annotations (using Hibernate as my provider) all required that table names/column names be double-quoted:
> (e.g. String ID_COLUMN_NAME = "\"Id\"";)
> This does not pose a problem EXCEPT when using the @JoinColumn annotation (specifically, the 'referencedColumnName' attribute). This DOES NOT work (I get an error that the logical column name cannot be found):
> @JoinColumn(name=ID_COLUMN_NAME, referencedColumnName=ID_COLUMN_NAME)
> However, this DOES work:
> @JoinColumn(name=ID_COLUMN_NAME, referencedColumnName="`Id`")
> It seems that the 'name' attribute supports double-quotes while the 'referencedColumnName' attribute does not. Is there a reason it should not?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (WFLY-1721) Access log support
by Yoshimasa Tanabe (JIRA)
[ https://issues.jboss.org/browse/WFLY-1721?page=com.atlassian.jira.plugin.... ]
Yoshimasa Tanabe commented on WFLY-1721:
----------------------------------------
Hi, Tomaz. I have a question.
I did the following CLI command, but WildFly does not output the access log.
Any idea?
This is CLI history.
{code}
[standalone@localhost:9990 /] /subsystem=undertow/server=default-server/host=default-host/setting=access-log:add
{"outcome" => "success"}
[standalone@localhost:9990 /] /subsystem=undertow/server=default-server/host=default-host/setting=access-log:read-resource
{
"outcome" => "success",
"result" => {
"directory" => "${jboss.server.log.dir}",
"pattern" => "common",
"prefix" => "access_log.",
"rotate" => true,
"worker" => "default"
}
}
{code}
{code:xml|title=standalone.xml}
[...]
<subsystem xmlns="urn:jboss:domain:undertow:1.0">
<buffer-caches>
<buffer-cache name="default" buffer-size="1024" buffers-per-region="1024" max-regions="10"/>
</buffer-caches>
<server name="default-server">
<http-listener name="default" socket-binding="http" max-post-size="10485760"/>
<host name="default-host" alias="localhost">
<location name="/" handler="welcome-content"/>
<access-log/>
</host>
</server>
<servlet-container name="default" default-buffer-cache="default" stack-trace-on-error="local-only">
<jsp-config/>
<persistent-sessions path="persistent-web-sessions" relative-to="jboss.server.data.dir"/>
</servlet-container>
<handlers>
<file name="welcome-content" path="${jboss.home.dir}/welcome-content" directory-listing="true"/>
</handlers>
</subsystem>
[...]
{code}
restarted WildFly, logged WARN log.
{code}
$ ./standalone.sh
[...]
13:47:13,929 WARN [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) service name: service jboss.undertow.server.default-server.host.default-host.access-log
[...]
{code}
and no access-log
{code}
ls $WILDFLY_HOME/standalone/log/
server.log server.log.2013-08-28
{code}
> Access log support
> ------------------
>
> Key: WFLY-1721
> URL: https://issues.jboss.org/browse/WFLY-1721
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Affects Versions: 8.0.0.Alpha3
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 8.0.0.Beta1
>
>
> We need to expose access log configuration trough management.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (HIBERNATE-142) @JoinColumn annotation doesn't fully support column names requiring double-quotes
by Paul Spinelli (JIRA)
Paul Spinelli created HIBERNATE-142:
---------------------------------------
Summary: @JoinColumn annotation doesn't fully support column names requiring double-quotes
Key: HIBERNATE-142
URL: https://issues.jboss.org/browse/HIBERNATE-142
Project: Hibernate Integration
Issue Type: Bug
Environment: Hibernate 4.2.4-Final
Eclipse Juno
J2EE 3.0 Web app
Reporter: Paul Spinelli
Assignee: Steve Ebersole
Priority: Minor
Due to the way an existing database schema has been configured, my JPA annotations (using Hibernate as my provider) all required that table names/column names be double-quoted:
(e.g. String ID_COLUMN_NAME = "\"Id\"";)
This does not pose a problem EXCEPT when using the @JoinColumn annotation (specifically, the 'referencedColumnName' attribute). This DOES NOT work (I get an error that the logical column name cannot be found):
@JoinColumn(name=ID_COLUMN_NAME, referencedColumnName=ID_COLUMN_NAME)
However, this DOES work:
@JoinColumn(name=ID_COLUMN_NAME, referencedColumnName="`Id`")
It seems that the 'name' attribute supports double-quotes while the 'referencedColumnName' attribute does not. Is there a reason it should not?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months
[JBoss JIRA] (WFLY-1385) Override default page-size-bytes in messaging subsystem configuration
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-1385?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-1385:
-----------------------------------------------
Miroslav Novak <mnovak(a)redhat.com> made a comment on [bug 920980|https://bugzilla.redhat.com/show_bug.cgi?id=920980]
This is not fixed in EAP 6.1.1.ER7 (HQ 2.3.5.Final).
@Jeff
Could you check whether your PR got to "eap" branch, please?
> Override default page-size-bytes in messaging subsystem configuration
> ---------------------------------------------------------------------
>
> Key: WFLY-1385
> URL: https://issues.jboss.org/browse/WFLY-1385
> Project: WildFly
> Issue Type: Enhancement
> Components: JMS
> Affects Versions: 8.0.0.Alpha1
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Minor
> Fix For: 8.0.0.Alpha2
>
>
> When HornetQ address-full-policy is switched from BLOCK to PAGE, the following exception is thrown during shutdown.
> {noformat}
> Exception:
> 09:48:05,247 WARN [org.hornetq.core.server] (MSC service thread 1-3) HQ222160: unable to send notification when broadcast group is stopped: java.lang.IllegalStateException: pageSize for address hornetq.notifications >= maxSize. Normally pageSize should be significantly smaller than maxSize, ms: 10485760 ps 10485760
> at org.hornetq.core.paging.impl.PagingStoreImpl.<init>(PagingStoreImpl.java:147) [hornetq-server-2.3.0.CR1-redhat-1.jar:2.3.0.CR1-redhat-1]
> at org.hornetq.core.paging.impl.PagingStoreFactoryNIO.newStore(PagingStoreFactoryNIO.java:98) [hornetq-server-2.3.0.CR1-redhat-1.jar:2.3.0.CR1-redhat-1]
> at org.hornetq.core.paging.impl.PagingManagerImpl.newStore(PagingManagerImpl.java:250) [hornetq-server-2.3.0.CR1-redhat-1.jar:2.3.0.CR1-redhat-1]
> {noformat}
> The standalone-full.xml configuration overrides the default address-setting's max-size-bytes (defaults to -1) to set it at 10 MiB.
> However, if the admin changes the address-full-policy from BLOCK to PAGE, it will conflict with the default value for page-size-bytes which is also 10MiB.
> To make the overridden standalone-full.xml more consistent, we can override page-size-bytes and set it to 2MiB (2097152 bytes). This change has no effect when the address-full-policy remains at BLOCK. When it is changed to PAGE, the resulting configuration will be coherent and there will be no exception thrown
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 8 months