[Beginner's Corner] - Jboss server exception while deploying jsf application
by Ranjanabha Bhattacharya
Ranjanabha Bhattacharya [http://community.jboss.org/people/ranjanabha123] created the discussion
"Jboss server exception while deploying jsf application"
To view the discussion, visit: http://community.jboss.org/message/588687#588687
--------------------------------------------------------------
I am a newbie to jsf and I am trying to deploy a jsf application in jboss 4.02.After I am starting the server I am getting following error.
15:11:01,378 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.web.deployment:war=web-console.war,id=-1390589069
State: NOTYETINSTALLED
I Depend On:
jboss.admin:service=PluginManager
ObjectName: jboss.admin:service=PluginManager
State: CONFIGURED
I Depend On:
jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory
Depends On Me:
jboss.web.deployment:war=web-console.war,id=-1390589069
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFactory
State: NOTYETINSTALLED
Depends On Me:
jboss.admin:service=PluginManager
Please guide me to solve the problem.My jsf page is not displaying in browser I think may it is due to this problem only
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/588687#588687]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 4 months
[JBoss Tools] - Create GWT Projects with JBoss Tools and Eclipse WTP
by Andre Dietisheim
Andre Dietisheim [http://community.jboss.org/people/adietish] modified the document:
"Create GWT Projects with JBoss Tools and Eclipse WTP"
To view the document, visit: http://community.jboss.org/docs/DOC-15794
--------------------------------------------------------------
h1. Use Eclipse WTP, get there with the standard
If you want to create GWT applications you unfortunately cannot do it the WTP way and create a so called dynamic web project. The Google plugins implement their own set of views, wizards, launchers and mostly duplicate what's already present and defacto standard in WTP. The consequence is that you'd have to deal with workarounds if you want to get functionalities (run/deploy on JBoss etc.) Google does not offer.
We therefore developed an experimental integration plugin for GWT that allows you to create GWT projects in the way most Eclipse users are used to: by creating Dynamic Web Projects.
h1. Preface
Eclipse offers nice tools to create web applications. The base framework's what we call the Eclipse Web Tools Platform (WTP). Eclipse WTP delivers a standard for most aspects involved when you create web applications.
The google web toolkit, GWT, is a nice framework to develop web applications. Google delivers a plugin for Eclipse and developing with GWT is a very pleasant experience. The GWT plugin uses an embedded jetty to run the application that you develop. Google unfortunately did not base its work on Eclipse WTP and does not comply to the Eclipse project structure for web application. So if you want to use JBoss instead of jetty, the approach to take is not as handy and intuitive as it could be. Furthermore there's no way to use and integrate into plugins that other solution providers offer. You mostly have to proceed by workarounds to get what Google does not offer.
We developed a set of (experimental) plugins that create GWT projects by extending Eclipse WTP. Our plugins implement well known usage patterns and integrate well with all Eclipse components that use the common standard for web projects. The most obvious benefit is that deploying to JEE application servers (and JBoss partcullarly) is as easy as it is with any other web project.
h1. Solution
Install and use the JBoss GWT Integration. You'll then be able to create GWT projects the WTP way and fully enjoy it's full-blow features and standardized usage patterns.
This How-To shows you all the steps to install the plugins and how to create a dynamic web project that's GWT enabled.
h2. Install JBoss GWT Integration
Add the Google Eclipse Plugins update site:
> http://dl.google.com/eclipse/plugin/3.6/ http://dl.google.com/eclipse/plugin/3.6/
Add the JBoss Tools update site:
> http://download.jboss.org/jbosstools/updates/nightly/trunk/ http://download.jboss.org/jbosstools/updates/nightly/trunk/
And Install the JBoss GWT Integration
http://community.jboss.org/servlet/JiveServlet/showImage/6254/Picture+4.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6254/Picture...
h2. Create a Dynamic Web Application Project
Make sure you have a JEE server (JBoss application server for instance) in your Eclipse environment. If not, download and declare it to your Eclipse IDE:
http://community.jboss.org/servlet/JiveServlet/showImage/6260/Picture+12.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6260/Picture...
http://community.jboss.org/servlet/JiveServlet/showImage/6259/Picture+11.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6259/Picture...
You're now ready to create a *Dynamic Web Project*.
http://community.jboss.org/servlet/JiveServlet/showImage/6256/Picture+5.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6256/Picture...
The wizard picks your server (runtime) and allows you to configure the various characteristic of your web project.
The *configuration* group allows you to pick the different facets of your project. We provide a *Google Web Toolkit* facet that will configure the GWT related characteristics.
Hit *Modify...*
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-18-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-18...
and select the *Google Web Toolkit* facet.
http://community.jboss.org/servlet/JiveServlet/showImage/6262/Picture+14.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6262/Picture...
A few wizard steps further, you may choose to get some GWT *sample code*.
http://community.jboss.org/servlet/JiveServlet/showImage/6411/generate-sa... http://community.jboss.org/servlet/JiveServlet/downloadImage/6411/generat...
You get the Hello World sample that you get when you use the Google Wizard. We just put it to the *WebContent* folder you configured in your Dynamic Web Project wizard (WTP default opposed to what Google does in their plugin). The sample's a fully working GWT application that allows you to get a first impression of what developing with GWT looks like.
h1. Cross compile to Javascript
GWT is about programming in Java and getting javascript for the browser. GWT achieves this with a cross-compiler that creates the javascript for you.
In order to get the project up and running you now need to cross compile the sample's client java code to javascript. Our project has the *GWT nature* and therefore offers the Google compiler in the context menu.
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-18-627... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-18...
h1. Deploy to JBoss
We are now ready to deploy our application. We strictly use the standard Eclipse *WTP* infrastructure in our setup, So you may deploy your GWT application in the same manner you usually deploy and run classic web applications with Eclipse WTP. You have to add the application to a server that's registered in the WTP *servers view*. We deploy our application to our JBoss application server by selecting it in the and choosing *Add and Remove...*
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-18-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-18...
You can now add the GWT application to your server. WTP will make sure that it gets deployed and the deployed artifacts are in sync with your workspace (even when you change code, resources, configurations, etc.)
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-18-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-18...
h1. Run your application and launch your browser
You may now run your application. We completely comply to the views and steps Eclipse WTP offers to web developers. So there's no custom way to start a server in our setup. We select our JBoss instance in the *Servers view* and *start* it.
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-18-626... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-18...
You can now point your browser to the address and port that your JBoss server's bound to.
http://community.jboss.org/servlet/JiveServlet/showImage/6271/Picture+2.png http://community.jboss.org/servlet/JiveServlet/downloadImage/6271/Picture...
h2. Speed up my development cycle!
The approach we've choosen so far uses an extra cross compile step to deploy the application after each change. That's very reliable but it gets tedious at development time. Google delivers a so called hosted/development mode. Its major benefit is that you dont need to cross compile on each change but you can change and test on the fly. This magic is achieved with a browser plugin and a google runtime that interprets your java code at runtime. Changing, testing, changing, testing etc. gets much faster and pleasant, the cross-compilation step's not needed any more.
h2. Launch GWT Codeserver
If you launch your application as Google Web Application, you'll be able to code and test on the fly. The GWT browser plugin will communicate with the GWT code server and execute your changes on the fly.
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-18-646... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-18...
You need to tell the browser plugin where your code server may be reached. You do that by using an *additional url parameter*. Your browser URL now reads as follows:
> http://localhost:8080/gwt-test/?gwt.codesvr=127.0.0.1:9997 http://localhost:8080/gwt-test/?gwt.codesvr=127.0.0.1:9997
Point your browser to this URL and you'll get the same page as before, nothing spectacular so far.
Now get back to your client code and change the button label, to see if changes are picked on the fly now.
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-18-640... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-18...
Do not cross-compile, get back to your browser and reload. What you see reflects the changes in your code. You don't need to cross compile to develop your app!
http://community.jboss.org/servlet/JiveServlet/showImage/102-15794-18-640... http://community.jboss.org/servlet/JiveServlet/downloadImage/102-15794-18...
To be picky on the issue you could now go to the launch configuration and disable the jetty google usually uses to serve your GWT application:
http://community.jboss.org/servlet/JiveServlet/showImage/6413/disable-bui... http://community.jboss.org/servlet/JiveServlet/downloadImage/6413/disable...
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/docs/DOC-15794]
Create a new document in JBoss Tools at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=102&co...]
13 years, 4 months
[JBoss Tools] - JBoss Tools 3.2 is Finally here!
by Max Rydahl Andersen
Max Rydahl Andersen [http://community.jboss.org/people/max.andersen%40jboss.com] modified the blog post:
"JBoss Tools 3.2 is Finally here!"
To view the blog post, visit: http://community.jboss.org/community/tools/blog/2011/02/21/jboss-tools-32...
--------------------------------------------------------------
http://in.relation.to/service/File/10824 http://in.relation.to/service/File/10824
h4. 3.2.0
[ http://www.jboss.org/tools/download Download] [ http://download.jboss.org/jbosstools/updates/stable/helios/ Update Site] [ http://marketplace.eclipse.org/content/jboss-tools-1 Market Place] [ http://docs.jboss.org/tools/whatsnew What's New] [ http://docs.jboss.org/tools/3.2.0.Beta1/ Documentation] [ http://www.jboss.com/index.html?module=bb&op=viewforum&f=201 Forums] [ http://jira.jboss.com/jira/browse/JBIDE JIRA] [ http://twitter.com/jbosstools Twitter]
I'm very happy to be able to announce that we pushed out JBoss Tools 3.2 to the servers shortly before the weekend.
h2. Installation/Upgrade
Existing Eclipse Workspaces used with JBoss Tools 3.1 will work with JBoss Tools 3.2, but do take a backup of your workspace to be on the safe side.
As per tradition the updatesite is now moved over to a stable location
http://download.jboss.org/jbosstools/updates/stable/helios/
To "upgrade" from JBoss Tools 3.1 to JBoss Tools 3.2 you need to install Eclipse 3.6 and add the updatesite. Updating Eclipse major versions via updatesite does sometime work, but we do recommend a clean install to make it all a bit cleaner.
If you don't like messing with updatesites you can also install JBoss Tools 3.2 via Eclipse Marketplace - simply use *Help > Eclipse Marketplace* directly from Eclipse and find JBoss Tools 3.2 (Helios) via the Search facility.
h2. New Features
The following paragraphs outlines the highlights from the JBoss Tools 3.2 release, but I recommend reading the complete
http://docs.jboss.org/tools/whatsnew What's New lists if you want to see all the noticable changes and improvements that have been made since JBoss Tools 3.1.
h3. JSF 2
The Visual Page Editor and our XHTML structured editors now supports JSF 2; especially the notion of composite components which is a new feature of JSF 2 allowing users to much easier define reusable components for their application or framework.
JSF 2 also provides a new standardized approach to load up resources via the classpath and web archives; these are all supported by JBoss Tools making the visual page editor render even more realistically the layout of the page but also code completion, navigation and even quickfixes now benefit from this additional information to make it easy to fix issues and navigate to the linked resources instantly.
h3. Context & Dependency Injection (CDI)
The CDI tooling have received a lot of updates, especially in context of providing validations of all the error handling cases covered by the CDI TCK test suite and a few other hints provided by the Weld CDI Team.
There is also a good set of wizards, code navigations and quickfixes added in this release and I recommend you go read http://community.jboss.org/community/tools/blog/2011/01/31/overview-of-co... Alexey Kazakov's blog about this feature set.
h3. Visual Page Editor
Besides supporting JSF 2 better in this release various other improvements were done to the Visual Page Editor.
* Templates for jBPM, Spring and Richfaces 4 were added/improved
* DocBook support were made more complete and is now a separately named editor
* A generic "Split-Editor" functionallity were added (can be used with any Eclipse editor)
* The UI were cleaned up to fit better into the Eclipse IDE
h3. Servers, Packaging & Remote Deployment
The biggest new feature for the Application Server integration in JBoss Tools 3.2 is the introduction of Remote Deployment.
Remote Deployment works (more or less) just like the Local deployment except instead of using local file copies we now relay the file transfer to the Eclipse Remote System Explorer API; this then allows you to deploy to systems via SSH, FTP, etc.
This Remote Deployment not only works for the JBoss Application Server adapters but is also provided via the "Deploy Only" server meaning you can use it to deploy any project to any application server or system which supports hotdeployment by scanning their local file system for changes.
We've also improved support for "non-WTP" style projects by enabling you to right click Folders and mark them as Deployable. These deployable folders can then be deployed to any of the Server adapters provided by JBoss Tools, including the Deploy Only server.
The JBoss Server Adapter now also supports the new JBoss 6 and updated versions of JBoss Enterprise Application Platform based servers.
h2. Automatic Runtime Detection
One of the big hassles of any IDE configuration is to identify and configure your various runtimes, such as JBoss Application Server, Seam, jbpm, ESB, Drools, JDK's etc.
We've contributed the installer logic from our JBoss Developer Studio 4 product into the actual JBoss Tools plugins and enhanced it so it can be configured to scan one or more directories at startup for new runtimes; if it detects a new runtime it will ask if it should add it and JBoss Tools will do a default installation of the runtime - freeing you from having to go through the various runtime user interfaces.
This feature is available under Eclipse Preferences in *JBoss Tools > JBoss Tools Runtime Detection*
In the future we plan to add more runtime detections, not just JBoss based ones.
h3. Google GWT (Experimental)
Google's Eclipse plugin for GWT does not provide seamless integration with Eclipse WTP based projects; thus we made an Eclipse Facet that allows you to easily enable Google GWT on your WTP project and not having to use custom wizards and special projects to get started with the Eclipse GWT tooling.
Please note that since Google are not providing stable named features from their updatesite to have Eclipse updatesites work together, it is necessary to install Google GWT plugin manually before trying to use our Google GWT facet.
See http://community.jboss.org/docs/DOC-15593 Andre's article on how to use this Google GWT feature.
h3. DeltaCloud (Experimental)
The tooling for Delta Cloud provides a perspective and a few views to easily interact with systems such as SteamCannon that provide a DeltaCloud API.
This gives you the ability to browse, start & stop virtual machines hosted by cloud service providers such as EC2 and Rackspace.
You can try it out by using https://try.steamcannon.org/deltacloud/api https://try.steamcannon.org/deltacloud/api as the URL for a Delta Cloud connection.
Note, DeltaCloud tooling is marked experimental while the DeltaCloud API and implementations are stabilizing. If needed we will provide an update to support the latest/stable DeltaCoud servers.
h3. Maven
We've continued to expand the support for Maven projects by extending m2eclipse tooling to automatically configure projects based on the dependencies of your project.
Thus now if you import or configure a Maven based project and it uses a standard dependency for either Seam, CDI, JSF, Hibernate or GateIn/Portal the features for these frameworks will now be enabled and configured automagically.
You can control this per framework under Eclipse Preferences via *JBoss Tools > JBoss Maven Integration*
To see an example of this applied, look at http://community.jboss.org/community/tools/blog/2011/02/21/getting-starte... Snjezana's blog where she illustrate how via Project Examples you can easily get started with the CDI and JSF tooling. This blog works because of the Maven Integration provided here.
h3. Modeshape
Modeshape provides a JCR based view on many different datasources such as file systems, databases, other JCR repositories and even your own services and applications.
The Modeshape tooling provided in JBoss Tools 3.2 gives you a way to easily connect to a Modeshape server, browse it content and checkin/checkout content from and to the Eclipse workspace.
h3. Teiid Designer
The Teiid Designer that is used to visualize model your datamodel and transformations as supported by the Teiid runtime is now included into JBoss Tools.
The Teiid Designer plugins also provides a testbed for testing and exploring your Teiid configured dataservices.
You can read more about Teiid Designer on its http://www.jboss.org/teiiddesigner community page.
h3. BPEL
The BPEL tooling is based on the Eclipse BPEL project but provides a set of bugfixes and features that have not yet made it back to the Eclipse BPEL project, especially in context of supporting deployment to other systems than Tomcat based systems such as Apache ODE. We support the Riftsaw JBoss based BPEL system.
If you want to read about the BPEL feature set and its future (its fixes are being contributed back to Eclipse.org) you can read http://community.jboss.org/community/tools/blog/2011/01/24/bpel-technical... Bob Brodt's blog about this.
h3. WebServices
We've added some much simpler wizards for creating JAX-RS or even JAX-WS webservices to the tooling; but even more interesting is the new Webservice Tester UI which gives you a view to easily query a SOAP or REST based webservice and introspect its result.
Brian Fitzpatrick wrote a http://community.jboss.org/community/tools/blog/2011/02/08/tools-tools-tools couple of http://community.jboss.org/docs/DOC-15778 blogs http://community.jboss.org/docs/DOC-15749 about it, giving you an overview of the new improvements for the WebServices support.
h3. Usage Reporting
When you install a JBoss Tools plugin, on the first startup of Eclipse a dialog will ask if you wish to send anonymous usage data to us. We use that information to see which OS's, system configurations and plugins you are running plus we get to see how fast (or slow) new versions of spreads over the world.
h3. ...and much more...
The above highlights are just a subset of the over 1600 issues fixed and implemented over the last many months thus the best way to get to know it all is to try it out :)
Let us know how it goes and above all,
Have fun!
--------------------------------------------------------------
Comment by going to Community
[http://community.jboss.org/community/tools/blog/2011/02/21/jboss-tools-32...]
13 years, 4 months
[Beginner's Corner] - Re: Secure access to an EJB3.0
by Pablo Fraga
Pablo Fraga [http://community.jboss.org/people/pablo.fraga1975] created the discussion
"Re: Secure access to an EJB3.0"
To view the discussion, visit: http://community.jboss.org/message/588986#588986
--------------------------------------------------------------
Hi,
I had the same problem, first i was trying to authenticate the client with the following code:
Properties env = new Properties();
env.setProperty(Context.SECURITY_PRINCIPAL, "caja");
env.setProperty(Context.SECURITY_CREDENTIALS, "password");
env.setProperty(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.security.jndi.JndiLoginInitialContextFactory");
env.setProperty(Context.PROVIDER_URL, "localhost:1099");
Debugging server side i found that principal doesn't propagate correctly, crawling the web i found this link:
http://msikora.typepad.com/michael_sikora_on_java_ee/2009/03/converting-t... http://msikora.typepad.com/michael_sikora_on_java_ee/2009/03/converting-t...
Where it says that i had to use the following code:
SecurityClient securityClient = SecurityClientFactory.getSecurityClient();
securityClient.setSimple("caja", "password");
securityClient.login();
InitialContext ctx = new InitialContext();
The problem is that aparently org.jboss.security.client.SecurityClient and org.jboss.security.client.SecurityClientFactory appears to apply to JBoss 5.0.0 and not to JBoss 4.2.3 the one we still use in our production environment.
Any help would be apreciated!
Thanks,
Pablo.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/588986#588986]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 4 months
Re: [jboss-user] [JBoss Tools] - Create GWT Projects with JBoss Tools and Eclipse WTP
by Gustavo Andres Brey
Gustavo Andres Brey [http://community.jboss.org/people/gbrey] commented on the document
"Create GWT Projects with JBoss Tools and Eclipse WTP"
To view all comments on this document, visit: http://community.jboss.org/docs/DOC-15794#comment-5452
--------------------------------------------------
Hi Andre,
I cannot install GWT Plugin and SDK, this is the error:
+Cannot complete the install because one or more required items could not be found.+
+ Software being installed: Google Plugin for Eclipse 3.6 2.2.0.v201102111811 (com.google.gdt.eclipse.suite.e36.feature.feature.group 2.2.0.v201102111811)+
+ Missing requirement: Google Plugin for Eclipse 3.6 2.2.0.v201102111811 (com.google.gdt.eclipse.suite.e36.feature.feature.group 2.2.0.v201102111811) requires 'org.eclipse.mylyn.commons.ui 0.0.0' but it could not be found+
Thanks,
--------------------------------------------------
13 years, 4 months
[JNDI and Naming] - JNDI lookup JBoss 6 -> JBoss 5.1: ProxyFactory not found
by Ignacio de Cordoba
Ignacio de Cordoba [http://community.jboss.org/people/icordoba] created the discussion
"JNDI lookup JBoss 6 -> JBoss 5.1: ProxyFactory not found"
To view the discussion, visit: http://community.jboss.org/message/588860#588860
--------------------------------------------------------------
Hello,
I need to perform a remote JNDI lookup from a JBoss 6 to a JBoss 5.1 server. I get the following exception:
Caused by: java.lang.RuntimeException: Exception while trying to locate proxy factory in JNDI, at key ProxyFactory/321phonic/SIPManagerBean/321phonic/SIPManagerBean/remote
at org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getProxyFactoryFromJNDI(ProxyObjectFactory.java:249) [:1.0.11]
at org.jboss.ejb3.proxy.impl.objectfactory.ProxyObjectFactory.getObjectInstance(ProxyObjectFactory.java:157) [:1.0.11]
at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:304) [:1.6.0_22]
at org.jnp.interfaces.NamingContext.getObjectInstance(NamingContext.java:1483) [:5.0.5.Final]
at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1500) [:5.0.5.Final]
... 144 more
Caused by: javax.naming.NameNotFoundException: ProxyFactory not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:771) [:5.0.5.Final]
at org.jnp.server.NamingServer.getBinding(NamingServer.java:779) [:5.0.5.Final]
at org.jnp.server.NamingServer.getObject(NamingServer.java:785) [:5.0.5.Final]
at org.jnp.server.NamingServer.lookup(NamingServer.java:396) [:5.0.5.Final]
at org.jnp.server.NamingServer.lookup(NamingServer.java:399) [:5.0.5.Final]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_22]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_22]
I suppouse it is because of the different versions of jbossclient-all.jar in both servers.
What is the preferred method of building a jbossclient-all.jar (in 5.1 it references lots of jars so I can't just copy it into the WEB-INF/lib of the war app in JBoss 6 instance) and deploy it into my client war withoud conflicts with own JBoss 6 client jars?
Thanks for any help,
Ignacio
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/588860#588860]
Start a new discussion in JNDI and Naming at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 4 months
