Re: [hibernate-dev] Hibernate site SEO optimization

[Sanne Grinovero]

Stefania (my girlfriend but also a professional SEO consultant) also
pointed out that we should make sure that indexing engines understand
that the documentation pages are intentionally similar, as you get
penalised for duplicate content.

So as you suggest we need to mark - for each guide - which one is the
"main" reference. I don't know if using a sitemap only is enough, I
was told that we need to add some headers in each webpage to refer it
to its canonical URL, I'll ask if we need both actions.

On 7 December 2015 at 08:12, Vlad Mihalcea  wrote:
> Thanks for pointing that out.
>
> The robots.txt is in place https://docs.jboss.org/robots.txt.
> But I couldn't find the sitemap.xml
>
> According to Google:
> https://support.google.com/webmasters/answer/156184?hl=en
> The sitemap.xml is important if:
>
> - Your site is really large
> - Your site has a large archive of content pages that are isolated or well
> not linked to each other. If you site pages do not naturally reference each
> other, you can list them in a sitemap to ensure that Google does not
> overlook some of your pages.
>
> So we meet both these two requirements.
> Maybe we need to add a sitemap.xml and reference the link to the "stable"
> docs only and the modification date.
>
> Vlad
>
> On Mon, Dec 7, 2015 at 9:46 AM, Gunnar Morling  wrote:
>
>> Hi Vlad,
>>
>> We already have something like this, at
>> http://docs.jboss.org/hibernate/stable/. The latest final version docs
>> are available there. It's only that results from there have not a good
>> search result ranking apparently.
>>
>> --Gunnar
>>
>>
>>
>> 2015-12-04 20:42 GMT+01:00 Vlad Mihalcea :
>> > Hi,
>> >
>> > It seems like a good step to tackle the SEO optimization problem is to
>> > offer a "curent" link in our site to point to the latest docs.
>> > That's how PostgreSQL and Spring do it and once this link is indexed by
>> > google, it will always render the latest version of the docs:
>> >
>> > http://www.postgresql.org/docs/current/static/
>> >
>> >
>> http://docs.spring.io/spring/docs/current/spring-framework-reference/html
>> >
>> > MySQL does not offer this option and when googling something about MySQL,
>> > there's a big chance of getting a 5.0 page instead of 5.6 or 5.7.
>> >
>> > I think we should add a "current" "symbolic link" in the docs folder:
>> >
>> > https://docs.jboss.org/hibernate/orm/
>> >
>> > and when we publish a new version, we need to go to Google Webmaster
>> Tools
>> > (at least that's how I do it on my blog) and ask google to reindex that
>> > particular "current" link. I guess that could be automated too.
>> >
>> > Vlad
>> > ___
>> > hibernate-dev mailing list
>> > hibernate-dev@lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

[hibernate-dev] Is it possible to let my framework enhance Hibernate more smoothly?

[babyfish]

Hi hibernate-dev friends


I created a java framework by using my spare time since 2008, it's finished 
and published to github 2 months ago, now the tutorial document is finished too.


Github page: 
https://github.com/babyfish-ct/babyfish


The most important documents:
tutorial.html(English) and tutorial_zh_CN.html(Chinese)
(These tutorial documents are also provided as the attachments of this 
email)


(I) Java part: Let's java support "Smart Data Structure".
(a) ObjectModel4Java: smart data structure with bidirectional 
association
(b) Unstable collement elements: Let set/map support unstable 
elements/keys
(c) Bubbled event, not only collection, but also collection view can 
trigger events


(II) JPA part: An ehancement of JPA/Hibernate
(a) ObjectModel4JPA: Enhance ObjectModel4Java to support JPA entity 
objects
(b) QueryPath: Removes the hard code style fetches and orders in the 
data access layer, Uses dynamic descriptors that can be specified and 
dispatched by all the layers.
(c) DistinctLimitQuery: Let's hibernate can do the real paging query 
with collection fetches when the database is Oracle.


As Steve Ebersole said, the JPA part is not smooth. Yes, he's right, I've 
used some byte code hack technologies to change the behavior of hibnerate.


Now, my tutorial document is finished so that everyone can understand this 
framework in short time, if some guys think it's valuable, is it possible to 
let Hibernate do a little refactor so that I can enhance it more smoothly? or 
is it possible to merge the JPA part of my framework and Hibernate together?
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] Hibernate site SEO optimization

[Steve Ebersole]

I've started discussions about this in general wrt the hibernate.org
webpage.  There is a lot of version-specific information there.  Hosting
this specifically for documentation on the doc site would be one option.
Note however that we have limited forms of access to that docs site which
makes it less than easy to manage content out there manually.


On Tue, Dec 8, 2015 at 5:24 AM Vlad Mihalcea 
wrote:

> We could list the stable doc only in the sitemaps and exclude all the
> others from the robots.txt.
> This way Google will only index the stable docs.
>
> To navigate between versions we need to add a selector somewhere on the
> page to load a specific version of the docs, but that doesn't have to be
> indexed by Google.
>
> Vlad
>
> On Tue, Dec 8, 2015 at 1:05 PM, Sanne Grinovero 
> wrote:
>
> > Stefania (my girlfriend but also a professional SEO consultant) also
> > pointed out that we should make sure that indexing engines understand
> > that the documentation pages are intentionally similar, as you get
> > penalised for duplicate content.
> >
> > So as you suggest we need to mark - for each guide - which one is the
> > "main" reference. I don't know if using a sitemap only is enough, I
> > was told that we need to add some headers in each webpage to refer it
> > to its canonical URL, I'll ask if we need both actions.
> >
> > On 7 December 2015 at 08:12, Vlad Mihalcea 
> > wrote:
> > > Thanks for pointing that out.
> > >
> > > The robots.txt is in place https://docs.jboss.org/robots.txt.
> > > But I couldn't find the sitemap.xml
> > >
> > > According to Google:
> > > https://support.google.com/webmasters/answer/156184?hl=en
> > > The sitemap.xml is important if:
> > >
> > > - Your site is really large
> > > - Your site has a large archive of content pages that are isolated or
> > well
> > > not linked to each other. If you site pages do not naturally reference
> > each
> > > other, you can list them in a sitemap to ensure that Google does not
> > > overlook some of your pages.
> > >
> > > So we meet both these two requirements.
> > > Maybe we need to add a sitemap.xml and reference the link to the
> "stable"
> > > docs only and the modification date.
> > >
> > > Vlad
> > >
> > > On Mon, Dec 7, 2015 at 9:46 AM, Gunnar Morling 
> > wrote:
> > >
> > >> Hi Vlad,
> > >>
> > >> We already have something like this, at
> > >> http://docs.jboss.org/hibernate/stable/. The latest final version
> docs
> > >> are available there. It's only that results from there have not a good
> > >> search result ranking apparently.
> > >>
> > >> --Gunnar
> > >>
> > >>
> > >>
> > >> 2015-12-04 20:42 GMT+01:00 Vlad Mihalcea :
> > >> > Hi,
> > >> >
> > >> > It seems like a good step to tackle the SEO optimization problem is
> to
> > >> > offer a "curent" link in our site to point to the latest docs.
> > >> > That's how PostgreSQL and Spring do it and once this link is indexed
> > by
> > >> > google, it will always render the latest version of the docs:
> > >> >
> > >> > http://www.postgresql.org/docs/current/static/
> > >> >
> > >> >
> > >>
> >
> http://docs.spring.io/spring/docs/current/spring-framework-reference/html
> > >> >
> > >> > MySQL does not offer this option and when googling something about
> > MySQL,
> > >> > there's a big chance of getting a 5.0 page instead of 5.6 or 5.7.
> > >> >
> > >> > I think we should add a "current" "symbolic link" in the docs
> folder:
> > >> >
> > >> > https://docs.jboss.org/hibernate/orm/
> > >> >
> > >> > and when we publish a new version, we need to go to Google Webmaster
> > >> Tools
> > >> > (at least that's how I do it on my blog) and ask google to reindex
> > that
> > >> > particular "current" link. I guess that could be automated too.
> > >> >
> > >> > Vlad
> > >> > ___
> > >> > hibernate-dev mailing list
> > >> > hibernate-dev@lists.jboss.org
> > >> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> > >>
> > > ___
> > > hibernate-dev mailing list
> > > hibernate-dev@lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

[hibernate-dev] [Search] Exposing NumericField

[Sanne Grinovero]

It took us a long time to have the concept of "NumericField" fully
exposed to Hibernate Search users, as a primary concept people are
getting familiar with.

Which means of course that the Lucene team is going to get rid of them
in the near future: [1].

NumericField(s) will live for a bit longer in a "backwards-codec"
package, and to be fair the migration makes sense for Lucene as the
new alternative structure is delivering much better performance across
the board (less indexing time, better query times, less index space,
...).

So what I'm wondering now is if it was a mistake to expose this.
For sure since we're up to redesign the API soon we should keep this
in mind, but also while we traditionally made "the best choice"
automatically out of the box about how to translate certain types to
the index world, we always allowed for power users to override our
defaults.

So what's the correct level of abstraction here?

We want to allow power users to use specifics, but not keep breaking
APIs. Or should we just accept that such level of details will keep
changing?

Ideas very welcome..

Thanks,
Sanne

1 - https://issues.apache.org/jira/browse/LUCENE-6917
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] Support for org.hibernate.flushMode setting

[Steve Ebersole]

Well if you read closely I said we support it on the
EntityManager/Session.  As far as I know we have never supported that on
the EntityManagerFactory/SessionFactory.

On Tue, Dec 8, 2015 at 11:50 AM Vlad Mihalcea 
wrote:

> Hi,
>
> I stumble don this question on the forum:
>
> https://forum.hibernate.org/viewtopic.php?f=1=1042301
>
> I remember there used to be a "org.hibernate.flushMode" configuration
> property (Steve mentioned this configuration property on SO too):
>
>
> http://stackoverflow.com/questions/13259677/how-do-i-set-flush-mode-to-commit-in-my-configuration-files
>
> I checked the code base and it looks like we no longer support it. Was
> there any reason for dropping this setting?
>
> Vlad
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

[hibernate-dev] Support for org.hibernate.flushMode setting

[Vlad Mihalcea]

Hi,

I stumble don this question on the forum:

https://forum.hibernate.org/viewtopic.php?f=1=1042301

I remember there used to be a "org.hibernate.flushMode" configuration
property (Steve mentioned this configuration property on SO too):

http://stackoverflow.com/questions/13259677/how-do-i-set-flush-mode-to-commit-in-my-configuration-files

I checked the code base and it looks like we no longer support it. Was
there any reason for dropping this setting?

Vlad
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] Support for org.hibernate.flushMode setting

[Vlad Mihalcea]

Since AUTO requires manual synchronization for native queries, maybe it's
worth adding such a configuration.

http://vladmihalcea.com/2014/08/13/the-dark-side-of-hibernate-auto-flush/

There might be users who choose ALWAYS, especially if they mix Hibernate
with native queries.

What do you think? Should we add a Jira issue for this issue or we should
leave this responsibility to the application layer?

Vlad

On Tue, Dec 8, 2015 at 7:58 PM, Steve Ebersole  wrote:

> Well if you read closely I said we support it on the
> EntityManager/Session.  As far as I know we have never supported that on
> the EntityManagerFactory/SessionFactory.
>
> On Tue, Dec 8, 2015 at 11:50 AM Vlad Mihalcea 
> wrote:
>
>> Hi,
>>
>> I stumble don this question on the forum:
>>
>> https://forum.hibernate.org/viewtopic.php?f=1=1042301
>>
>> I remember there used to be a "org.hibernate.flushMode" configuration
>> property (Steve mentioned this configuration property on SO too):
>>
>>
>> http://stackoverflow.com/questions/13259677/how-do-i-set-flush-mode-to-commit-in-my-configuration-files
>>
>> I checked the code base and it looks like we no longer support it. Was
>> there any reason for dropping this setting?
>>
>> Vlad
>> ___
>> hibernate-dev mailing list
>> hibernate-dev@lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] Forum changes proposal

[Brett Meyer]

On 12/08/2015 02:46 AM, Vlad Mihalcea wrote:
> Hi,
>
> I was discussing with Steve on the HipChat page yesterday that we should
> probably enable these forum options:
> Enable queued posts:
> Ability to put registered users posts to post approval if their post count
> is lower than the specified value below. This setting has no effect on the
> permission setting for post/topic approval. Maximum post count for queued
> posts:
> If queued posts is enabled, this is the post count the user need to reach
> in order to post without post approval. If the users post count is below
> this number, the post is stored in the queue automatically.This way we can
> make sure spam won't reach the forum because we have to approve all posts
> and active users can get their post approved immediately.
+1 from me.  Although, I'd suggest setting that post count extremely 
low.  Even "1" is likely sufficient, considering the spammers always 
seem to open a new account and post a brand new topic.
> We might want to suggest users to use StackOverflow because it's a very
> active community there are we could focus on unanswered questions there
> too. Maybe we can change the hibernate.org site to display the SO tag link
> before our forum. This way we might redirect some posts to SO instead of
> the forum. This can decrease the time to get a response, and many easy
> questions would get answered by other SO users too.
I'm on the fence on this one.

On the one hand, SO is not a user forum.  Keep in mind the hibernate.org 
forums are for more than just issues and usage discussions.  We've had 
new feature discussions start there, general topics, etc.

On the other hand, many issues/usage questions go unanswered -- they'd 
certainly get more eyes and activity on SO.

Maybe the best approach is a hybrid, where we clearly lay out the 
intentions/strengths of each?
> Vlad
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev


___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] Forum changes proposal

[Vlad Mihalcea]

Hi,

I agree that a value of 1 is sufficient too. Once a user posted a
Hibernate-related question, there is no way he will want to spam the forum.

I also think we should keep the forum it's a way to reach the actual dev
team. On SO, you get answers for the community.
So both the forum and SO are important and we should blend them, rather
than pick one over the other.

Vlad

On Wed, Dec 9, 2015 at 12:42 AM, Brett Meyer  wrote:

> On 12/08/2015 02:46 AM, Vlad Mihalcea wrote:
> > Hi,
> >
> > I was discussing with Steve on the HipChat page yesterday that we should
> > probably enable these forum options:
> > Enable queued posts:
> > Ability to put registered users posts to post approval if their post
> count
> > is lower than the specified value below. This setting has no effect on
> the
> > permission setting for post/topic approval. Maximum post count for queued
> > posts:
> > If queued posts is enabled, this is the post count the user need to reach
> > in order to post without post approval. If the users post count is below
> > this number, the post is stored in the queue automatically.This way we
> can
> > make sure spam won't reach the forum because we have to approve all posts
> > and active users can get their post approved immediately.
> +1 from me.  Although, I'd suggest setting that post count extremely
> low.  Even "1" is likely sufficient, considering the spammers always
> seem to open a new account and post a brand new topic.
> > We might want to suggest users to use StackOverflow because it's a very
> > active community there are we could focus on unanswered questions there
> > too. Maybe we can change the hibernate.org site to display the SO tag
> link
> > before our forum. This way we might redirect some posts to SO instead of
> > the forum. This can decrease the time to get a response, and many easy
> > questions would get answered by other SO users too.
> I'm on the fence on this one.
>
> On the one hand, SO is not a user forum.  Keep in mind the hibernate.org
> forums are for more than just issues and usage discussions.  We've had
> new feature discussions start there, general topics, etc.
>
> On the other hand, many issues/usage questions go unanswered -- they'd
> certainly get more eyes and activity on SO.
>
> Maybe the best approach is a hybrid, where we clearly lay out the
> intentions/strengths of each?
> > Vlad
> > ___
> > hibernate-dev mailing list
> > hibernate-dev@lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>
> ___
> hibernate-dev mailing list
> hibernate-dev@lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev