[Javassist Development] New message: "Re: ScopedClassPoolRepositoryImpl and default ClassPool"
by Flavia Rainone
JBoss development,
A new message was posted in the thread "ScopedClassPoolRepositoryImpl and default ClassPool":
http://community.jboss.org/message/528747#528747
Author : Flavia Rainone
Profile : http://community.jboss.org/people/flavia.rainone@jboss.com
Message:
--------------------------------------------------------------
> alesj wrote:
>
>
> > Now I'm open for suggestions on what should be the next step: to write a patch for Javassist; to do an alpha release of the new version and update depending projects (JBoss AOP and JBoss Reflection, besides deployers-vfs tests); or to do more refactoring and improve something that doesn't look ok.
> Whatever gets you back working on the Reflect+Javassist impl asap. ;-)
>
> Check if there are no regressions with dependening projects and perhaps create a new Alpha release.
>
> Like I said, we should try to get Reflect fully working on Javassist + Classpools asap,
> to actually see the whole picture: issues, benefits, bugz, optimizations, ...
> In order to speed up things, Kabir is gonna help you with this -- you just tell him where you need him the most.
Ok! I'm doing the alpha release and then I'm updating the depending projects with it.
After that, I'm going to port the changes to JBoss AOP trunk, as we agreed on before.
IMO, this porting and updating things is work for one person only. Kabir could help me by doing the implementation of the https://jira.jboss.org/jira/browse/JBREFLECT-5 that we are going to need. Without that, we won't be able to to see the whole picture, and that's the main piece that we are missing right now.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528747#528747
14 years, 10 months
[Javassist Development] New message: "Re: ScopedClassPoolRepositoryImpl and default ClassPool"
by Ales Justin
JBoss development,
A new message was posted in the thread "ScopedClassPoolRepositoryImpl and default ClassPool":
http://community.jboss.org/message/528723#528723
Author : Ales Justin
Profile : http://community.jboss.org/people/alesj
Message:
--------------------------------------------------------------
> Now I'm open for suggestions on what should be the next step: to write a patch for Javassist; to do an alpha release of the new version and update depending projects (JBoss AOP and JBoss Reflection, besides deployers-vfs tests); or to do more refactoring and improve something that doesn't look ok.
Whatever gets you back working on the Reflect+Javassist impl asap. ;-)
Check if there are no regressions with dependening projects and perhaps create a new Alpha release.
Like I said, we should try to get Reflect fully working on Javassist + Classpools asap,
to actually see the whole picture: issues, benefits, bugz, optimizations, ...
In order to speed up things, Kabir is gonna help you with this -- you just tell him where you need him the most.
Our target should be AS6_M3, it doesn't mean we need to be at 100%,
but we should be able to run a portion of testsuite with Reflect's TypeInfoFactory being Javassist based.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528723#528723
14 years, 10 months
[Javassist Development] New message: "Building Web 2.0 UIs with JSF, Realtime Updates with JSF and Ajax Push Taught at GIDS"
by shaguf mohtisham
JBoss development,
A new message was posted in the thread "Building Web 2.0 UIs with JSF, Realtime Updates with JSF and Ajax Push Taught at GIDS":
http://community.jboss.org/message/528693#528693
Author : shaguf mohtisham
Profile : http://community.jboss.org/people/shaguf5575
Message:
--------------------------------------------------------------
JavaServer Faces is a Java-based Web application framework intended developed to simplify development integration of Web-based user interfaces. It is often mentioned together with Ajax, a combination of technologies that makes it possible to create rich user interfaces. Since JSF supports multiple output formats, Ajax-enabled components can easily be added to enrich JSF-based user interfaces. Oracle's Frank Nimphius says that Service Oriented Architecture (SOA) has become a reality in modern software development but Web services don't have a user interface. This is fine if communication is between machines. But what about human interaction like in data entry and work flow? Users need an application display they feel comfortable working with. So what about building Web 2.0 user interfaces for service oriented architectures? Does it work, or does it hurt - and if so, how bad is it? Frank is coming this summer to India's biggest summit for the software developer ecosystem - Great Indian Developer Summit (http://www.developersummit.com/) to show how JavaServer Faces can be used to build compelling Ajax user interfaces for Web Services models giving end users a comfortable working environment that includes client side validation and user interface customization.
In his second session at GIDS 2010, Frank addresses the topic of implementing automatic UI refreshes. To web application users, it must appear as if the Web reinvents itself once a year with more interactive UIs, increasing performance through partial page refreshes, and desktop-like usability patterns that allow users to become as productive using web applications as they are using real desktop clients. One technical detail, though, hasn't changed in the past and is unlikely to change in the near future: HTTP. Hypertext Transfer Protocol is based on the request-response principle in which the client sends a query to the server and the server responds with the requested data. Between requests, no connection is maintained between the client and the server that would allow server-side logic to send more data unasked. Any changes in the underlying data layer used by an application are first detected within the next client request. Hopefully, it doesn't come to you by surprise when we say that in the modern days of Web 2.0 and Rich Enterprise Applications (REA), the Web still is disconnected and stateless. So, in these modern days of Web 2.0 and Rich Enterprise Applications (REA), is the Web still is disconnected and stateless? Not really, because you frequently use some applications on the Web that update their client UIs with server-side changes without your needing to do anything. The question, therefore, is how this was accomplished and whether you can do the same in JavaServer Faces. In his session, Frank will guide attendees through the options that are available in AJAX and other implementation technologies of Rich Internet Applications (RIA) to implement automatic UI refreshes.
Frank Nimphius is a principal product manager for application development tools at Oracle Corporation since 1999. He actively contributes to the development of Oracle JDeveloper and the Oracle Application Development Framework (ADF). He represents the Oracle J2EE development team at J2EE conferences world wide, including various Oracle user groups and the Oracle Open World conference. The talk 'Building Web 2.0 User Interfaces for Web Service Models using JSF' will be co-presented by Jobinesh Purushothaman. Jobinesh Purushothaman is an enterprise Java specialist with 10+ years of experience in the industry. He is involved in design and architectural decisions of various products using ADF and JavaEE technologies. He is interested in developing more simplified enterprise technologies where developers can focus on their business solutions rather on the technology complexities.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528693#528693
14 years, 10 months
[JCA Development] New message: "Re: Standalone JCA: JNDI binding for multiple connection factories..."
by Jesper Pedersen
JBoss development,
A new message was posted in the thread "Standalone JCA: JNDI binding for multiple connection factories...":
http://community.jboss.org/message/528646#528646
Author : Jesper Pedersen
Profile : http://community.jboss.org/people/jesper.pedersen
Message:
--------------------------------------------------------------
> The 1.6 Final Draft November 2009 argues with itself over this:
Nah, 6.5.1.3, 17.5.1.1, 20.6.2, 20.6.3 specifies the implementation requirements for a CF (javax.resource.Referenceable + java.io.Serializable).
The text in 20.6.1 gives a hint to the implementor, that if the +naming server+ doesn't support both mechanisms, one can be used. See the 3 bullets in the section.
> I'm not sure about the unique name part though.
Yes, this has to be designed.
> What is the alias? Do you mean generically or with something
> like a LinkRef (I've never used that before so not sure how it works
> yet).
Something like,
java:/eis/myresourceadapter --> java:/uniquenamegeneratedbythecontainer
LinkRef or other solutions is an implementation detail, we can worry about once we have the design for the unique names.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528646#528646
14 years, 10 months
[Javassist Development] New message: "Re: ScopedClassPoolRepositoryImpl and default ClassPool"
by Flavia Rainone
JBoss development,
A new message was posted in the thread "ScopedClassPoolRepositoryImpl and default ClassPool":
http://community.jboss.org/message/528638#528638
Author : Flavia Rainone
Profile : http://community.jboss.org/people/flavia.rainone@jboss.com
Message:
--------------------------------------------------------------
> mailto:flavia.rainone@jboss.com wrote:
>
> I'm calling that new module scoped-classpool. Once it is ready, we can decide whether it would be a good idea to use those changes as a patch for Javassist, or whether we wanna keep it the way it is.
That new module is created. I removed everything that I thought is no longer being used, and replaced all references to javassist.scopedpool classes by references to the new org.jboss.classpool.scoped classes.
A summary of what has been done can be obtained by looking at the svn history log:
- Copied Scoped ClassPool classes from Javassist to a new scopedpool module.
- ScopedCPRepository is no longer singleton, it is an abstract class with a protected constructor instead. The default class pool can be defined as a parameter of the constructor.
- Replaced all references to javassist.scopedpool package by org.jboss.classpool.scoped package.
- Deleted ScopedClassPoolFactoryImpl class
Now I'm open for suggestions on what should be the next step: to write a patch for Javassist; to do an alpha release of the new version and update depending projects (JBoss AOP and JBoss Reflection, besides deployers-vfs tests); or to do more refactoring and improve something that doesn't look ok.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528638#528638
14 years, 10 months
[JCA Development] New message: "Re: Standalone JCA: JNDI binding for multiple connection factories..."
by Scott Marlow
JBoss development,
A new message was posted in the thread "Standalone JCA: JNDI binding for multiple connection factories...":
http://community.jboss.org/message/528621#528621
Author : Scott Marlow
Profile : http://community.jboss.org/people/smarlow@redhat.com
Message:
--------------------------------------------------------------
It is a requirement that a CF implements the
javax.resource.Referenceable and java.io.Serializable - so that will
always be the case. Hence the current instanceof check.
Dealing
with resource adapters that doesn't implement this requirement could be
something we could look at down the road - but ideally people should
fix their code. That is why we have the validator.
The 1.6 Final Draft November 2009 argues with itself over this:
"20.6.1 Responsibilities In both managed and non-managed environments, registration of a connection factory instance in the JNDI namespace must use either the JNDI Reference or Serializable mechanism. ... "
"6.5.1.3 Additional Requirements ... A connection factory implementation class must implement the interface javax.resource.Referenceable. ... "
An idea could be to create a unique name for each CF, and then
create an alias for the unique name that the user will use. That would
allow us to move the primary names in the JNDI without having to change
any user code. I thinking of java:/eis/, java:global, and other
scenarios depending where the JCA container is deployed.
The
key is to make it simple for users - a JNDI name should be optional,
and in that case we would create an alias based on our default
strategy, f.ex. java:/eis/resourceadapter as we have now.
Also
we should consider how the deployment of the same resource adapter
multiple times - under different names should work. Making the resource
adapter archive name part of the unique name could be an idea - we can
always use the metadata repository to search for information.
+1 for not having to change any user code due to how we manage the CF jndi binding I'm not sure about the unique name part though.
What is the alias? Do you mean generically or with something like a LinkRef (I've never used that before so not sure how it works yet).
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/528621#528621
14 years, 10 months