Service Locator implementaion for PetStore

PetStore use two service locator class, one for the web
http://java.sun.com/blueprints/code/jps131/src/com/sun/j2ee/blueprints/servicelocator/web/ServiceLocator.java.html
and another one for ejb
http://java.sun.com/blueprints/code/jps131/src/com/sun/j2ee/blueprints/servicelocator/ejb/ServiceLocator.java.html
as explanied on this topic
http://java.sun.com/blueprints/patterns/ServiceLocator.html
I wonder why they have made the Web-tier class is a singleton, and caches the objects it looks up, while the EJB-tier class is not a singleton, and does not cache?
Does any body have a clue
thanks

Hi,
This question was answered on the patterns interest list recently. The response is at
http://swjscmail1.java.sun.com/cgi-bin/wa?A2=ind0301&L=j2eepatterns-interest&P=R5864
hope that helps,
Sean

Similar Messages

Does location based services (LBS) work for international locations (outside the USA)?

Does location based services (LBS) work for international locations (outside the USA)? For example does it work in Canada, European countries etc. Any help is appreciated.

Yes, but possibly limited to coverage of Skyhook database..
Applications that use location services also use the data from Skyhook...
Skyhook is a service that records the MAC addresses of Cell Base stations/towers and wireless access points.
Google Maps vehicles records the wireless AP data at the same time they get street view images.
There was some controversy over this - but they effectively record the location and the MAC address of any AP they find as they drive round. This gets sent to a massive database at Skyhook and is used to either locate without GPS or enhance/aid the GPS information. It's also why the location is always the road outside!
If your location/MAC relationship has not been mapped by Skyhook, Google or others - then the good news is that you can add it - although it can take a month or two at least - to work. The reason is that it depends which database is being used by Skyhook's clients..
Add your Wireless Access Point (or Wireless Router) here: http://www.skyhookwireless.com/howitworks/submit_ap.php
The main website for Skyhook is here: http://www.skyhookwireless.com
Hope that helps...!

No 'Location' option for Adobe Partner Services in PSE 9 (Mac)

I'm trying to run some prints and photo books off through the Kodak Gallery option in Photoshop Elements 9 on my Mac, but it is sending me to the US Kodak Gallery website.
If I need to do this on my PC it is easy, I just change my 'Location' to be the UK in Preferences > Adobe Partner Services, but in the Mac Preferences there is no 'Location' option to change.
I've reinstalled a couple of times, but no joy. Is this just another thing that is missing in the Mac version of PSE9?
Thanks for any help on offer out there. Mike

Hi Mike,
On MAC, the location option is not present under Preferences->Adobe Partner services. Instead it is present directly under the preferences. It will be present at Preferences->Adobe Partner Services Location. Please tell if you are able to find this option.
-Saurabh

SMBLN filed blank in case of service Purchase order for MSEG

Hi expert
SMBLN (Number of Material Document) filed blank in case of service Purchase order for MSEG.
if i check for normal po i get my number for which i have doing reverse.
Case example
when i check in mseg for Mvt 106 Material Docu No , in the field SMBLN i get for the Material Docu No of 105 for normal PO.
when i check in mseg for Mvt 102 Material Docu No , in the field SMBLN i dont get for the Material Docu No of 105 for Servicel PO
Regard
Nabil
Edited by: sayednabil on Apr 11, 2011 11:50 AM

Hello andrewjkasten,
It's good to hear from you again, although I truly wish it were to share a more pleasant experience than when we previously conversed. It is always great to keep an eye on sales however you can so you don't miss them! I'm sorry to hear a technical issue may have caused your order to not reach our systems and missing out on a great sale price!
Using the information you registered with the forum, I've sadly been unable to locate your computer order. With that said, I would like to look further into this and am sending you a private message to gather the necessary information. I look forward to your correspondence!
Respectfully,
Tasha|Social Media Specialist | Best Buy® Corporate
Private Message

SERVICE LOCATOR ?? Is it really an interesting Design pattern??

Hi everybody,
i've a problem with the J2EE Design Pattern "Services locator" (it's a singleton).
It is said that by making use of a Service Locator we can :
- hide to the client the complexities of initial context creation, EJB home object lookup,and EJB objectre-creation.
- multiple clients can reuse the Service Locator object to reduce code complexity, provide a single point of control, and improve performance by providing a caching facility.
But i would like to understand at which side should that service locator object reside??!!??
If it is at server side then the clients need well an initial context in order to make a lookup on that object.
Conclusion :
the service locator doesn't hide the complexities of initial context!!
Furthermore the client has to perform a look-up on that service locator object!! The only advantage left is caching facility.
If it is at client side, each client needs his own services locator object
Conclusion :
multiple client don't reuse the same service locator. What's the advantage to be a singleton ???
There is certainly something that i don't understand so help me please!! Thanks.

Hi Yves,
But i would like to understand at which side should
that service locator object reside??!!??
If it is at client side, each client needs his own
services locator object
Conclusion :
multiple client don't reuse the same service locator.
What's the advantage to be a singleton ???The service locator resides on the client side and is implemented as
a singleton. Since it is possible that there could be multiple
class loaders/JVMs on the client side, and therefore, multiple
instances of the "singleton" service locator. This is typical
in a distributed environment (e.g. servlets/JSPs in a web-tier
cluster using service locator). Thus service locator is not
a truly "distributed singleton" object. But, the empahsis
is to design the service locator such that it does not hold
any state that needs to be replicated across multiple
instances across different JVMs as mentioned. Thus, there
is no need for multiple clients to use the "same" service locator,
but still the benefits of implementing this pattern is realized.
By making it a singleton, and keeping it from holding state
that needs to be replicated, we realize the benefits of this pattern.
You may also want to visit the J2EE Pattern interest list
and see these relevant discussions :
Topic: Service Locator and passivation
http://archives.java.sun.com/cgi-bin/wa?A2=ind0106&L=j2eepatterns-interest&F=&S=&P=1026
Topic: Caching EJBHome interfaces
http://archives.java.sun.com/cgi-bin/wa?A2=ind0106&L=j2eepatterns-interest&F=&S=&P=9226
Topic: Using Service Locator for Data Source caching
http://archives.java.sun.com/cgi-bin/wa?A1=ind0106&L=j2eepatterns-interest#31
hope this helps,
thanks,
-deepak

Using service Locator pattern to dynamically access remote EJBs

Hi All,
Please help to guide me how I can use a service locator to retrieve a remote object (residing on another application but on same domain) .
I do not want to use Dependency Injection since I want to dynamically discover them ( there are many implementations of same interface (POJO)). Each EJB implementation implements its own remote/local interface that extends this global POJO interface.
I have two J2ee-Applications on same domain. J2EE-Application 1 has an EJB module (EJB Module 1) that intends to access an EJB Module (EJB Module 2) in J2EE-Application 2. Following observations:
1. Dependency Injection fails if (include the EJB Module 2 jar in J2EE-Application 1). Reason App Server complains the EJB has been deployed (Deployment fails)
2. Dependency Injection works if (exclude the EJB Module 2 jar in J2EE-Application 1) and include the Remote Interface in EJB Module 1(J2EE-Application 1).Positive Observation (Deployment success and DI also success)
3.Using Service Locator to retrieve the remote object if (exclude the EJB Module 2 jar in J2EE-Application 1) and include the Remote Interface in EJB Module 1(J2EE-Application 1). Negative and Positive Observation.
Positive Observation: Using dependency injection I can still retrieve the Remote Object
Another Positive: The Service Locator remote lookup to another Bean in same Application but different EJB Module is successful.
Negative Observation:
The Service Locator lookup to this same remote object with Successful Dependency Injection fails (An Ejb in a different application).
Can't retrieve the Remote Object with Service Locator. Message from Server:.
NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial.
Thanks in advance

"I do not want to use Dependency Injection since I want to dynamically discover them ( there are many implementations of same interface (POJO))"
If you're calling ejbs from other ejbs or servlets, the same could probably be acomplished by using dependency injection (@EJB) in a number of instance variables typed with different remote/local interfaces or even with different beanName attributes (for when more than one bean implements the same managed interface in the same app - not sure how it works outside the same jee app...) , and dinamically selecting one of them; or encapsulating those injected variables into a stateless ejb as your service locator to make them accessible from POJOs too (which, due to concurrent acess, wouldn't work for statefull ejbs references...).
Anyway, using the jndi lookup service locator pattern seems ok in this case.
What doesn't seem ok, given the nature of the error for the negative observation - jndi context initialization - is that
Another Positive: The Service Locator remote lookup to another Bean in same Application but different EJB Module is successful.
Can you check your code and reconfirm that you're using the same context initialization code for both the positive and negative observations ?

How to call workflow approve service in loop for multiple documents.

i have created a serviceHandler for approving the document and i post the comma separated dIDs as a string from workflow approval template(custom template). And in serviceHandler program i pass the did for approving and only first document is approved and for other document its throwing error, Its showing error document revision is not a latest revision but document is having only one revision.
my code is: can anyone help me.
public void SendAllDocuments()
        throws DataException, ServiceException{
    try{
    String [] ContentDids;
    System.out.println("+++++++here we are the all SendAllDocuments++++++++++++++");
    String workflowIds = m_binder.getLocal("workflowIds");
    if(!workflowIds.isEmpty()){
         ContentDids = workflowIds.split("\\,");
    }else{
        throw new ServiceException("document are not selected from users, workflowIds"+workflowIds);
    int arrayLength = ContentDids.length;
    for(int iterator=0;iterator<=arrayLength-1;iterator++){
        SendDocumentToUserQueue(ContentDids[iterator]);
    }}catch(Exception e){ e.printStackTrace();}
    m_workspace.releaseConnection();
//DocMeta table varible which are coming from Internal assignment page
//xWF_SentFrom",xWorkflowStepAlias",xWF_SendTo",xPurposeForSubmission",xPurposeForRejection",xDocApproval",xWorkflowComments"
//xInternalAssignment",togroup",xWF_SendToSend",xWF_SendToSend12",xPurposeForSubmissionSend",xWF_SendToApprove",wfSendApproveComments"
//Revision table variable which can get from getRevisionsTableValueFromDid
// dDocName", dDocType",dRevLabel",dSecurityGroup",dDocAccount"
public void SendDocumentToUserQueue(String approvalId) throws DataException, ServiceException{
    try{
        DataResultSet resultset =getRevisionsTableValueFromDid(approvalId);
        String sendToName = m_binder.getLocal("sendToName");
        String sender="takuma";
    //String workflowComments = m_binder.getLocal("workflowComments");
    String workflowReason = m_binder.getLocal("workflowReason");
    m_binder.putLocal("IdcService", "WORKFLOW_Approve");
    m_binder.putLocal("idcToken", m_binder.getLocal("idcToken"));
    m_binder.putLocal("dID", approvalId);
    m_binder.putLocal("xWF_SendTo", sendToName);
    m_binder.putLocal("xPurposeForSubmission","108");
    m_binder.putLocal("xWF_SentFrom", sender);
    m_binder.putLocal("xWorkflowStepAlias", "");
    m_binder.putLocal("xPurposeForRejection", "");
    m_binder.putLocal("xDocApproval", "");
    m_binder.putLocal("xWorkflowComments", "");
    m_binder.putLocal("xInternalAssignment", "");
    m_binder.putLocal("xWF_SendToSend", "");
    m_binder.putLocal("dDocName", getData(resultset,"dDocName"));
    m_binder.putLocal("dDocType", getData(resultset,"dDocType"));
    m_binder.putLocal("dRevLabel", getData(resultset,"dRevLabel"));
    m_binder.putLocal("dSecurityGroup", getData(resultset,"dSecurityGroup"));
    m_binder.putLocal("dDocAccount", getData(resultset,"dDocAccount"));
    executeService(m_binder, sender);
}catch(Exception e){ e.printStackTrace();}
public DataResultSet getRevisionsTableValueFromDid(String documentId) throws DataException, ServiceException{
    DataResultSet drs = new DataResultSet();
    try{
        /*String sqlDocType="select dDocType from revisions where dId ='"+documentId+"'";
    ResultSet documentRset = getSystemWorkspace().createResultSetSQL(sqlDocType);
    //handle null pointer exception for DocumentValue
    String DocumentValue = ResultSetUtils.getValue(documentRset, "dDocType");*/
    String sql="select dDocName,dDocType,dRevLabel,dSecurityGroup,dDocAccount from Revisions where dId ='"+documentId+"'";
    ResultSet rset = getSystemWorkspace().createResultSetSQL(sql);
    if (rset == null || rset.isEmpty()) {
        SystemUtils
                .info("Resultset is null please check database query and Did ="+documentId);
    drs.copy(rset);
    catch(Exception e){
        System.out.println("in catch of getRevisionId Method");
        e.printStackTrace();}
    //handle null pointer exception for DocumentValue
    return drs;
public String getData(DataResultSet dataSet, String value) {
    String fieldValue = "";
    fieldValue = ResultSetUtils.getValue(dataSet, value);
    System.out.println(fieldValue+"value is null in getData Method=======");
    return fieldValue;
public UserData getFullUserData(String userName, ExecutionContext cxt,
        Workspace ws) throws DataException, ServiceException {
    if (ws == null)
        ws = getSystemWorkspace();
    UserData userData = UserStorage.retrieveUserDatabaseProfileDataFull(
            userName, ws, null, cxt, true, true);
    //ws.releaseConnection();
    return userData;
public Workspace getSystemWorkspace() {
    Workspace workspace = null;
    Provider wsProvider = Providers.getProvider("SystemDatabase");
    if (wsProvider != null)
        workspace = (Workspace) wsProvider.getProvider();
    return workspace;
public void executeService(DataBinder binder, String userName)
        throws DataException, ServiceException {
    // obtain a connection to the database
    Workspace workspace = getSystemWorkspace();
    // check for an IdcService value
    String cmd = binder.getLocal("IdcService");
    if (cmd == null)
        throw new DataException("!csIdcServiceMissing");
    // obtain the service definition
    ServiceData serviceData = ServiceManager.getFullService(cmd);
    if (serviceData == null)
        throw new DataException(LocaleUtils.encodeMessage(
                "!csNoServiceDefined", null, cmd));
    // create the service object for this service
    Service service = ServiceManager.createService(serviceData.m_classID,
            workspace, null, binder, serviceData);
    // obtain the full user data for this user
    UserData fullUserData = getFullUserData(userName, service, workspace);
    service.setUserData(fullUserData);
    // binder.m_environment.put("REMOTE_USER", userName);
    ServiceException error = null;
    try {
        // init the service to not send HTML back
        service.setSendFlags(true, true);
        // create all the ServiceHandlers and implementors
        service.initDelegatedObjects();
        // do a security check
        service.globalSecurityCheck();
        // prepare for the service
        service.preActions();
        // execute the service
        service.doActions();
        // doany cleanup
        service.postActions();
        // store any new personalization data
        service.updateSubjectInformation(true);
        service.updateTopicInformation(binder);
    } catch (ServiceException e) {
        varTrueFalse = false;
        error = e;
        SystemUtils.info("exception in second location=" + e);
        e.printStackTrace();
    } finally {
        // Remove all the temp files.
        service.cleanUp(true);
    // handle any error
    if (error != null) {
        error.printStackTrace();
        if (binder.getLocal("StatusCode") == null) {
            binder.putLocal("StatusCode", String.valueOf(error.m_errorCode));
            binder.putLocal("StatusMessage", error.getMessage());
        } else {
            throw new ServiceException(error.m_errorCode,
                    error.getMessage());

I guess it is caused by the fact that some of variables in the binder refer to the first workflow item. My bet would be dDocName.
Try to find out what's in the binder if you approve the second item from GUI and what's there when you do it from your program. That should give you enough info what you need to change.

Slow attachment upload with Exchange Web Services (Outlook 2011 for Mac?)

We're experiencing slow attachment upload with Exchange Web Services versus MAPI, OWA, and Outlook Anywhere. I'm not totally certain that it is Exchange Web Services or specifically Outlook 2011 for Mac. I attempted to test with the Mac Mail
App, but it makes it difficult to tell when the attachment has been uploaded and the file has been sent. Here's what we're seeing (10mb file):
MAPI / RPC/HTTPS / OWA: 10-15 seconds upload time
Exchange Web Services (Outlook 2011 for Mac): 60-90 seconds upload time
Thoughts? Any idea why we would see such a drastic difference in attachment upload time? Any way to prove definitively that it is Exchange Web Services vs. Outlook 2011 for Mac? We've tried it from multiple locations with multiple different machines,
and although the upload times vary (some locations have more bandwidth etc) the ratios remain similar.

Hi ,
Does all the user occurred the issue ?
If only special user, I recommend you do the following steps and test:
1.Remove and re-add the email account and check if this helps to resolve the issue.
To remove and add the email accounts:
Open Outlook > GO to Tools > Accounts > Click on "Minus" symbol to remove and "Plus" to add an Email account.
2.Creating a new user profile:
http://support.microsoft.com/kb/2439218/
3. If the issue persists, rebuild the data base and check the results:
http://support.microsoft.com/kb/2360509
You can also post it on Office for MAC forum to get special support about the difference between Outlook and Outlook for MAC.
http://www.microsoft.com/mac/support
Wendy Liu
TechNet Community Support

Can we implement "Service Locator" in Stateless Session Bean??

Hi,
My enterprise application is using Stateless Session Bean. To increase the performace , I think of implementing "service Locator" pattern so as to cache the EJBHome objects in order to avoid looking up Home object every time. I want to know whether this will work out in case of stateless session bean??
Thanks for ur help.

Hi,
The purpose of service locator is to abstract the lookup of the server side services like ejb and DSNs. It should be a normal java class but as such there is no such restriction. You can have a look at the service locator patter at the j2ee blue prints.
/Ashwani

Service Locator and session facade pattern

What are differences between Service Locator and session facade pattern?
For me it seems one and the same.
Please explain me in detail. Expecting kind help.
Thanks,
Rahul
Edited by: rahulb1 on Feb 26, 2008 5:07 PM

rdoekes wrote:
The ServiceLocator Pattern is a singleton which hold a map of used DataSources. The idea is that you perform a lookup once and use the cache afterwards. The session facade is just one DataSource lookup.huh? Those J2EE patterns are not really reduced to datasources and the SessionFacade has actually nothing to do with datasources.
Session Facade
It has Facade in it and a Facade is usually used to give a simple entrypoint by providing a standartized interface. The same is now with the Session Facade. You have a Session bean that represents a high-level business component that interacts and calls lower-level business components.
Imagine having client a accessing 5 business objects with the remote calls, which is not an efficient way (network latency) or accessing the SessionFace and the session face is doing all the work through local access.
Service Locator
As J2EE components are using JDNI to lookup for ejb interfaces,DataSources, JMS components, connections etc. isntead of writing all the lookup in many code piecess across the project, you write a service locator that gives you a centralized place to handle the lookup's. It's easier to maintain and to control such a setup.
As you can see there's quite a big difference ;-)
cya,
Nail

Service Locator and Performance?

We currently have an application with numerious EJBs. Obviously, this in turn involves
numerous JNDI look ups for these EJBs. Both the client (a web application) and
the EJBs run within the same JVM, however not as part of a singe EAR application
(the EJBs are deployed as standalone application modules). We do not have any
Service Locator (J2EE pattern) implemented. My question is, given this scenario,
will there be a performance enhancement if a Service locator is implemented to
cache JNDI look-ups? If so, Will this come into play if we deploy the app as an
EAR?
Thanks,
Krish

There are a lot of tools out there.
Here's what I've used:
On Windows/Linux, OptimizeIt and Jprobe are pretty common.
If you're using jrockit, try JRA
http://dev2dev.com/products/wljrockit81/analyzer.jsp
On HP-UX, I like HP's JMeter:
http://www.hpjmeter.com
-- Rob
Krish wrote:
Is there a Profiling tool that I could use to identify where most of the time is
being spent?
Thx,
Rob Woollen <[email protected]> wrote:
If your end goal is to improve performance, then I'd strongly encourage
you to spend some time tracking down where time is currently being spent.
In my experience, creating InitialContext objects can be expensive.
Lookups generally aren't that bad, but it's a reasonable approach to
cache both.
Basically, if you're spending a lot of time in JNDI lookups, then I'd
suggest doing the Service Locator pattern. If your time is being mainly
spent elsewhere, attack that first.
-- Rob
Krish wrote:
We currently have an application with numerious EJBs. Obviously, thisin turn involves
numerous JNDI look ups for these EJBs. Both the client (a web application)and
the EJBs run within the same JVM, however not as part of a singe EARapplication
(the EJBs are deployed as standalone application modules). We do nothave any
Service Locator (J2EE pattern) implemented. My question is, given thisscenario,
will there be a performance enhancement if a Service locator is implementedto
cache JNDI look-ups? If so, Will this come into play if we deploy theapp as an
EAR?
Thanks,
Krish

Using Service Locator in Struts app without ant eejb components

Hi
We are developing a Struts application witjout any EJB components.
But we may go for EJB in future.
Keeping that in mind we want to introduce a service locator between the action class and the business logic. So it may be easier to acomodate in future.
But how do i do that ? Can anyone help me in this?
Since all the Service locator example which i have seen is implemented using ejb
Please do help me in this
Thanks
Ottran

Controller (Action class) gets reference to Business Delegate (BD) and calls a particular business method.
The BD gets reference to Service Locator (from JNDI tree) to access a business service. The business sevice can be implemented using EJB, POJO, Web Service, legacy app, etc.
A UML diagram is available at
http://www.softwareleadership.org/docs/J2EEDesignPatterns.html
Click on Business Delegate to view diagram with Service Locator.

Service locator

OK - this may take some time.....
We have an application split across multple projects. We use XDoclet as a start point to generate EJB/Web deployment descriptors.
We do not want to annotate the EJB java source with @ejb-ref and @ejb-local-ref's because of potential future changes. In other words if a utility class were changed to use an EJB, then all EJB's that use that utility class need to have an ejb-ref or ejb-local-ref added to their deployment descriptor, which if you are using XDoclet means updating the EJB java source.
So, we use XDoclet to generate most of the deployment descriptor content, and take responsibility for working out what ejb-ref or ejb-local-refs are required for each EJB as part of our packaging step in our build. We do this by using BCEL to build up a cross-reference of the inter-relationships between classes, and identify which classes have strings that begin java:comp/env/ejb/. Starting at the implementation class of an EJB, we exhaust all classes that are used by the EJB, accumulating all the lookup strings along the way. This may seem like overkill, but it works.
OK, we're getting closer to the question.
It has been suggested that we can remove this step of the build process by enhancing our service locator. Since all of our lookups are routed through this locator, the proposal is to put the actual lookup for the required EJB inside a new stateless session bean that is invoked from the service locator. The cache of EJBHomes is still in the service locator, and the new session bean will implement a local interface only.
This means that effectively all of our EJBs except the new session bean only have to have an ejb-local-ref for the new session bean, and the new session bean simply has all ejb-ref/ejb-local-ref's required by the application.
So my question is, is this an acceptable suggestion? We are talking about returning EJBHome objects from another EJB's context for use in the requesting EJB's context. Can anyone think of a problem with this? Apparently this has been mocked up and seems to work. I just have a nagging reservation about going ahead with this.
Our ref names are consistent across all of our EJB's, so java:comp/env/ejb/Fred always results in the same JNDI name regardless of which EJB is used, and this would not change in the future.
We are targeting J2EE 1.4/J2SE1.4.2
Got there in the end....
Many thanks for any views on this.

cpallab wrote:
A service can be offered by objects, or objectCould you explain what that even means?

Service Locator Pattern

I have a question about the Service Locator Pattern. If The service locator caches the EJBHome references in a Hashmap and retreives them though a method, does that method need to be synchronized for Thread Safety?
If it has to be synchronized, doesnt it introduce performance bottle neck by letting only 1 thread access the method at any time?
Please see code snippet below...
Thanks,
Krish
public static synchronized EJBHome getHome(Class homeClass) throws NamingExeption {
EJBHome home = (EJBHome) this.homes.get(homeClass);
if(home == null) {
ctx = getInitialContext();
home = (EJBHome) PortableRemoteObject.narrow(ctx.lookup(homeClass.getName()),homeClass);
this.homes.put(homeClass,home);
return home;
}

Hi,
Take a look at the below thread on server side which discusses this issue in details.
http://www.theserverside.com/discussions/thread.tss?thread_id=14992
Anil

I am trying to hook up my Airport Express to my current network and AirPort Extreme but keep getting the same error message: "This version of AirPort Utility doesn't support this base station. Go to AirPort Service and Support for more information."

I am trying to hook up my Airport Express to my current network and AirPort Extreme but keep getting the same error message: "This version of AirPort Utility doesn’t support this base station. Go to AirPort Service and Support for more information." Any thoughts?

This sounds as if you have an older AirPort Express that is no longer supported by the newer Mavericks operating system.
To check and see if that might be the case, locate the model number on the side of the AirPort Express. It will start with an "A" followed by four numbers. Hard to see in the faint print.....so you may need reading glasses or a magnifying class to see the model number clearly.
Model numbers A1084 and A1088 of the AirPort Express are no longer supported by AirPort Utility in Mavericks.
You will need to use a Mac running Leopard, Snow Leopard, or a PC to be able to administer the older AirPort Express.

Service Locator implementaion for PetStore

Similar Messages

Maybe you are looking for