WSSIG - Call for panel members

The Web Services Special Interest Group (WSSIG) will be meeting on September 18, 2005 during the Oracle OpenWorld 2005 at the Moscone Center, San Francisco, California.
The highlight of our meeting is an educative discussion on Web Services by
a panel of industry experts who will share their knowledge, best practices, tips and tricks. Oracle Corporation will be represented on the panel as well to discuss future directions, Fusion Middleware and Project Fusion.
If you have considerable experience with Web Services and interested in
filling the two remaining slots on this panel, please email [email protected] latest by September 2, 2005. Please include a brief bio, highlighting your Web Services expertise and your contact phonenumber.
We encourage everyone who is attending OpenWorld 2005 to join us at 3:25PM
in Room 3005 to attend this exciting session to learn about Web Services,
how to leverage them in your business today and get your questions
answered.
Please visit our website (http://wssig.oaug.org) for more details and information on how to join the WSSIG.
Look forward to seeing you in San Francisco!
WSSIG Board of Directors

the problem is the null layout.
the background paints itself on top of buttons and the such.
i had the same problem and fix it using the layeredPane, in which you set a certain depth for each component.
the background can then be set at level zero and the butrtons at a higher depth ... then the repain does not cover the buttons.
to learn how to use the layered panes go to ..
http://java.sun.com/docs/books/tutorial/uiswing/components/layeredpane.html

Similar Messages

Multiple back bean calls for rendered panels

Hello,
We have experienced some strange behaviours, when rendering a panel based on some back bean paramater the backing bean method is called multiple times. It seems that the backing bean is called for each child element is the panel.
For instance in the following example the backing bean will be called 6 times.
<t:div id="test" rendered="#{! empty UCB.attribut}" >
     <t:outputText value="text1" />
     <t:outputText value="text2" />
     <t:outputText value="text3" />
     <t:outputText value="text4" />
     <t:outputText value="text5" />
</t:div>Is this a configuration issue or just how jsf is implemented?
//Chris

Called sequentially (from my original post):
wsCodeList["GetTupleList"].arguments.TupleName = "BUSTYPE";
var call:Object = wsCodeList["GetTupleList"].send();
call.destination = "busType";
wsCodeList["GetTupleList"].arguments.TupleName = "ENTTYPE";
call = wsCodeList["GetTupleList"].send();
call.destination = "entityType";
The docs seem to say this is allow and example found online
do similar, except the arguments are passed as a parameter to send.
This doesn't work for me though. The web service I'm using will
only take the arguments using the arguments object.

IPTComm 2010 Call for Papers: Deadline Extended

CALL FOR PAPERS: DEADLINE EXTENDED
4th ACM Conference on Principles, Systems and Applications of IP Telecommunications
IPTComm 2010
http://www.iptcomm.org
August 2-3, 2010
Leibniz Supercomputing Center
Munich, Germany
IMPORTANT DATES
================
Paper registration: Midnight, March 5, 2010.
Paper submission: Midnight March 19th, 2010 (Firm deadline).
Notification of acceptance: May 21st, 2010.
Final camera-ready submission: June 30th, 2010.
Conference dates: August 2-3, 2010.
The paper submission deadline has been extended to March 19, 2010.
However, authors are required to register with EDAS and submit
their paper abstract by the original deadline of Midnight March 5,
2010.
The IP communications domain has matured beyond providing VoIP only
services. Universities, enterprises, businesses and individual
consumers routinely use VoIP. The focus of IP communications is now on
the operations, management, administration and provisioning aspects of
large-scale, reliable and secure communication systems. To this extent,
the research and standardization work now includes log file analysis,
session tracing across proxy meshes and overload control. As IP
communications grapples with these issues, newer technologies in the
form of cloud-based IP communication systems; peer-to-peer VoIP
networks; use of IP communications in virtual worlds; social
networks and IP communications are starting to assert a strong
presence in the IP communications domain.
The aim of the IPTComm conference is to serve as a platform for
researchers from academia, research labs, industry and government to
share their ideas, views, results and experiences in the field of
IP-based telecommunication. IPTComm will include presentations of
theoretical and experimental achievements, innovative systems,
prototyping efforts, case studies, and advancements in technology.
We invite authors to submit papers in the following and related areas:
New services and service models
* Over-the-top services.
* Social networking and IP communications.
* IP telecommunications in virtual worlds.
* Compositional services and model checking.
* Cloud-based IP communications infrastructure.
* Rapid application development frameworks.
* APIs and enablers for IP communication services.
* Browser-based IP communication services.
* Context-aware communication services.
* IMS and NGN services.
Management and Resilience
* Advantages and disadvantages of IP communications as a P2P
application.
* Advances in P2P overlays for IP communications systems.
* Management of IP communications systems and networks.
* Overload management schemes for IP communications.
* Log files and log file analysis for IP communication systems.
* Scalability of large-scale IP communication systems.
* Traffic and QoS measurement of VoIP traffic.
* Self-tuning and self-monitoring IP communications systems.
* Service discovery.
* Energy consumption and energy management in IP communication
systems.
* Incentives in P2P IP communication systems.
* Resilience in P2P IP communication system.
Security
* Identity management for IP communications systems.
* Anonymity and privacy in IP communications.
* Forensics and diagnostics in IP communication systems.
* Techniques to detect, mitigate and prevent SPIT, phreaking
and vishing.
* Denial of service detection and prevention.
Mobile IP Communications
* Mobile IP communication services.
* Mobility in cloud-based IP communications infrastructure.
* Mobile P2P IP communication systems.
Miscellaneous
* The role of IP communications in the power grid.
* Open source development in IP communications.
* Research issues in vertical IP communication markets (e.g.,
privacy in the medical field, location in logistical
field, etc.)
* Regulatory issues in IP communications.
AUTHOR INFORMATION
==================
Papers submission is handled by EDAS (http://edas.info/N8459).
IPTComm solicits full papers up to 12 pages in length, in two-column
ACM conference format
(see http://www.acm.org/sigs/publications/proceedings-templates). All
submissions must describe original research, not published nor
currently under review for another conference or journal. The program
committee will referee all papers, and accepted papers will be
published in the conference proceedings. Papers will also be published in
the ACM Digital Library.
In 2010, IPTComm will be accepting short papers of at least 5 pages and
no more than 6 pages. The aim of the short paper category is to help
maintain a published record of work carried out as well as facilitate
future affiliations and foster collaborative work. Short papers are
subject to the same rigorous review process as full papers and follow
the same submission process, schedule and expectation of presentation as
the full papers.
IMPORTANT DATES
================
Paper registration: Midnight, March 5, 2010.
Paper submission: Midnight March 19th, 2010 (Firm deadline).
Notification of acceptance: May 21st, 2010.
Final camera-ready submission: June 30th, 2010.
Conference dates: August 2-3, 2010.
Conference Location: Leibniz Supercomputing Center, Munich, Germany.
CONFERENCE CO-CHAIRS
====================
Georg Carle (Technical University of Munich)
Helmut Reiser (Leibniz Supercomputing Center)
TPC CO-CHAIRS
=============
Gonzalo Camarillo (Ericsson Research)
Vijay K. Gurbani (Bell Laboratories/Alcatel-Lucent)
DEMONSTRATION AND INDUSTRY TALKS CO-CHAIRS
==========================================
Carol Davids (Illinois Institute of Technology)
Saverio Niccolini (NEC Laboratories Europe)
PUBLICITY CHAIR
===============
Gregory Bond (AT&T Research)
Steering Committee
==================
Gregory Bond (AT&T Research)
Saverio Niccolini (NEC Laboratories Europe)
Henning Schulzrinne (Columbia University)
Dorgham Sisalem (Tekelec)
Radu State (University of Luxembourg)
TPC MEMBERS
===========
John Buford Avaya Labs Research
Eric Chen NTT Corporation
Eric Cheung AT&T Labs - Research
Tasos Dagiuklas Technological Educational Institute of Mesolonghi
Carol Davids Illinois Institute of Technology
Ali Fessi Technical University of Munich
Rosario Garroppo University of Pisa
Aniruddha Gokhale Vanderbilt University
Swapna Gokhale University of Connecticut
Carmen Guerrero University Carlos III of Madrid
Christian Hoene University of Tubingen
Alan Jeffrey Bell Laboratories, Alcatel-Lucent
Cullen Jennings Cisco
Salvatore Loreto Ericsson
Jouni Maenpaa Ericsson
Enrico Marocco Telecom Italia
Joerg Ott Helsinki University of Technology
Victor Pascual Avila Acme Packets
Joachim Posegga University of Passau
Anand Prasad NEC Corporation
Yacine Rebahi Fraunhofer Institut Fokus, Berlin
Ivica Rimac Bell Laboratories, Alcatel-Lucent
Ronaldo Salles Military Institute of Engineering (Brazil)
Stefano Salsano University of Rome "Tor Vergata"
Jan Seedorf NEC Europe Ltd.
Jose Solar Technical University of Denmark
Ivan Vidal University Carlos III of Madrid
Xiaotao Wu Avaya Labs Research
Pamela Zave AT&T Laboratories

Reminder: Our call for papers is closing on Monday 27th July. Be sure to send your abstracts to [[email protected]]
We also have a Twitter account and will be posting updates via that. Se sure to follow: aus_ora_spatial
Ross.

IPTComm 2010: Call for Papers

****** NOTE: Submissions due on Mar 5, 2010 *******
IPTCOMM 2010
============
The Fourth Conference on Principles, Systems and Applications of
IP Telecommunications
August 2 and 3, 2010
Leibniz Supercomputing Center
Munich, Germany
http://iptcomm.org
The IP communications domain has matured beyond providing VoIP only
services. Universities, enterprises, businesses and individual
consumers routinely use VoIP. The focus of IP communications is now on
the operations, management, administration and provisioning aspects of
large-scale, reliable and secure communication systems. To this extent,
the research and standardization work now includes log file analysis,
session tracing across proxy meshes and overload control. As IP
communications grapples with these issues, newer technologies in the
form of cloud-based IP communication systems; peer-to-peer VoIP
networks; use of IP communications in virtual worlds; social
networks and IP communications are starting to assert a strong
presence in the IP communications domain.
The aim of the IPTComm conference is to serve as a platform for
researchers from academia, research labs, industry and government to
share their ideas, views, results and experiences in the field of
IP-based telecommunication. IPTComm will include presentations of
theoretical and experimental achievements, innovative systems,
prototyping efforts, case studies, and advancements in technology.
We invite authors to submit papers in the following and related areas:
New services and service models
* Over-the-top services.
* Social networking and IP communications.
* IP telecommunications in virtual worlds.
* Compositional services and model checking.
* Cloud-based IP communications infrastructure.
* Rapid application development frameworks.
* APIs and enablers for IP communication services.
* Browser-based IP communication services.
* Context-aware communication services.
* IMS and NGN services.
Management and Resilience
* Advantages and disadvantages of IP communications as a P2P
application.
* Advances in P2P overlays for IP communications systems.
* Management of IP communications systems and networks.
* Overload management schemes for IP communications.
* Log files and log file analysis for IP communication systems.
* Scalability of large-scale IP communication systems.
* Traffic and QoS measurement of VoIP traffic.
* Self-tuning and self-monitoring IP communications systems.
* Service discovery.
* Energy consumption and energy management in IP communication
systems.
* Incentives in P2P IP communication systems.
* Resilience in P2P IP communication system.
Security
* Identity management for IP communications systems.
* Anonymity and privacy in IP communications.
* Forensics and diagnostics in IP communication systems.
* Techniques to detect, mitigate and prevent SPIT, phreaking
and vishing.
* Denial of service detection and prevention.
Mobile IP Communications
* Mobile IP communication services.
* Mobility in cloud-based IP communications infrastructure.
* Mobile P2P IP communication systems.
Miscellaneous
* The role of IP communications in the power grid.
* Open source development in IP communications.
* Research issues in vertical IP communication markets (e.g.,
privacy in the medical field, location in logistical
field, etc.)
* Regulatory issues in IP communications.
AUTHOR INFORMATION
==================
Papers submission is handled by EDAS (http://edas.info/N8459).
IPTComm solicits full papers up to 12 pages in length, in two-column
ACM conference format
(see http://www.acm.org/sigs/publications/proceedings-templates). All
submissions must describe original research, not published nor
currently under review for another conference or journal. The program
committee will referee all papers, and accepted papers will be
published in the conference proceedings. Pending cooperation agreements,
papers will also be published in the ACM Digital Library.
In 2010, IPTComm will be accepting short papers of at least 5 pages and
no more than 6 pages. The aim of the short paper category is to help
maintain a published record of work carried out as well as facilitate
future affiliations and foster collaborative work. Short papers are
subject to the same rigorous review process as full papers and follow
the same submission process, schedule and expectation of presentation as
the full papers.
IMPORTANT DATES
================
Paper submission: Midnight March 5th, 2010.
Notification of acceptance: May 21st, 2010.
Final camera-ready submission: June 30th, 2010.
Conference dates: August 2-3, 2010.
Conference Location: Leibniz Supercomputing Center, Munich, Germany.
CONFERENCE CO-CHAIRS
====================
Georg Carle (Technical University of Munich)
Helmut Reiser (Leibniz Supercomputing Center)
TPC CO-CHAIRS
=============
Gonzalo Camarillo (Ericsson Research)
Vijay K. Gurbani (Bell Laboratories/Alcatel-Lucent)
DEMONSTRATION AND INDUSTRY TALKS CO-CHAIRS
==========================================
Carol Davids (Illinois Institute of Technology)
Saverio Niccolini (NEC Laboratories Europe)
PUBLICITY CHAIR
===============
Gregory Bond (AT&T Research)
Steering Committee
==================
Gregory Bond (AT&T Research)
Saverio Niccolini (NEC Laboratories Europe)
Henning Schulzrinne (Columbia University)
Dorgham Sisalem (Tekelec)
Radu State (University of Luxembourg)
TPC MEMBERS
===========
John Buford Avaya Labs Research
Eric Chen NTT Corporation
Eric Cheung AT&T Labs - Research
Tasos Dagiuklas Technological Educational Institute of Mesolonghi
Carol Davids Illinois Institute of Technology
Ali Fessi Technical University of Munich
Rosario Garroppo University of Pisa
Aniruddha Gokhale Vanderbilt University
Swapna Gokhale University of Connecticut
Carmen Guerrero University Carlos III of Madrid
Christian Hoene University of Tubingen
Alan Jeffrey Bell Laboratories, Alcatel-Lucent
Cullen Jennings Cisco
Salvatore Loreto Ericsson
Jouni Maenpaa Ericsson
Enrico Marocco Telecom Italia
Joerg Ott Helsinki University of Technology
Victor Pascual Avila Acme Packets
Joachim Posegga University of Passau
Anand Prasad NEC Corporation
Yacine Rebahi Fraunhofer Institut Fokus, Berlin
Ivica Rimac Bell Laboratories, Alcatel-Lucent
Ronaldo Salles Military Institute of Engineering (Brazil)
Stefano Salsano University of Rome "Tor Vergata"
Jan Seedorf NEC Europe Ltd.
Jose Solar Technical University of Denmark
Ivan Vidal University Carlos III of Madrid
Xiaotao Wu Avaya Labs Research
Pamela Zave AT&T Laboratories

Reminder: Our call for papers is closing on Monday 27th July. Be sure to send your abstracts to [[email protected]]
We also have a Twitter account and will be posting updates via that. Se sure to follow: aus_ora_spatial
Ross.

Call for participation: OASIS Enterprise Key Management Infrastructure TC

We would welcome your participation in this process. Thank you.
Arshad Noor
StrongAuth, Inc.
To: OASIS members & interested parties
A new OASIS technical committee is being formed. The OASIS Enterprise Key
Management Infrastructure (EKMI) Technical Committee has been proposed by the
members of OASIS listed below. The proposal, below, meets the requirements of
the OASIS TC Process [a]. The TC name, statement of purpose, scope, list of
deliverables, audience, and language specified in the proposal will constitute
the TC's official charter. Submissions of technology for consideration by the
TC, and the beginning of technical discussions, may occur no sooner than the
TC's first meeting.
This TC will operate under our 2005 IPR Policy. The eligibility
requirements for becoming a participant in the TC at the first meeting (see
details below) are that:
(a) you must be an employee of an OASIS member organization or an individual
member of OASIS;
(b) the OASIS member must sign the OASIS membership agreement [c];
(c) you must notify the TC chair of your intent to participate at least 15
days prior to the first meeting, which members may do by using the "Join this
TC" button on the TC's public page at [d]; and
(d) you must attend the first meeting of the TC, at the time and date fixed
below.
Of course, participants also may join the TC at a later time. OASIS and the TC
welcomes all interested parties.
Non-OASIS members who wish to participate may contact us about joining OASIS
[c]. In addition, the public may access the information resources maintained for
each TC: a mail list archive, document repository and public comments facility,
which will be linked from the TC's public home page at [d].
Please feel free to forward this announcement to any other appropriate lists.
OASIS is an open standards organization; we encourage your feedback.
Regards,
Mary
Mary P McRae
Manager of TC Administration, OASIS
email: mary.mcrae(AT)oasis-open.org
web: www.oasis-open.org
a) http://www.oasis-open.org/committees/process.php
b) http://www.oasis-open.org/who/intellectualproperty.php
c) See http://www.oasis-open.org/join/
d) http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ekmi
CALL FOR PARTICIPATION
OASIS Enterprise Key Management Infrastructure (EKMI) TC
Name
OASIS Enterprise Key Management Infrastructure (EKMI) TC
Statement of Purpose
Public Key Infrastructure (PKI) technology has been around for more than a
decade, and many companies have adopted it to solve specific problems in the
area of public-key cryptography. Public-key cryptography has been embedded in
some of the most popular tools -- web clients and servers, VPN clients and
servers, mail user agents, office productivity tools and many industry-specific
applications -- and underlies many mission-critical environments today.
Additionally, there are many commercial and open-source implementations of PKI
software products available in the market today. However, many companies across
the world have recognized that PKI by itself, is not a solution.
There is also the perception that most standards in PKI have already been
established by ISO and the PKIX (IETF), and most companies are in
operations-mode with their PKIs -- just using it, and adopting it to other
business uses within their organizations. Consequently, there is not much left
to architect and design in the PKI community.
Simultaneously, there is a new interest on the part of many companies in the
management of symmetric keys used for encrypting sensitive data in their
computing infrastructure. While symmetric keys have been traditionally managed
by applications doing their own encryption and decryption, there is no
architecture or protocol that provides for symmetric key management services
across applications, operating systems, databases, etc. While there are many
industry standards around protocols for the life-cycle management of asymmetric
(or public/private) keys -- PKCS10, PKCS7, CRMF, CMS, etc. -- however, there is
no standard that describes how applications may request similar life-cycle
services for symmetric keys, from a server and how public-key cryptography may
be used to provide such services.
Key management needs to be addressed by enterprises in its entirety -- for both
symmetric and asymmetric keys. While each type of technology will require
specific protocols, controls and management disciplines, there is sufficient
common ground in the discipline justifying the approach to look at
key-management as a whole, rather than in parts. Therefore, this TC will
address the following:
Scope
A) The TC will create use-case(s) that describe how and where
the protocols it intends to create, will be used;
B) The TC will define symmetric key management protocols,
including those for:
1. Requesting a new or existing symmetric key from a server;
2. Requesting policy information from a server related to caching of keys on the
client;
3. Sending a symmetric key to a requestor, based on a request;
4. Sending policy information to a requestor, based on a request;
5. Other protocol pairs as deemed necessary.
C) To ensure cross-implementation interoperability, the TC will create a test
suite (as described under 'Deliverables' below) that will allow different
implementations of this protocol to be certified against the OASIS standard
(when ratified);
D) The TC will provide guidance on how a symmetric key-management infrastructure
may be secured using asymmetric keys, using secure and generally accepted
practices;
E) Where appropriate, and in conjunction with other standards organizations that
focus on disciplines outside the purview of OASIS, the TC will provide input on
how such enterprise key-management infrastructures may be managed, operated and
audited;
F) The TC may conduct other activities that educate users about, and promote,
securing sensitive data with appropriate cryptography, and the use of proper
key-management techniques and disciplines to ensure appropriate protection of
the infrastructure.
List of Deliverables
1. XSchema Definitions (XSD) of the request and response protocols (by August
2007) 2. A Test Suite of conformance clauses and sample transmitted keys and
content that allows for clients and servers to be tested for conformance to the
defined protocol (by December 2007)
3. Documentation that explains the communication protocol (by August 2007)
4. Documentation that provides guidelines for how an EKMI may be built,
operated, secured and audited (by December 2007)
5. Resources that promote enterprise-level key-management: white papers,
seminars, samples, and information for developer and public use. (beginning
August 2007, continuing at least through 2008)
Anticipated Audiences:
Any company or organization that has a need for managing cryptographic keys
across applications, databases, operating systems and devices, yet desires
centralized policy-driven management of all cryptographic keys in the
enterprise. Retail, health-care, government, education, finance - every industry
has a need to protect the confidentiality of sensitive data. The TC's
deliverables will provide an industry standard for protecting sensitive
information across these, and other, industries.
Security services vendors and integrators should be able to fulfill their use
cases with the TC's key management methodologies.
Members of the OASIS PKI TC should be very interested in this new TC, since the
goals of this TC potentially may fulfill some of the goals in the charter of the
PKI TC.
Language:
English
IPR Policy:
Royalty Free on Limited Terms under the OASIS IPR Policy
Additional Non-normative information regarding the start-up of the TC:
a. Identification of similar or applicable work:
The proposers are unaware of any similar work being carried on in this exact
area. However, this TC intends to leverage the products of, and seek liaison
with, a number of other existing projects that may interoperate with or provide
functionality to the EKMI TC's planned outputs, including:
OASIS Web Services Security TC
OASIS Web Services Trust TC
W3C XMLSignature and XMLEncryption protocols and working group
OASIS Digital Signature Services TC
OASIS Public Key Infrastructure TC
OASIS XACML TC (and other methods for providing granular access-control
permissions that may be consumed or enforced by symmetic key management)
b. Anticipated contributions:
StrongAuth, Inc. anticipates providing a draft proposal for the EKMI protocol,
at the inception of the TC. The current draft can be viewed at:
http://www.strongkey.org/resources/documentation/misc/skcl-sks-protocol.html
and a working implementation of this protocol is available at:
http://sourceforge.net/projects/strongkey for interested parties.
c. Proposed working title and acronym for specification:
Symmetric Key Services Markup Language (SKSML), subject to TC's approval or
change.
d. Date, time, and location of the first meeting:
First meeting will be by teleconference at:
Date: January 16, 2007
Time: 10 AM PST, 1PM EST
Call in details: to be posted to TC list
StrongAuth has agreed to host this meeting.
e. Projected meeting schedule:
Subject to TC's approval, we anticipate monthly telephone meetings for the first
year. First version of the protocol to be voted on by Summer 2007. StrongAuth is
willing to assist by arranging for the teleconferences; we anticipate using
readily available free teleconference services.
f. Names, electronic mail addresses, of supporters:
Ken Adler, ken(AT)adler.net
June Leung,June.Leung(AT)FundServ.com
John Messing, jmessing(AT)law-on-line.com
Arshad Noor, arshad.noor(AT)strongauth.com
Davi Ottenheimer, davi(AT)poetry.org
Ann Terwilliger, aterwil(AT)isa.com
g. TC Convener:
Arshad Noor, arshad.noor(AT)strongauth.com

Hi Bilge,
did you put your text in a blender before sending it?
I understood everything works fine except the miscellaneous menu item in the configuration tab of ERM?
Have you already tried to clear all browser cache, close all browsers and try it again?
Best,
Frank

[Call for Speakers & Sponsors] March 4th, 2015 - ASUG Ontario

[Call for Speakers & Sponsors] March 4th, 2015 - ASUG Ontario Chapter Meeting
Follow our Events on Twitter - @ASUG_Ontario
    SAP Customer Keynotes by Canada Post and Cirque Du Soliel.
    Over 150 Attendees from the SAP Ecosystem.
    SAP Mobility Panel
    Real-World Customer Case Studies.
    Break-Out Track Session.
    Sponsor Showcase Area
Limited slots in the SPONSOR SHOWCASE - Reply ASAP via Survey

You'd really have to get back in touch with Support and give them your reference number, so they can look into this for you. If you don't have any luck getting a response, post up your reference number and we'll see what we can do.
Cat

IPTComm 2007 Call for Participation

Please find enclosed the Call for Participation for a new conference devoted to IP telecommunications to be held in New York, July 2007. You are encouraged to circulate this message to interested colleagues, mailing lists, forums and blogs.
Greg Bond
IPTComm 2007 Co-Chair
==============================================================
Call For Participation
IPTComm 2007
PRINCIPLES, SYSTEMS AND APPLICATIONS OF IP TELECOMMUNICATIONS
19, 20 July 2007
Columbia University
NY, USA
(in cooperation with ACM SIGCOMM)
http://iptcomm.org
Registration for IPTComm 2007 is now open! Be sure to register soon in order to qualify for the early registration discount. The conference program has been finalized. Some highlights are: a stimulating technical program, Jeff Pulver as the keynote speaker, Jonathan Rosenberg opening Day Two, a panel discussion with broad representation from industry and academia, two tutorials, and a demos program. We are now in the process of organizing some entertaining social events. Details will be available soon. Hope to see you in New York in July!

Hi John,
Is I said in the mail I sent you, I'd be interested in having a go at this. We use TRAC in house and it would be nice to have a connector up and running for TPC.
I'm hoping others would be willing to join in as well.
Thanks
Femi

C++ STL library error: Non-const function ... called for const object

Hello,
I'm using the Forte Developer 6 Update 2 C++ compiler and standard library on Solaris 9 SPARC. I've installed the recommended patch set for C++ (both the workshop and platform patches).
In my code, I have a STL set with some elements that I want to modify, say:
typedef set<SomeClass> MySet;
typedef MySet::iterator MySetIter;
I'm trying to look for an element, then update some of its fields:
MySet theSet;
SomeClass sci;
MySetIter it = theSet.find(sci);
if (it != theSet.end()) {
it->update_some_fields();
The above code fails with the following error (some details scrapped):
Error: Non-const function SomeClass::update_some_fields() called for const object
Which is weird, since set::find() seems to return a set<...>::iterator, not a set<...>::const_iterator!
If I try a workaround, like this:
if (it != theSet.end()) {
SomeClass &tmp = *it;
tmp->update_some_fields();
I get this other error:
Initializing SomeClass& requires an lvalue.
Is there some way to convince the Forte compiler to work around this situation (most likely a compiler / library bug)?

This was fixed, too, by replacing the set with a map. It seems that the issue was related to the fact that any change made to a set member is supposed to not modify the elements that make up the key (the elements that are used in the comparison function to determine the ordering). The Windows (dinkumware) implementation of the STL allows set modifications, though I don't know how they check that the key fields are not modified. The Solaris implementation (and the GNU implementation, too) disallows any modifications made to set members. At least that's what a person more knowledgeable of C++ in our office found out. So I don't think the issue was related to template constructors or any unimplemented features after all.

Unable to open desktop file /usr/share/applications/redhat-email.desktop for panel launcher: No such file or directory

Dear Experts,
Please note that I am facing a chllenge while confiuguring the VNCServer on the local test Server. The Local Test Sver OS Version is Redhat Enterprise Linux Server
Release 5.5 32-bit. Please review the following error message and advise me on how to fix the vncserver issue.
[root@test .vnc]# cat xstartup
#!/bin/sh
# Uncomment the following two lines for normal desktop:
unset SESSION_MANAGER
exec /etc/X11/xinit/xinitrc
gnome-session &
[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &
#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
twm &
[root@test .vnc]# cat /etc/sysconfig/vncservers
# The VNCSERVERS variable is a list of display:user pairs.
# Uncomment the lines below to start a VNC server on display :2
# as my 'myusername' (adjust this to your own). You will also
# need to set a VNC password; run 'man vncpasswd' to see how
# to do that.
# DO NOT RUN THIS SERVICE if your local area network is
# untrusted! For a secure way of using VNC, see
# <URL:http://www.uk.research.att.com/archive/vnc/sshvnc.html>.
# Use "-nolisten tcp" to prevent X connections to your VNC server via TCP.
# Use "-nohttpd" to prevent web-based VNC clients connecting.
# Use "-localhost" to prevent remote VNC clients connecting except when
# doing so through a secure tunnel. See the "-via" option in the
# `man vncviewer' manual page.
# VNCSERVERS="2:myusername"
# VNCSERVERARGS[2]="-geometry 800x600 -nolisten tcp -nohttpd -localhost"
VNCSERVERS="1:oracle"
[root@test .vnc]# ls
passwd test.oracle.co.zm:1.pid test.oracle.co.zm:3.log test.oracle.co.zm:5.pid test.oracle.co.zm:6.pid
test.oracle.co.zm:1.log test.oracle.co.zm:2.log test.oracle.co.zm:5.log test.oracle.co.zm:6.log xstartup
[root@test .vnc]# more test.oracle.co.zm:1.log
Xvnc Free Edition 4.1.2
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
Underlying X server release 70101000, The X.Org Foundation
Tue Mar 11 11:18:37 2014
vncext:      VNC extension running!
vncext:      Listening for VNC connections on port 5901
vncext:      Listening for HTTP connections on port 5801
vncext:      created VNC server for screen 0
Could not init font path element unix/:7100, removing from list!
localuser:root being added to access control list
No profile for user 'root' found
SESSION_MANAGER=local/test.oracle.co.zm:/tmp/.ICE-unix/13603
Window manager warning: Log level 32: could not find XKB extension.
** (eggcups:13671): WARNING **: IPP request failed with status 1030
** (eggcups:13671): WARNING **: IPP request failed with status 1030
** (nm-applet:13697): WARNING **: No connections defined
Initializing nautilus-open-terminal extension
Unable to open desktop file /usr/share/applications/redhat-email.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-writer.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory
Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory
[root@test .vnc]#
Regards
Mohammed Abdul Muqeet

Hi,
Try these 3 solutions
1. Did you start vncserver services as:
service vncserver start
2.Check that port 5901 has not been blocked by a firewall:
# nc -vz localhost 5901
You should get a connection and a termination. If you get an error, fix the firewall.
3. service iptables stop
Hope This Helps
Regards,
-DK

I am not able to get name of the person when he is calling for which i have already saved the no. on my contact list i have reseted my phone twice help me out

hello i have started using iphone 5 for which i downloaded my contacts from i clouds i am not able to get name of the person when he is calling for which i have already saved the no. on my contact list i have reseted my phone twice its only showing the names of the person whose no. i have saved it with the country code i am staying in india new delhi pls help me i am fed up not able to get the name of person who is calling

Sir, your Apple ID can be used as an iCloud account as well. They are both the same thing.
You can learn more from --> Set up your Apple ID for iCloud and iTunes - Apple Support

I have multiple lines for family members on my account. Can I still transfer upgrades between lines? I don't see the option any more.

I have multiple lines for family members on my account. Can I still transfer upgrades between lines? I don't see the option any more.

More everything. I have one line coming up on the 19th of this month and I'd like to transfer to another user with a later upgrade date. Just not seeing the option anywhere.

I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build. The same call works fine when running on the device

I have a production mobile Flex app that uses RemoteObject calls for all data access, and it's working well, except for a new remote call I just added that only fails when running with a release build. The same call works fine when running on the device (iPhone) using debug build. When running with a release build, the result handler is never called (nor is the fault handler called). Viewing the BlazeDS logs in debug mode, the call is received and send back with data. I've narrowed it down to what seems to be a data size issue.
I have targeted one specific data call that returns in the String value a string length of 44kb, which fails in the release build (result or fault handler never called), but the result handler is called as expected in debug build. When I do not populate the String value (in server side Java code) on the object (just set it empty string), the result handler is then called, and the object is returned (release build).
The custom object being returned in the call is a very a simple object, with getters/setters for simple types boolean, int, String, and one org.23c.dom.Document type. This same object type is used on other other RemoteObject calls (different data) and works fine (release and debug builds). I originally was returning as a Document, but, just to make sure this wasn't the problem, changed the value to be returned to a String, just to rule out XML/Dom issues in serialization.
I don't understand 1) why the release build vs. debug build behavior is different for a RemoteObject call, 2) why the calls work in debug build when sending over a somewhat large (but, not unreasonable) amount of data in a String object, but not in release build.
I have't tried to find out exactly where the failure point in size is, but, not sure that's even relevant, since 44kb isn't an unreasonable size to expect.
By turning on the Debug mode in BlazeDS, I can see the object and it's attributes being serialized and everything looks good there. The calls are received and processed appropriately in BlazeDS for both debug and release build testing.
Anyone have an idea on other things to try to debug/resolve this?
Platform testing is BlazeDS 4, Flashbuilder 4.7, Websphere 8 server, iPhone (iOS 7.1.2). Tried using multiple Flex SDK's 4.12 to the latest 4.13, with no change in behavior.
Thanks!

After a week's worth of debugging, I found the issue.
The Java type returned from the call was defined as ArrayList. Changing it to List resolved the problem.
I'm not sure why ArrayList isn't a valid return type, I've been looking at the Adobe docs, and still can't see why this isn't valid. And, why it works in Debug mode and not in Release build is even stranger. Maybe someone can shed some light on the logic here to me.

Error calling for web-service from BPEL

hello,
I'm getting an exception thrown when I try to call for a web service. Until yesterday it was fine, but since today we keep getting this error message:
<2006-05-29 21:02:03,635> <ERROR> <red.collaxa.cube>
<BaseCubeSessionBean::logError> Error while invoking bean "finder": Instance not found in datasource.
The process domain was unable to fetch the instance with key "c2c73aae36359a11:84cc09:10b7b50ebef:-7d45" from the datasource.
Please check that the instance key "c2c73aae36359a11:84cc09:10b7b50ebef:-7d45" refers to a valid instancet
hat has been started and not removed from the process domain.
ORABPEL-02152
Instance not found in datasource.
The process domain was unable to fetch the instance with key "c2c73aae36359a11:84cc09:10b7b50ebef:-7d45" from the datasource.
Please check that the instance key
"c2c73aae36359a11:84cc09:10b7b50ebef:-7d45" refers to a valid instance that has been started and not removed from the process domain.
at com.collaxa.cube.engine.data.AdminFinder.__lookupInstanceMetaData(AdminFinder.java:314)
at com.collaxa.cube.engine.data.AdminFinder.__lookupInstanceMetaData(AdminFinder.java:262)
at com.collaxa.cube.engine.data.AdminFinder.lookupInstanceByConversationId(AdminFinder.java:235)
at com.collaxa.cube.ejb.impl.FinderBean.lookupInstanceByConversationId(FinderBean.java:177)
at IFinderBean_StatelessSessionBeanWrapper42.lookupInstanceByConversationId(IFinderBean_StatelessSessionBeanWrapper42.java:669)
at com.oracle.bpel.client.Locator.lookupInstance(Locator.java:420)
at displayInstance.jspService(_displayInstance.java:111)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:350)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:824)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequestDispatcher.java:222)
at com.collaxa.cube.fe.DomainFilter.doFilter(DomainFilter.java:152)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:663)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:330)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:830)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:285)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:126)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
at java.lang.Thread.run(Thread.java:534)
Any ideas how I can fix it?
Thanks.

Hi,
We've tried increasing the
<transaction-config timeout="60000" /> to 120000, and also tried increasing the syncMaxWaitTime from the console...
But nothing seems to help.
In addition, the test page of the web service we are invoking returns after 1 second (so there shouldn't be a latency problem)
Maybe you have any other ideas?

How to look for New start Called call for a Maintenance plan

Hi,
I need to find out all calls for a maintenance plan of scheduling type- 'New Start' and Status- 'Called'. How to find this using tables.
For 'New Start' scheduling type probably table field and value is MHIS-TERMA = 'N'. There are different statuse in this table but I am not able to identify the status 'called'. Also what is the field MHIS-ZAEHL(Maintenance package number) for?
Thanks,
Vimal

Taken from the standard IP10 program:
* possible status combinations
* TSABR - Scheduling status: planned date called
* TSVBT - Scheduling status: call outstanding
* TSENQ - Scheduling status: call horizon not reached
* TSENM - Scheduling status: stopped manually
* TSTAT - Sceduling status
* TSABR   TSVBT   TSENQ   TSENM   TSTAT
*   X       -       -       -       A     called with order
*   X       -       -       -       -     called without order
*   -       X       X       -       -     on hold (TSENQ), due (TSVBT)
*   -       X       X       -       F     on hold, due and fixed
*   X       -       -       -       X     skipped
*   -       X       X       X       -     blocked
*   -       X       X       X       F     blocked
*   X       -       -       -       -     LRMDT <> 0, completed

Flat File-to-RFC question, multiple RFC calls for one file.

Hi guys,
I'm quite new to XI / PI and I have a question regarding a File-to-RFC scenario we're trying in NW PI 7.1.
We have a flat file which has two lines with two fields each, let's take this as an example :
001,001
002,002
The files needs to be converted to XML and then transferred to the RFC program which will update a table with the values above.
In the ESR I've created 3 data types (z_row1,z_record1 and z_fileinput1), 1 message type (z_file2rfc_ob_mt), 1 message mapping (z_file2rfc_mm), 2 Service Interface (z_file2rfc_ob_si and z_file2rfc_ib_ztestpi) and 1 operation mapping (z_file2rfc_om).
In the Integration Builder (ID) I've created everything required (The sender and receiver communication channels, sender and receiver agreement, receiver determination and interface mapping).
We're also using content conversion to convert the flat file to XML, this does seem to work because I see all the lines/field in the message when it gets into PI. The problem is that the RFC can only accept two fields at a time and only the first line gets updated. I see that only the first line gets sent to the RFC.
How can I make the RFC call for each and every line ?
Thanks !!

Create the RFC with table, which takes multiple lineitem as input and update the table in single call.
If you want response back then call RFC as synchrounous else in Asynchrounous mode.
By doing this in single call it will update the complete table.
Gaurav Jain
Reward Points if answer is helpful

WSSIG - Call for panel members

Similar Messages

Maybe you are looking for