AS7-886 any suggestions on fixing PU.getNewTempClassLoader
by Scott Marlow
I'd like to use the JPA persistence unit getNewTempClassLoader with
EclipseLink sometime for 7.1. Any suggestions how to fix?
Should JPA perhaps duplicate the module classloader logic that reads the
raw VFS classfiles or is there an easier way? It is probably fine to
delegate to the original module class loader for parent level class
loading but not for loading application classes.
The idea of the JPA PU temp class loader is for accessing app classes,
before the app class loader loads them.
https://github.com/jbossas/jboss-as/blob/master/jpa/core/src/main/java/or...
is not yet working.
Thanks,
Scott
12 years, 8 months
Looking for migration expertise in a few areas
by Sande Gilda
Based on the review of the content specification document for Migration
from EAP 5.x to EAP 6, it looks like I'm lacking in material for the
following topics. You can see the current list of all migration topics
and information here:
https://docs.jboss.org/author/display/AS7/How+do+I+migrate+my+application....
Keep in mind that purpose of this guide is to document only those
changes that are necessary to successfully run and deploy EAP5.1
applications on EAP6, not to modify the applications to use the latest
EAP 6 features and functions. Please feel free to update the document if
you have additional information or correct anything that is wrong. If
you do not want to edit the document directly, please send information
to me and I will make the changes.
*Topic
* *Expert *
Examples of JNDI mappings in previous releases and how they might look
now ???
Migrate remote EJB clients to the EAP 6 client API Carlo DeWolf
Jaikiran Pai
???
Migrate EAP 5 deployed applications which make remote invocations to
EAP6 ???
Update your JMS client code Andy Miller
Clebert Suconic
???
Changes you need to make for clustering in EAP 6 ???
Changes you need to make for security in EAP 6 ???
Migrate applications using jboss-beans.xml style deployments ???
Migrate applications using jboss-service.xml style deployments ???
If you have the expertise, know who I could talk to, or know where I can
find material for any of the above topics, please let me know. Also, if
you notice any migration issues or topics I might be missing, please let
me know ASAP!
Thanks,
Sande
12 years, 8 months
datasource/connection-url reference to interfaces/ports
by Scott Stark
The datasource/connection-url property in the domain model is outside of
the interfaces and socket-binding-group usage. The current
datasource_1_0.xsd does not have a reference to sockets or interfaces.
We also don't seem to be setting jboss.server.* system properties that
could be used to create a configuration fragment like:
<datasource jndi-name="java:jboss/datasources/MysqlDS" enabled="true"
use-java-context="true" pool-name="H2DS">
<connection-url>jdbc:mysql://${jboss.server.default.interface}:${jboss.server.socket-binding-group.mysql}/database</connection-url>
<driver>mysql</driver>
<security>
<user-name>sa</user-name>
<password>sa</password>
</security>
</datasource>
What is the plan to allow jca connection factories to integrate into the
interfaces/ports part of the domain model?
This came up as we add support for mysql in the openshift express
cartridge, and modification of the connection-url for the host the
server is running on requires changes in two parts of the standalone.xml
configuration rather than one.
12 years, 8 months
Management Console: changing values that require a restart
by David Bosschaert
Hi all,
Just like to get the general feeling about this.
In the Management Console and via the Detyped API you can in some cases
modify configuration that requires a restart in order to become
effective. I'd like to find out what the general feeling is about this:
Option 1: make it editable via the Console and display a message that
changing this configuration requires a restart.
Option 2: make it viewable only.
So option 2 is clearly the safest option, but has a drawback that people
can't use the console to specify this configuration, they'd have to
crack open the .xml and edit that.
Option 1 gives people a fancy editor over standalone.xml / domain.xml
but does have the disadvantage that the specified values don't get
applied until the restart is done.
How do we generally handle this? Obviously, the best thing to do is
change the behaviour so that the restart isn't needed by sometimes this
isn't the highest priority within the realm of time constraints...
Cheers,
David
12 years, 8 months
Status 2011-08-22
by Kabir Khan
Last week:
JMX management model facade work
As part of ^ I rewrote the management model<->open mbean type conversion, since what I had before was terrible :-)
This week:
Update the subsystem archetype + docs to use the 7.0.1 org.jboss.as:jboss-as-subsystem-test subystem testing harness which was inspired by the 7.0.0 version of the archetype.
Start testing the JMX management model facade in AS and resolve any issues
PTO starting Wednesday, back on Thursday 1st.
12 years, 8 months
JMX add/remove connector
by Kabir Khan
JMX has the following ops
/subsystem=jmx:add-connector(name=xxx,……)
/subsystem=jmx:remove-connector(name=xxx)
I'd like to move these to fit the normal add/remove pattern, e.g.
/subsystem=jmx/connector=xxx:add(…)
/subsystem=jmx/connector=xxx:remove
I didn't find an existing JIRA for this so I created https://issues.jboss.org/browse/AS7-1616
12 years, 8 months
Re: [jboss-as7-dev] SME review for Migration from EAP5.1 to EAP6 beta documentation (JMS Client)
by Kabir Khan
Who is in charge of our messaging subsystem?
On 22 Aug 2011, at 14:05, Sande Gilda wrote:
> Hi Andy and Kabir,
>
> Based on these responses, I plan to add a section for JMS Client migration. Is there any existing community doc for this? I see a some information, for example, https://docs.jboss.org/author/display/AS7/Messaging+configuration, but I'm need help figuring out what people might have done in EAP 5.1 and what they'll need to change to get the application to deploy and run in EAP6.
>
> Who can I work with or where can I go to get this information?
>
> Thanks,
> Sande
>
> On 08/19/2011 02:51 PM, Burr Sutter wrote:
>> EJB clients is a great one.
>>
>> JMS clients as well
>>
>> We often have customers asking how to keep their JMS clients the same but change out some of the App Servers.
>>
>> Usage scenarios are:
>> - Swing app running on 1000 end-user desktops - they wish to change the servers (some of them) but not the clients
>> - App Server to App Server JMS connections - WebSphere app pushes messages to JBoss via JMS - customer does not wish to tamper with the WAS environment but would like to upgrade from AS5/EAP5 to AS7/EAP6
>>
>> Our GSS guys may have a better handle on this item.
>>
>>
>> On 8/18/2011 10:07 PM, David M. Lloyd wrote:
>>> Migrate remote EJB clients to the EAP 6 client API; migrate EAP 5 deployed applications which make remote invocations to EAP 6.
>>>
>>> I have no idea yet what either topic entails though. Hopefully we'll know soon.
>>>
>>> Migrate applications using jboss-beans.xml style deployments. Migrate applications using jboss-service.xml style deployments.
>>>
>>> Hmm, can't think of anything else that isn't already on your list...
>>>
>>> On 08/18/2011 08:58 PM, Sande Gilda wrote:
>>>> I have only heard back from a couple of people. Based on that feedback,
>>>> I have added the following topics:
>>>>
>>>> * Upgrade your Hibernate 3.x application to use Hibernate 4
>>>> * Configure changes for applications that use Hibernate and JPA
>>>>
>>>> If you have any additional comments, concerns, or suggestions, please
>>>> try to let me know by tomorrow, August 19.
>>>>
>>>> Thanks,
>>>> Sande
>>>>
>>>> On 08/12/2011 08:00 AM, Sande Gilda wrote:
>>>>> Thanks Kevin.
>>>>>
>>>>> I forgot to mention in the original email, I need feedback on content
>>>>> by next Friday, August 19.
>>>>>
>>>>> Thanks,
>>>>> Sande
>>>>>
>>>>> On 08/11/2011 04:35 PM, Kevin Barfield wrote:
>>>>>> Adding se-jboss to get more input.
>>>>>>
>>>>>> Kevin Barfield
>>>>>> Sr. Manager - Middleware and Cloud Solutions Architects
>>>>>> 404-760-8069
>>>>>> kevin.barfield(a)redhat.com
>>>>>>
>>>>>> ----- Original Message -----
>>>>>> From: "Sande Gilda"<sgilda(a)redhat.com>
>>>>>> To: "Jason Greene"<jgreene(a)redhat.com>, "Stuart
>>>>>> Douglas"<sdouglas(a)redhat.com>, "Strong Liu"<stliu(a)redhat.com>, "Andy
>>>>>> Taylor"<ataylor(a)redhat.com>, "David M.
>>>>>> Lloyd"<david.lloyd(a)redhat.com>, "James Perkins"<jperkins(a)redhat.com>,
>>>>>> "Carlo DeWolf"<cdewolf(a)redhat.com>, "Jaikiran Pai"<jpai(a)redhat.com>,
>>>>>> "Bill Burke"<bburke(a)redhat.com>, "Allesio
>>>>>> Soldano"<asoldano(a)redhat.com>, "Remy Maucherat"<rmaucher(a)redhat.com>,
>>>>>> "Paul Ferraro"<pferraro(a)redhat.com>, "Jesper
>>>>>> Pedersen"<jpederse(a)redhat.com>, "Andrig Miller"<anmiller(a)redhat.com>,
>>>>>> "Anil Saldhana"<asaldhan(a)redhat.com>, "Marek
>>>>>> Novotny"<mnovotny(a)redhat.com>, "Pete Muir"<pmuir(a)redhat.com>, "Jim
>>>>>> Tyrrell"<jtyrrell(a)redhat.com>, "Robb
>>>>>> Greathouse"<robb.greathouse(a)jboss.com>, "Kevin
>>>>>> Barfield"<kbarfiel(a)redhat.com>
>>>>>> Cc: "Misty Stanley-Jones"<misty(a)redhat.com>, "Bruno
>>>>>> Georges"<bgeorges(a)redhat.com>
>>>>>> Sent: Thursday, August 11, 2011 4:31:00 PM
>>>>>> Subject: SME review for Migration from EAP5.1 to EAP6 beta documentation
>>>>>>
>>>>>> Hi everyone,
>>>>>>
>>>>>> I am working on the Migration from EAP5.1 to EAP6 Migration Guide and
>>>>>> I believe you are the SMEs for my document.
>>>>>>
>>>>>> This is the goal of the document:
>>>>>>
>>>>>>
>>>>>> The purpose of this guide is to document only those changes that are
>>>>>> necessary to successfully run and deploy EAP5.1 applications on EAP6.
>>>>>> It will provide information on how to resolve deployment and runtime
>>>>>> problems and to how prevent changes in application behaviour. This is
>>>>>> the first step in moving to the new platform. Once the application is
>>>>>> successfully deployed and running on the new platform, plans can be
>>>>>> made to upgrade individual components to use the new functions and
>>>>>> features of AS7.
>>>>>> I have tried to pull material from actual migrations and from the
>>>>>> email lists, but I'm sure there is a lot that I've missed. Much of
>>>>>> the material that's been collected can be found here:
>>>>>>
>>>>>>
>>>>>> https://docs.jboss.org/author/display/AS7/How+do+I+migrate+my+application...
>>>>>>
>>>>>> Information about known example application migrations, including the
>>>>>> step-by-step debugging guide, can be found here:
>>>>>>
>>>>>>
>>>>>> https://docs.jboss.org/author/display/AS7/Example+Applications
>>>>>> Can you please look over the following content specification for the
>>>>>> documentation? Please let me know what I am missing and if I am
>>>>>> including anything that should not be there. Also, if you know of
>>>>>> other people who might be able to provide information about migration
>>>>>> requirements, please let me know so I can talk to them and add them
>>>>>> to the SME list.
>>>>>>
>>>>>> Thanks in advance,
>>>>>> Sande
>>>>>>
>>>>>>
>>>>>>
>>>>>> T - Migrate your application from EAP 5 to EAP 6
>>>>>>
>>>>>> T - Update your application's dependencies due to class loading changes
>>>>>> (This section will reference core documentation on modules and
>>>>>> classloading)
>>>>>> T - Understand module dependencies
>>>>>> T - Use Tattletale to find application dependencies
>>>>>> T - Create or modify files that control class loading in EAP 6
>>>>>> T - Resolve class loading exceptions and other errors
>>>>>>
>>>>>> T - Update your datasource configuration
>>>>>> (This section will reference core documentation on datasource
>>>>>> configuration)
>>>>>> T - Define the datasource
>>>>>> T - Install the JDBC Driver
>>>>>> T - Configure your datasource for Hibernate and JPA
>>>>>>
>>>>>> T - Update your application JNDI namespace names
>>>>>> (This section will reference core documentation on portable JNDI names)
>>>>>> T- Review the JNDI Namespace Rules
>>>>>> T - Modify your application code to follow the new JNDI namespace rules
>>>>>>
>>>>>> T - Modify logging dependencies
>>>>>> (This section will reference core documentation on JBoss logging)
>>>>>> T - Update your code for third-party logging frameworks
>>>>>> T - Modify code to use the new JBoss Logging Framework
>>>>>>
>>>>>> T - Replace JPA/Hibernate Second Level Cache with Infinispan
>>>>>> (This section will reference core documentation on Infinispane)
>>>>>>
>>>>>> T - Configure security for basic authentication
>>>>>> (This section will reference core documentation on security)
>>>>>>
>>>>>> T - Configure JAX-RS / Resteasy changes
>>>>>> (This section will reference core documentation on JAX-RS)
>>>>>>
>>>>>> T- Other changes needed for migration to EAP6
>>>>>> T - Change Maven plugin name
>>>>>> T - Change ResourceBundle properties location
>>>>>>
>>>>>> R- Migration of example applications
>>>>>> R - Migrate Seam JPA example
>>>>>> R - Migrate Seam Booking example
>>>>>> R - Migrate Performance application example
>>>>>> T - Migrate Seam Booking binaries - Step-by-Step debugging guide
>>>>>>
>>>>>> T - Migrate Seam 2 archives to JBoss AS 7
>>>>>> - Update the datasource configuration
>>>>>> - Add any required dependencies
>>>>>> - Copy dependent archives from outside frameworks or other locations
>>>>>> - Debug and resolve Seam 2 JNDI errors
>>>>>>
>>>>>> T - Migrate Spring archives to JBoss AS 7
>>>>>> T - Update Hibernate applications
>>>>>> T - Update JPA applications
>>>>>> T - Update native JDBC applications
>>>>>> T - Manage application dependencies
>>>>>>
>>>>>> What other tasks might be required when migrating your application
>>>>>> from EAP5 to EAP6?
>>>>>> What have I missed?
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>
>>>
12 years, 8 months
Dear subsystem owners/components leads ....
by Heiko Braun
Currently the console provides management operations for a very basic set of use cases.
This needs to be extended for AS 7.1.
Going forward we require your feedback. What do you think should be tackled next?
Most of these questions are very problem domain specific. It would be great if all component leads
could take some time and think about the following:
- does my component expose reasonable management operations?
- what would developers expect? what about system administrators?
- how does play within a managed domain?
- is my component part of a layered product? what's needed there?
We don't expect you to provide the UI, but at least the low level management operations need to be implemented by your team.
Think about the most frequently used operations. We don't need to expose every nitty gritty details of you configuration schema.
It would be really great help, if you could assign somebody to be our point of contact for all questions management related.
Make sure you plan some time early in this iteration so we can work through these issues.
Prepare for change requests and new component releases.
Last but not least, some areas that I believe can be improved:
- security
- clustering
- ejb, jpa, weld
- transactions
- messaging (non JMS)
- infinispan
Thanks for your help,
Ike
12 years, 8 months
