Develop Reference

Configuring Wildfly standalone "<remote-naming/>"

Looking for examples of how to configure a Wildfly server to be very simple standalone JNDI namespace server.
I would like to specify value pairs so that our external java applications can access and use the defined resources using JNDI API's.
From the Documentation it is clear that I have to use the XML tag.
Remote JNDI Configuration
The Naming subsystem configuration may be
used to (de)activate the remote JNDI interface, which allows clients
to lookup entries present in a remote WildFly instance.
Only entries within the java:jboss/exported context are accessible
over remote JNDI. In the subsystem's XML configuration, remote JNDI
access bindings are configured through the XML
element:
<remote-naming />
But what isn't clear is HOW to use it, I cant find any examples anywhere.
If I had the following object:
String: MyFirstProperty
How do Insert this into the <remote-naming /> tag so that Wildfly makes it available for me to retrieve?

Custom jndi name for ejb3.X with Jboss 7.1

I am migrating one application from weblogic to jboss7.1 and ejb2.0 to ejb3.X. The application is using jndi name for ejb lookup.
Could someone help me to find out how can i configure my custom jndi name with ejb3.0 and jboss 7.1.
I have read on internet that in Jboss 7.1 there is no concept of jndi-name. if it is true. could someone let me know how can i lookup this jndi name, getting registered by jboss for ejbs present in ejb-jar.xml
java:global/pirptfe/RRMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.RRMSessionFacadeHome
java:app/pirptfe/RRMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.RRMSessionFacadeHome
java:module/RRMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.RRMSessionFacadeHome
java:jboss/exported/pirptfe/RRMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.RRMSessionFacadeHome
java:global/pirptfe/RRMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.RRMSessionFacadeRemote
java:app/pirptfe/RRMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.RRMSessionFacadeRemote
java:module/RRMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.RRMSessionFacadeRemote
java:jboss/exported/pirptfe/RRMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.RRMSessionFacadeRemote

i got the answer of my question. in ejb3.X on jboss7.1 and above there is no concept of custom jndi. you have to call your ejb as below
ctx.lookup("java:global/pirptfe/RRMSessionFacadeEJB!com.bfm.app.pirptfe.heatmap.ejb.RRMSessionFacadeHome");

Corba NameService configuration in Websphere 8.5.5

As part of my application requirement, I have to configure a attribute called "ORBInitRef.NameService=corbaloc:iiop:ABCDE012:14888/NameService" in Websphere 8.5.5. Earlier i have used Jboss for my applciation deployment but now have to use WAS. In, WAS where should i have to configure this attribute in admin console? Is there any way to do it through orb.properties file in WAS root folder. Please let me know to approach??

Please follow the below steps to configurable Corba Name service in WAS 8.5.5 in admin console.
--> Environment --> Name Space Bindings --> New --> Provide your corba details here.
Example:
1) corba URL : corbaloc:iiop:ABCDE012:14888/NameService
2) provide Lookup name. using this, u will get a RootContext by lookup like JNDI.
Code Example :
InitialContext context = new InitialContext();
org.omg.CosNaming.NamingContext rootContext=(NamingContext)context.lookup("testing");
using the rootContext, you can fetch the server stubs and preform the operation required.

Optional JNDI Binding For Websphere Web Application

I would like to have optionally supplied information available to my webapp when deployed to Websphere (we are using 8.5) via the application's JNDI context.
I know that I can put a resource-ref or resource-env-ref in my web.xml but when I do that WAS will require me to supply a binding for it and deployment time.
My application will look in JNDI for certain values and adjust its behavior if found, but will function fine with default behaviour if it does not find values in JNDI. How, in WAS, do I supply a binding (just for a string or a URL) for my webapp without declaring a dependency on it in a resource-ref or resource-env-ref in my web.xml.
I know how to do this in Tomcat, I just put a Environment entry in the context.xml, like this:
<Environment
name="com.myorg.config"
value="http://localhost:8081/suff"
type="java.lang.String"/>

You can use an #Resource String lookupName; to accomplish the same in a portable manner. You will be prompted for a value at deployment time, but you can specify nothing, which will cause no value to be injected.

Apache Jackrabbit - Override Jackrabbit configuration parameters when deployed in Glassfish v3

I feel like an idiot, but where/how do I override the Jackrabbit configuration parameters when deployed in Glassfish v3? I've tried setting rep.home in the Glassfish Admin -> Enterprise Server -> System Properties panel, but it doesn't seem to have any affect.
Do I have the property name correct?
Is this not the right place to do
this?
BTW - I'm using the Jackrabbit release bundled with the Sling API.

The Jackrabbit Configuration Parameters indicated by your link are automatically set by the Jackrabbit Repository implementation when reading the repository.xml configuration file.
What you can do to relocate the Jackrabbit Repository inside Sling is either set the "sling.repository.home" framework property (of the OSGi framework into which Sling is deployed).
Alternatively you can edit the Repository Server configuration in the Web Console Configuration Manager page. Select the configuration labeled something like org.apache.sling.jcr.jackrabbit.server.SlingServerRepository.XXX where "xxx" looks like UUID string. In that configuration change the Repository Home path. Please note, though, that this will not move your existing repository directory but just tell Sling to use a different location.